From nobody Mon Jan 6 04:34:06 2025 X-Original-To: freebsd-fs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4YRM7B4mJFz5jssL for ; Mon, 06 Jan 2025 04:45:26 +0000 (UTC) (envelope-from pmc@citylink.dinoex.sub.org) Received: from uucp.dinoex.org (uucp.dinoex.org [IPv6:2a0b:f840::12]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "uucp.dinoex.sub.de", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YRM786TFtz534g for ; Mon, 6 Jan 2025 04:45:24 +0000 (UTC) (envelope-from pmc@citylink.dinoex.sub.org) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of pmc@citylink.dinoex.sub.org designates 2a0b:f840::12 as permitted sender) smtp.mailfrom=pmc@citylink.dinoex.sub.org; dmarc=none; arc=pass ("uucp.dinoex.org:s=M20221114:i=1") Received: from uucp.dinoex.org (uucp.dinoex.org [IPv6:2a0b:f840:0:0:0:0:0:12]) by uucp.dinoex.org (8.18.1/8.18.1) with ESMTPS id 5064j6Vb010077 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for ; Mon, 6 Jan 2025 05:45:06 +0100 (CET) (envelope-from pmc@citylink.dinoex.sub.org) ARC-Seal: i=1; a=rsa-sha256; d=uucp.dinoex.org; s=M20221114; t=1736138709; cv=none; b=gNYrbt7kthB0ZhZRInxq5gZIXcMuXGGz5BJgVqNsnrfa5guws6pGw6TjnEu4/pVTS7sPbNEk1MwDVD0KbsGwILwb67q2MX7vZ+nLltja+aFX7j9Pyx+m882fXfVbDMnH1dbUSiSUAXmp5jnIRIYwDeeSiaCcQNi8iMIVBNP2fk4= ARC-Message-Signature: i=1; a=rsa-sha256; d=uucp.dinoex.org; s=M20221114; t=1736138709; c=relaxed/simple; bh=5rKiu2mMmkdMs0rRV/NG/+zcP7G5XxmT+/Y/xdd44PY=; h=Received:Received:Received:Received:X-Authentication-Warning:Date: From:To:Subject:Message-ID:MIME-Version:Content-Type: Content-Disposition:X-Milter:X-Greylist; b=hUAbkQNBKba57G3cY8BKbacIY8SmX6hxNEj7Jj6QGrvTmACtFRjoTj4/WA98+gH+yUPf39zd66aGKPL2dEUdd7BEVkHDX3cuj3mLi4h8OETfLBuINZ6p1zPLWZjmHaua44IPdi99GsFi3l3yZK0hl3cIU548zWKj3pCbOjgKqww= ARC-Authentication-Results: i=1; uucp.dinoex.org X-MDaemon-Deliver-To: Received: (from uucp@localhost) by uucp.dinoex.org (8.18.1/8.18.1/Submit) with UUCP id 5064j6aJ010076 for freebsd-fs@freebsd.org; Mon, 6 Jan 2025 05:45:06 +0100 (CET) (envelope-from pmc@citylink.dinoex.sub.org) Received: from disp.intra.daemon.contact (disp-e.intra.daemon.contact [IPv6:fd00:0:0:0:0:0:0:112]) by admn.intra.daemon.contact (8.18.1/8.18.1) with ESMTPS id 5064a5kM067707 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=OK) for ; Mon, 6 Jan 2025 05:36:05 +0100 (CET) (envelope-from pmc@citylink.dinoex.sub.org) Received: from disp.intra.daemon.contact (localhost [127.0.0.1]) by disp.intra.daemon.contact (8.18.1/8.18.1) with ESMTPS id 5064Y6pw088367 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for ; Mon, 6 Jan 2025 05:34:06 +0100 (CET) (envelope-from pmc@citylink.dinoex.sub.org) Received: (from pmc@localhost) by disp.intra.daemon.contact (8.18.1/8.18.1/Submit) id 5064Y6h2088366 for freebsd-fs@freebsd.org; Mon, 6 Jan 2025 05:34:06 +0100 (CET) (envelope-from pmc@citylink.dinoex.sub.org) X-Authentication-Warning: disp.intra.daemon.contact: pmc set sender to pmc@citylink.dinoex.sub.org using -f Date: Mon, 6 Jan 2025 05:34:06 +0100 From: "Peter 'PMc' Much" To: freebsd-fs@freebsd.org Subject: system stalled, no I/O but 100% CPU from nfs Message-ID: List-Id: Filesystems List-Archive: https://lists.freebsd.org/archives/freebsd-fs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-fs@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Milter: Spamilter (Reciever: uucp.dinoex.org; Sender-ip: 0:0:2a0b:f840::; Sender-helo: uucp.dinoex.org;) X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (uucp.dinoex.org [IPv6:2a0b:f840:0:0:0:0:0:12]); Mon, 06 Jan 2025 05:45:09 +0100 (CET) X-Rspamd-Queue-Id: 4YRM786TFtz534g X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.23 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; ARC_ALLOW(-1.00)[uucp.dinoex.org:s=M20221114:i=1]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.93)[-0.928]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; MISSING_XM_UA(0.00)[]; DMARC_NA(0.00)[sub.org]; ASN(0.00)[asn:205376, ipnet:2a0b:f840::/32, country:DE]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; HAS_XAW(0.00)[]; R_DKIM_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_COUNT_FIVE(0.00)[5]; PREVIOUSLY_DELIVERED(0.00)[freebsd-fs@freebsd.org]; TO_DN_NONE(0.00)[]; MLMMJ_DEST(0.00)[freebsd-fs@freebsd.org]; MIME_TRACE(0.00)[0:+] Cheers, This doesn't look good. It goes on for hours. What can be done about it? (13.4 client & server) 44 processes: 4 running, 39 sleeping, 1 waiting CPU: 0.4% user, 0.0% nice, 99.6% system, 0.0% interrupt, 0.0% idle Mem: 21M Active, 198M Inact, 1190M Wired, 278M Buf, 3356M Free ARC: 418M Total, 39M MFU, 327M MRU, 128K Anon, 7462K Header, 43M Other 332M Compressed, 804M Uncompressed, 2.42:1 Ratio Swap: 15G Total, 15G Free PID USERNAME THR PRI NICE SIZE RES STATE TIME WCPU COMMAND 417 root 4 52 0 12M 2148K RUN 20:55 99.12% nfscbd 0 root 65 -16 - 0B 1040K swapin 0:17 0.64% kernel 11054 root 1 52 0 18M 7664K RUN 0:04 0.10% bsdtar 11 root 15 -56 - 0B 240K WAIT 0:15 0.05% intr 16 root 1 -16 - 0B 16K - 0:01 0.03% racctd 11062 root 1 20 0 14M 3804K RUN 0:00 0.03% top 7 root 3 -16 - 0B 48K psleep 0:00 0.01% pagedaemon 11056 root 1 20 0 21M 10M select 0:00 0.01% sshd 6 root 1 -16 - 0B 16K - 0:00 0.01% rand_harvest Interface Traffic Peak Total vtnet0 in 5.380 KB/s 9.113 KB/s 781.439 MB out 4.012 KB/s 8.002 KB/s 674.294 MB # nfsstat -zc > /dev/null ; sleep 1 ; nfsstat -c Rpc Counts: Getattr Setattr Lookup Readlink Read Write Create Remove 1 2 5 0 0 0 0 0 Rename Link Symlink Mkdir Rmdir Readdir RdirPlus Access 0 0 0 0 0 1 0 1 Mknod Fsstat Fsinfo PathConf Commit 0 0 0 0 0 Rpc Info: TimedOut Invalid X Replies Retries Requests 0 0 0 0 11 Cache Info: Attr Hits Attr Misses Lkup Hits Lkup Misses BioR Hits BioR Misses BioW Hits BioW Misses 11 1 2 5 0 0 0 0 BioRL Hits BioRL Misses BioD Hits BioD Misses DirE Hits DirE Misses Accs Hits Accs Misses 0 0 1 1 1 0 8 1 From nobody Mon Jan 6 13:53:38 2025 X-Original-To: freebsd-fs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4YRbJ154kYz5kZYm for ; Mon, 06 Jan 2025 13:53:53 +0000 (UTC) (envelope-from rick.macklem@gmail.com) Received: from mail-ed1-x52f.google.com (mail-ed1-x52f.google.com [IPv6:2a00:1450:4864:20::52f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YRbJ12y58z4gfT for ; Mon, 6 Jan 2025 13:53:53 +0000 (UTC) (envelope-from rick.macklem@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ed1-x52f.google.com with SMTP id 4fb4d7f45d1cf-5d3f65844deso24640959a12.0 for ; Mon, 06 Jan 2025 05:53:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1736171632; x=1736776432; darn=freebsd.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=X4fWRx31BWKHQ4S1TTrH2arfs/wxC30fRyFs9wjf+gs=; b=bUWtPxmGi+DPgsZ9pDJsutD27mUCFHSglkPQ9KOxZsNl9azFdNpnp5SQIfLTmKbzNg JwMApyVwUEJenyNEFFwMS3oMAPSq8YZDH6JImDcRgRkZ2rB5FBIpVsCMyWejlgpcxQXX h68Yo/zgwf/GcjuV2xnkxaqg45Ksgqg91KkKZmZqbXVGv+S42xyukDNtMnZjPD5LPWMu Ak8YZNvPwC/5GFcYrHXa3GFML2PJaqD3O7Vh/wdEbKs51oYZqr33vHHIyg3NxQikItcY mTtF075Fr1tTLouwY/CsGjIWu5ZeNsfH0evebJmfhpn2egqXnGf82hekAf4dgLPqGuiG GBYQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1736171632; x=1736776432; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=X4fWRx31BWKHQ4S1TTrH2arfs/wxC30fRyFs9wjf+gs=; b=thdeUbOTioFWI+3YpDFWuO31AI6QkIVKxNb78cBEtldUtR+rkFxZhlTZNJGbwWDW45 ASPcjKdzJCk4U8bes81j/MbWjqFbwvLP78b6IFpT1/2lBPPs4s+iNbHa9VkQGRcRczeo p52kdc3Y0mE9OeU9lnyOXUmumIfCoy7nTI8ObKYXDpFZ4tZq+rda76fWE1eZRB7fyMkV 8i8hCWLO9i5msF3y3dYyOo0CJe01QUmuyq31pdO5JgTrRVv3Qw03kscEp9K9fn7kWCoa 9AQoJg2D48sZk0RSTCKcT8rwHZrVR+5PoyvCWDGkvjWxBb6UotyZUD7Jn6wRk9Ryj1+F dMpA== X-Gm-Message-State: AOJu0YyDFzhO+EiVul+jXYRSoDUxTDzO4blnFl7DnfExWg+EwXLnPLCF UMGUGnR4/csG9/4eo7hvTTgEzpxZdRh7NZJWZtH0UzwLRheEtpX8rKDfjxLVhcO451KY2bqE2Q/ Xc97C8GJ4VDkYvhH/dqt58Q91xL5T X-Gm-Gg: ASbGncuMIS7vysKN59HVQIaFE8kncXvyObSXvC+4cNP5F4x4pAkGttYMftJiffNVnyn QpA2AYxQs4YunZpB6Vg/S69VoXmmgZn7KQLGA X-Google-Smtp-Source: AGHT+IFLNZhl/vYtUxsVaG7z0Vale9g1YuG3Mkfva67RMYkuLdfVEvIpl/XZFliqKrVvmvm/GCU0IFW+/aGBB8YVz5M= X-Received: by 2002:a05:6402:26d1:b0:5d3:e45d:ba91 with SMTP id 4fb4d7f45d1cf-5d81de39850mr54893414a12.32.1736171631351; Mon, 06 Jan 2025 05:53:51 -0800 (PST) List-Id: Filesystems List-Archive: https://lists.freebsd.org/archives/freebsd-fs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-fs@FreeBSD.org MIME-Version: 1.0 References: In-Reply-To: From: Rick Macklem Date: Mon, 6 Jan 2025 05:53:38 -0800 X-Gm-Features: AbW1kvYbh3QUNnsxNw51M0fkbjq2gFtad0yVFmNjaBtcqgXxq8TZjKEkngg-lzk Message-ID: Subject: Re: system stalled, no I/O but 100% CPU from nfs To: "Peter 'PMc' Much" Cc: freebsd-fs@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4YRbJ12y58z4gfT X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; TAGGED_FROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] On Sun, Jan 5, 2025 at 8:45=E2=80=AFPM Peter 'PMc' Much wrote: > > Cheers, > > This doesn't look good. It goes on for hours. What can be done about it? > (13.4 client & server) > > > 44 processes: 4 running, 39 sleeping, 1 waiting > CPU: 0.4% user, 0.0% nice, 99.6% system, 0.0% interrupt, 0.0% idle > Mem: 21M Active, 198M Inact, 1190M Wired, 278M Buf, 3356M Free > ARC: 418M Total, 39M MFU, 327M MRU, 128K Anon, 7462K Header, 43M Other > 332M Compressed, 804M Uncompressed, 2.42:1 Ratio > Swap: 15G Total, 15G Free > > PID USERNAME THR PRI NICE SIZE RES STATE TIME WCPU COMMAN= D > 417 root 4 52 0 12M 2148K RUN 20:55 99.12% nfscbd Do you have delegations enabled on your server (vfs.nfsd.issue_delegations not 0)? (If you do not, I have no idea why the server would be doing callbacks, which is what nfscbd handles.) Also, "nfsstat -m" on the client shows you/us what your mount options are. > 0 root 65 -16 - 0B 1040K swapin 0:17 0.64% kernel > 11054 root 1 52 0 18M 7664K RUN 0:04 0.10% bsdtar > 11 root 15 -56 - 0B 240K WAIT 0:15 0.05% intr > 16 root 1 -16 - 0B 16K - 0:01 0.03% racctd > 11062 root 1 20 0 14M 3804K RUN 0:00 0.03% top > 7 root 3 -16 - 0B 48K psleep 0:00 0.01% pageda= emon > 11056 root 1 20 0 21M 10M select 0:00 0.01% sshd > 6 root 1 -16 - 0B 16K - 0:00 0.01% rand_h= arvest > > > Interface Traffic Peak Total > vtnet0 in 5.380 KB/s 9.113 KB/s 781.439 = MB > out 4.012 KB/s 8.002 KB/s 674.294 = MB > > > # nfsstat -zc > /dev/null ; sleep 1 ; nfsstat -c Adding -E makes it show all RPC counts. (Without -E you just get the "old Sun compatible" output. > Rpc Counts: > Getattr Setattr Lookup Readlink Read = Write Create Remove > 1 2 5 0 0 = 0 0 0 > Rename Link Symlink Mkdir Rmdir Re= addir RdirPlus Access > 0 0 0 0 0 = 1 0 1 > Mknod Fsstat Fsinfo PathConf Commit > 0 0 0 0 0 > Rpc Info: > TimedOut Invalid X Replies Retries Requests > 0 0 0 0 11 > Cache Info: > Attr Hits Attr Misses Lkup Hits Lkup Misses BioR Hits BioR M= isses BioW Hits BioW Misses > 11 1 2 5 0 = 0 0 0 > BioRL Hits BioRL Misses BioD Hits BioD Misses DirE Hits DirE M= isses Accs Hits Accs Misses > 0 0 1 1 1 = 0 8 1 > > The above suggests that there is still some activity on the client, but the info. is limited. If the client is still in this state, you can collect more info via: # tcpdump -s 0 -w out.pcap host run for a little while. The out.pcap file needs to be looked at in wireshark (tcpdump is useless at decoding NFS). If there is nothing secret in it, you can email it to me as an attachment, so I can take a look. # ps axHl done repeatedly gets a lot more info about the NFS related thread= s. (I'll admit I doubt the info is useful for this case?) # nfsstat -E -c -z repeatedly as above. If you just want to get rid of the mount # umount -N should work, although it can take a couple of minutes. Either not running "nfscbd" on the client or disabling delegations by setting vfs.nfsd.issue_delegations=3D0 on the server (assuming you have them enabled) ,might/should avoid the problem. rick From nobody Mon Jan 6 16:37:49 2025 X-Original-To: freebsd-fs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4YRg681LYSz5jqtn for ; Mon, 06 Jan 2025 16:45:36 +0000 (UTC) (envelope-from pmc@citylink.dinoex.sub.org) Received: from uucp.dinoex.org (uucp.dinoex.org [IPv6:2a0b:f840::12]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "uucp.dinoex.sub.de", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YRg653djXz43b6 for ; Mon, 6 Jan 2025 16:45:33 +0000 (UTC) (envelope-from pmc@citylink.dinoex.sub.org) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of pmc@citylink.dinoex.sub.org designates 2a0b:f840::12 as permitted sender) smtp.mailfrom=pmc@citylink.dinoex.sub.org; dmarc=none; arc=pass ("uucp.dinoex.org:s=M20221114:i=1") Received: from uucp.dinoex.org (uucp.dinoex.org [IPv6:2a0b:f840:0:0:0:0:0:12]) by uucp.dinoex.org (8.18.1/8.18.1) with ESMTPS id 506Gj6ZZ055954 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Mon, 6 Jan 2025 17:45:06 +0100 (CET) (envelope-from pmc@citylink.dinoex.sub.org) ARC-Seal: i=1; a=rsa-sha256; d=uucp.dinoex.org; s=M20221114; t=1736181909; cv=none; b=qTPFgnuCPCOklTnOu5qnuC94jcW+ZXIu6wZotWzRzT1/iBxurrCS2J4pQb7Tbb2JdyLb1dCptKXhTDzvyFIS46lLAgL0C6KIIkyf/BZyeOYO6GZ3JZIEGBYtJXdusoaA7fNzizRwNm4DUz2X/YboS4JTR+EHvWwqxUs4FdwtaoU= ARC-Message-Signature: i=1; a=rsa-sha256; d=uucp.dinoex.org; s=M20221114; t=1736181909; c=relaxed/simple; bh=OY7vKxa7cJMlB3uDe0HmOa6LJhsuQJFQdGiugUj8m2A=; h=Received:Received:Received:Received:X-Authentication-Warning:Date: From:To:Cc:Subject:Message-ID:References:MIME-Version:Content-Type: Content-Disposition:Content-Transfer-Encoding:In-Reply-To:X-Milter: X-Greylist; b=aXfs2uUW1DFkw/jQs52wJSo16Y4aIj+8WaN/6KyHl3ma8ZzTci4H/xqgrM7Lg7KnnDxfCZf7HCQy/e4FSJPC5b/Gs8eji37BlNIVMvkZxnP6PVpwCZiur8xJ5q83EE+21UiqzR2x9HvVQzRj+i/C68kcA0Rd0gCYB31JgS+LBJk= ARC-Authentication-Results: i=1; uucp.dinoex.org Received: (from uucp@localhost) by uucp.dinoex.org (8.18.1/8.18.1/Submit) with UUCP id 506Gj66d055953; Mon, 6 Jan 2025 17:45:06 +0100 (CET) (envelope-from pmc@citylink.dinoex.sub.org) Received: from disp.intra.daemon.contact (disp-e.intra.daemon.contact [IPv6:fd00:0:0:0:0:0:0:112]) by admn.intra.daemon.contact (8.18.1/8.18.1) with ESMTPS id 506Gd6dc026824 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=OK); Mon, 6 Jan 2025 17:39:06 +0100 (CET) (envelope-from pmc@citylink.dinoex.sub.org) Received: from disp.intra.daemon.contact (localhost [127.0.0.1]) by disp.intra.daemon.contact (8.18.1/8.18.1) with ESMTPS id 506Gbn7U093122 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Mon, 6 Jan 2025 17:37:50 +0100 (CET) (envelope-from pmc@citylink.dinoex.sub.org) Received: (from pmc@localhost) by disp.intra.daemon.contact (8.18.1/8.18.1/Submit) id 506GbnI1093121; Mon, 6 Jan 2025 17:37:49 +0100 (CET) (envelope-from pmc@citylink.dinoex.sub.org) X-Authentication-Warning: disp.intra.daemon.contact: pmc set sender to pmc@citylink.dinoex.sub.org using -f Date: Mon, 6 Jan 2025 17:37:49 +0100 From: "Peter 'PMc' Much" To: Rick Macklem Cc: freebsd-fs@freebsd.org Subject: Re: system stalled, no I/O but 100% CPU from nfs Message-ID: References: List-Id: Filesystems List-Archive: https://lists.freebsd.org/archives/freebsd-fs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-fs@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In-Reply-To: X-Milter: Spamilter (Reciever: uucp.dinoex.org; Sender-ip: 0:0:2a0b:f840::; Sender-helo: uucp.dinoex.org;) X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (uucp.dinoex.org [IPv6:2a0b:f840:0:0:0:0:0:12]); Mon, 06 Jan 2025 17:45:09 +0100 (CET) X-Rspamd-Queue-Id: 4YRg653djXz43b6 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.25 / 15.00]; ARC_ALLOW(-1.00)[uucp.dinoex.org:s=M20221114:i=1]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.95)[-0.953]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; TAGGED_RCPT(0.00)[]; ASN(0.00)[asn:205376, ipnet:2a0b:f840::/32, country:DE]; RCPT_COUNT_TWO(0.00)[2]; MIME_TRACE(0.00)[0:+]; MISSING_XM_UA(0.00)[]; FREEMAIL_TO(0.00)[gmail.com]; R_DKIM_NA(0.00)[]; MLMMJ_DEST(0.00)[freebsd-fs@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; RCVD_COUNT_FIVE(0.00)[5]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DMARC_NA(0.00)[sub.org]; HAS_XAW(0.00)[] On Mon, Jan 06, 2025 at 05:53:38AM -0800, Rick Macklem wrote: ! On Sun, Jan 5, 2025 at 8:45=E2=80=AFPM Peter 'PMc' Much ! wrote: ! > This doesn't look good. It goes on for hours. What can be done about i= t? ! > (13.4 client & server) ! > ! > ! > 44 processes: 4 running, 39 sleeping, 1 waiting ! > CPU: 0.4% user, 0.0% nice, 99.6% system, 0.0% interrupt, 0.0% idle ! > Mem: 21M Active, 198M Inact, 1190M Wired, 278M Buf, 3356M Free ! > ARC: 418M Total, 39M MFU, 327M MRU, 128K Anon, 7462K Header, 43M Other ! > 332M Compressed, 804M Uncompressed, 2.42:1 Ratio ! > Swap: 15G Total, 15G Free ! > ! > PID USERNAME THR PRI NICE SIZE RES STATE TIME WCPU COMM= AND ! > 417 root 4 52 0 12M 2148K RUN 20:55 99.12% nfsc= bd ! Do you have delegations enabled on your server ! (vfs.nfsd.issue_delegations not 0)? Not knowingly: # sysctl vfs.nfsd.issue_delegations vfs.nfsd.issue_delegations: 0 ! (If you do not, I have no idea why the server would be doing ! callbacks, which is what nfscbd ! handles.) Me neither. ;) The good news at this point is, it is a single event. At first I thought the whole cluster got slow (it is always too slow ;) ), but it was only this node - the others have no cpu consumption on nfscbd. The bad thing is, I cannot remember why I did switch that thing on. ! Also, "nfsstat -m" on the client shows you/us what your mount ! options are. It had to be destroyed, as effects got worse. What I figured is: it didn't issue any syscalls, and it didn't act on kill -9. Which means: most likely it found an infinite loop inside the kernel, aka a never-returning syscall. ! The above suggests that there is still some activity on the client, but t= he ! info. is limited. Yes, it got ever slower. The NFS mount is for /usr/ports, and I did fix some ports there. At some point a "make clean" would start to take minutes to complete, and there I noticed something is wrong. Finally it didn't even echo on the console (I had only one cpu available, and then when something is stuck within the kernel, all depends on preemption). ! If the client is still in this state, you can collect more info via: ! # tcpdump -s 0 -w out.pcap host ! run for a little while. I had to destroy it. I tried to run dtrace to pinpoint exactly where that thing does execute, but it didn't startup. At that point I didn't consider it feasible to try further investigation. These are temporary building guests, they get destroyed after completion anyway. So, as apparently it was a single event, I might suggest we just remember that nfscbd /can do this/ (under yet unclear circumstances) and otherwise hope for the best. And probably I should get rid of that daemon altogether. I think I read something about these delegations, and it looked suitable for the usecase, but I didn't realize that it would need to be activated on the server also. (The usecase is, a snapshot + clone is created from the ports repo, then switched to a desired tag/branch, and that filetree is then used by a single guest, exclusively.) Thanks for Your help! cheerio, PMc From nobody Mon Jan 6 17:34:16 2025 X-Original-To: fs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4YRhBK10VGz5jvfl for ; Mon, 06 Jan 2025 17:34:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YRhBJ4779z47DJ for ; Mon, 6 Jan 2025 17:34:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1736184856; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=dR/8m0yOvErV3Uq/0TO0LCHp+yF0AWME0DlROCYL+W4=; b=c/10ivpu/ReYk8nHGf4ihkDe+B/8pBealKib9u3LNeUSTn38511dzWtO8Yx+l9GirKQXfP o+zPjVp1KOgrJaBE/tCuXePn9eLfkEu8mgkC6pew7wvfY4PI0TN51Udmr5AfdFJKqHzMgL BrxLCX2lW7H1OUbYkmwROsBQ5yAYkbnygzO65iv51kLZx7NpNnCFO4cR80p0NDu4FN87mu 5cZCC1juNl65bzbN6uKkOHp6AtWHsbejf2A7PqpBoWenSK+5wHb2N4gMzlgl18GysHueo9 kbx/icx7oWrSUAb7MDEtpj2YelpYSjB0CXxPM5frK2uDUv5RFEd7sDargzvgKQ== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1736184856; a=rsa-sha256; cv=none; b=GQ4DuZksLs3t4Zeq2XLjvJXqy+5SIy5kJOZiCWFiJjPtCRkzKkqfJRgydhx9dRMlSeSrky Rd60sZJm0Q/cWhdLiWao39izGtembYQmfd2a8qTcmaYORe/e5C2MAudrq3JDkGYN/Vmyqi b/q4RsH5pl7JpTypXg2RL/EbLmMfiWZpP68vhKxN6l2d5UjZOtmiSdM1mYLwzOEkOURjDo CBfWJqIbK7XOGljSMp5wEKGgwV76/qm4HijLnCuqbOgxWLYsnK3YseGupVxmZGEmWkKWeR hWD/ow9qBLrrfBkdFsr/fFuCJXg26G/i1KLkMfFM5hfrql9zJCwQtPc30LVTBA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4YRhBJ3jFMzZcR for ; Mon, 06 Jan 2025 17:34:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 506HYGT8034361 for ; Mon, 6 Jan 2025 17:34:16 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 506HYGgJ034360 for fs@FreeBSD.org; Mon, 6 Jan 2025 17:34:16 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 283761] glabel(8) ExFAT support requested Date: Mon, 06 Jan 2025 17:34:16 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 14.2-RELEASE X-Bugzilla-Keywords: feature X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: emaste@freebsd.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: Not A Bug X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Filesystems List-Archive: https://lists.freebsd.org/archives/freebsd-fs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-fs@FreeBSD.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D283761 Ed Maste changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |emaste@freebsd.org --- Comment #4 from Ed Maste --- (In reply to Kyle Evans from comment #3) > I'd be somewhat afraid that glabel(8) support may give the wrong idea tha= t we can > do anything with these and just cause frustration. We can mount them via fusefs-exfat though, so IMO support in glabel is fine= to have. --=20 You are receiving this mail because: You are the assignee for the bug.= From nobody Mon Jan 6 20:20:07 2025 X-Original-To: fs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4YRlsg5Xc9z5k8ny for ; Mon, 06 Jan 2025 20:20:07 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YRlsg4HmWz4WVJ for ; Mon, 6 Jan 2025 20:20:07 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1736194807; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=fS98Ojtb5VKs5RwMT9eQlTkRREb11zMJFmzKtdpXWgU=; b=w/0GGm/0clKvjTjFPKRFJDx9/Hwlm/fWpTXRMXqHwQ/BgBFl2QS2TxES+nRPPVKlfZ4FSI nGXgPdOgex4zmoGmUtTZ4bcI9GaaWbjkJ6lh53OjKBXoSqjG82tX1WvAIQLvOfYqb34SUu ZNMNRr6IzEGPkgpW4IaRi5EJgKFJknVxw0CGGGGIoZh8NmW8pBvbVQJKzKODPW62YKYECY IYrYcQJo31aumNNGHiFRhakDLzhA31Qv9r2wfc0+81ALcJ0aBsF+JXZoQ5zYFS9SrfuXzd H8LQ6/DpY3b+CBKXwmvZ2TWfyxfmEe5tFBmZfTk4qV/+pBXmWuQMNnSuYIa3Vg== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1736194807; a=rsa-sha256; cv=none; b=EJToEINngGzvHNi/h5vbUT3ZTGb86UZy58g+u1/LwN8k9Ixkx7ujP1xR78EuOmP2u+em1G r3EVvs7o6RW9uj+8XeEXb8g/inwz2hpyfyT8eD/f+kUrFNSsXhFbhhWKA1W4U5AfLKee8Z HlooRrtcpArA7ITUDT9+exS984jtrZccY60NDfEqHVOOBdZZhcv2r5Ok7VuMINusxuptGp h9JWpgT0Lh0CyOPG4k8jS1YC+7d/nCPXiwjvfTs+dHc7ivBNJ4nGtBAkFbPzDOUaD9oeeN SNh/GPukDuF32PnNXk0efG0ORFbfU5p8v5YZNNmT/a/tEU8ofu8LqrnUrdjXpQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4YRlsg3gz7zf7V for ; Mon, 06 Jan 2025 20:20:07 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 506KK7oF035729 for ; Mon, 6 Jan 2025 20:20:07 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 506KK7Eo035728 for fs@FreeBSD.org; Mon, 6 Jan 2025 20:20:07 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 283888] makefs Assertion Failed: makefs/zfs/fs.c, line 190 Date: Mon, 06 Jan 2025 20:20:07 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 14.2-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to Message-ID: In-Reply-To: References: Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Filesystems List-Archive: https://lists.freebsd.org/archives/freebsd-fs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-fs@FreeBSD.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D283888 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bugs@FreeBSD.org |fs@FreeBSD.org --=20 You are receiving this mail because: You are the assignee for the bug.= From nobody Mon Jan 6 22:47:19 2025 X-Original-To: fs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4YRq7W3zXfz5kLJv for ; Mon, 06 Jan 2025 22:47:19 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YRq7W2Tkjz4qCv for ; Mon, 6 Jan 2025 22:47:19 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1736203639; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=4U/br/UQTlChd/tczUK2xtqMs1wCly8GF6DOnUXcCMU=; b=CYT2I0y0/Pe+4ADKOrhnm7HKqExjQNE++uu/LLrG7bGBiCfwwjA2cXW58545xxhW1/U/cJ EuafHw0drC1+bgnyc10gkRzIAAGQWixA260fU50wQQRtZ6N5sP+o5hn5qWWLHpPJXxP/h8 PylNa5poNTyTl1njD8o74nMvOMiPM8Zc2w1k7Nbh0c5GzfeDZB1UAdkplyI2ol6LpzohxI XrEs7sk2rUbcmF+TCapF9b3lI8a7o3e7vuLCDcYoslBsDiDU3l3dX1QiGvkaarWBmRTKRm tiqxreOBag+cpz8k4J460nO/jwHJqWaOr7opLmlt/z21YdZ1KEkKaLpcBYJJFg== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1736203639; a=rsa-sha256; cv=none; b=grj55TtVYZNui5EqneuKtGfu3ZM6xkPp2VObVkDQRvg1t0ooZu6Br4UNNsGtmyxAeTaP0E m3+oR6dOq55PD9xQQd8uU59R6z1e2h6JktCs21KWdZJUd/iNKeHH2YviDX4OOuIkvJlC6W 3BLThPoLRUTb1Fhgjvon8UwD/AfP7OOagQ+k2f/xKEd9SQhNzgY8cXk3ipENHnUu9ZIe3U RLAKMlrT6cShv9wPo2HUkzJF3RGgJSwIAvwHCbsgaFhw1WeYZ0zP2uhk2MFKyagFvISNFM RcQbPotB2egXXv6IT5CCiMNLUQ4XDnOn5Tpp5Jdkr9R0D+5NOseWZlr+rtkonQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4YRq7W1jRszkd7 for ; Mon, 06 Jan 2025 22:47:19 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 506MlJ66004028 for ; Mon, 6 Jan 2025 22:47:19 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 506MlJpq004027 for fs@FreeBSD.org; Mon, 6 Jan 2025 22:47:19 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 283888] makefs Assertion Failed: makefs/zfs/fs.c, line 190 Date: Mon, 06 Jan 2025 22:47:19 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 14.2-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: markj@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status Message-ID: In-Reply-To: References: Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Filesystems List-Archive: https://lists.freebsd.org/archives/freebsd-fs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-fs@FreeBSD.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D283888 Mark Johnston changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |Open --- Comment #2 from Mark Johnston --- I tried opening the core dump using 14.2 debug symbols, but it's unusable.= =20 Where did you makefs binary come from? The assertion is saying that makefs, while traversing the input directory hierarchy, encountered something that isn't a regular file, a directory, or= a symlink. So, probably a unix socket or a fifo. I can see in walk.c (not specific to ZFS) that sockets are skipped, so there's probably a fifo in th= ere somewhere. Can you confirm whether that's the case? makefs -t ffs works fine with fifos, so I suppose we should handle them in = the ZFS backend too, but it'd be nice to confirm that that's the actual problem here. (In reply to Michael Dexter from comment #1) That would be unrelated. Did you do anything to the pool before you export= ed it? --=20 You are receiving this mail because: You are the assignee for the bug.= From nobody Tue Jan 7 09:04:52 2025 X-Original-To: fs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4YS4r54G0qz5kD7v for ; Tue, 07 Jan 2025 09:04:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YS4r52wQ8z4vrC for ; Tue, 7 Jan 2025 09:04:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1736240693; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=OkXX3/P+QAyYetQ1nMyAvtY62LdBtl0HBu2q85w/KdQ=; b=hGLTYYap90Oz5zN54FtU/AjpHiJK6KWGNvwkEKYDbG0pLSmNGUdWZ0VZ90TYoGinKuZTcT NKy9yn+D0+8EQEyt9LHBu7qIE72/6GVES8t1qX1OrrMAwRE/H14qJ0x9BPwkDVaMQCiJFU ZGENt2qGgkx2Da3KRCauoFMFW6bm4V0k6OpOeSErt18pA41pLxntpZLG7FGVvIEuST5LAk khvzQNzOxMYvqtBnr/nUVtnyPWaRXTr/FLTuqDnmBQqwjd/hlg0a97prKHV+x4Z5CMPDWy Q6ANTNdf9URFmuGPTqiDAs8KdYE0Ox1tME8Y04Pln/wqVGlwBDibfZR+QNkOBQ== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1736240693; a=rsa-sha256; cv=none; b=GrUTarzB7uJzVk4JOijFi1ZxhcnxQ3s/ECwpplHWuvx1DoOzqdEYLh3JWISvc+f/kzSWXJ MJrgzbq+2f8OhIPnIVpx4CdkDcla8oXmm+ZmRfUNPzND+rv63n+3U+sv5h9OTZL3w3qNks XXi1YMI46y7rjBuselZtWZZK65VEQIo7+cC9KBrWtQmcfpy3kW0DG8/O9cHe/IK1osH2XL LTqya6PkH8Bwh85Ny+L5COVCrvKjJuP41TSGk6/D0zRTDO1FFNMm8hMiOtYvo8pNJURdfI heRaP7qa5f3HRxDGaUhPLJUZ8d0xjTJfIh3UHW6AeeNstPo7N7i4tvQqBojpMg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4YS4r52D3dz13BV for ; Tue, 07 Jan 2025 09:04:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 50794rUl086677 for ; Tue, 7 Jan 2025 09:04:53 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 50794rr5086676 for fs@FreeBSD.org; Tue, 7 Jan 2025 09:04:53 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 283888] makefs Assertion Failed: makefs/zfs/fs.c, line 190 Date: Tue, 07 Jan 2025 09:04:52 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 14.2-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: editor@callfortesting.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: DUPLICATE X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution Message-ID: In-Reply-To: References: Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Filesystems List-Archive: https://lists.freebsd.org/archives/freebsd-fs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-fs@FreeBSD.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D283888 Michael Dexter changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Open |Closed Resolution|--- |DUPLICATE --- Comment #3 from Michael Dexter --- (In reply to Mark Johnston from comment #2) This is stock upstream 14.2 or locally-build 14.2 binaries and I see this a duplicate of my previous PR 283583 having make the same mistake: accidental= ly mount devfs in the directory used for makefs. Regarding the panic in the photo, my steps were: Image a makefs-produced image to an NVMe device and: import the pool with -R /media manually mount zroot/ROOT/default set a root password with pw generate rc.conf generate loader.conf recursively copy in .ssh install 9 upstream non-base packages export the pool, causing the panic Subsequent imports/exports did not cause the panic. I will closed as a duplicate of 283583. *** This bug has been marked as a duplicate of bug 283583 *** --=20 You are receiving this mail because: You are the assignee for the bug.= From nobody Tue Jan 7 09:04:52 2025 X-Original-To: fs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4YS4r60NNhz5kDBF for ; Tue, 07 Jan 2025 09:04:54 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YS4r54dJDz4vrD for ; Tue, 7 Jan 2025 09:04:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1736240693; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=o+2A/LLm+hlddGIh/Qk8Dgci9VbOIID0E8IMmBFUDFY=; b=v9o8tnsDIJEjd8c18QsFBzClVTjtfEEhJrYybylozTyeH0OVu4ZOsYkN8dD2I8OcnQx1eX J6m55Ua/WEjUSWTxp4QG80CXFm0IdmA3pRf3Neidu0DPTQU7UXBWj3IWXA3klRT30UbZP0 /DM0F/VwylDIX4h9OtxulAe5BYWG1o7Kh8udmh6/KfQHebU2jR2aptCiGbBz2IGCLNMNW8 Z3ve55I5KnkmxEcWybn76CGE62GCHK+6NBANBm9m9U2TjjdQBaX6TahXdHncKGP2vF1jhw JnnoBNy6bjXoenMvmImtPz1NFj5V+csMphcMXw5xTRTW8rHR2M2oyEMZlkspsg== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1736240693; a=rsa-sha256; cv=none; b=N3RbCTAFTVC+Env2d513pnaJid5eljAQ5Zh6IPxQJSR0/jL71IiUdDINyx7koWTCdLpwQM DwSErObe+ptLYX9/g5qjLkEo8nxfyJ9OKZ1n50uyJWds9untifOyk20sJOqOXUR4anMe2u aEfUTjmI8DtFXT6/RwRE705ggoFASjca/H6m3UaWQIL3l1U3B4X39Qym4WkVuf+puLdNqj SHzpv7SsZiShxxyUzCoAfFKwaE4ikjjPHmfL7UmrLDYCHxpfaaKZh4BSf6kQC8LJYFcFD5 nttLHu+6Ydq6ahcfVpbMOavC6zNKLvwLgc3Db1u4X66akaoJ3lOGmc5z9d3UQw== ARC-Authentication-Results: i=1; mx1.freebsd.org; none Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4YS4r542X8z13Mq for ; Tue, 07 Jan 2025 09:04:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 50794rkf086688 for ; Tue, 7 Jan 2025 09:04:53 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 50794r3f086687 for fs@FreeBSD.org; Tue, 7 Jan 2025 09:04:53 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 283583] makefs(8) -t zfs Assertion on unexpected devfs mount in directory Date: Tue, 07 Jan 2025 09:04:52 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 14.2-RELEASE X-Bugzilla-Keywords: crash X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: editor@callfortesting.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Filesystems List-Archive: https://lists.freebsd.org/archives/freebsd-fs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-fs@FreeBSD.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D283583 --- Comment #1 from Michael Dexter --- *** Bug 283888 has been marked as a duplicate of this bug. *** --=20 You are receiving this mail because: You are the assignee for the bug.= From nobody Tue Jan 7 14:24:07 2025 X-Original-To: fs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4YSCwR5b1fz5kdt3 for ; Tue, 07 Jan 2025 14:24:07 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YSCwR3kzVz4Gp1 for ; Tue, 7 Jan 2025 14:24:07 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1736259847; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=OFsqzCWvSP8Z6RWFlbMFUfsDZ/2N86pV2NerGPat9ik=; b=p0XlW7CCfZp8oOZAzIuZPoXzuIvZ9FEDaC0+C+7Au+d3BuzJN+tx+p7/d9vlpSguJ4DkOZ S7+bFmIJTdwkz3uzvYiGCVO1LMdjKwbM0mKp7afBjm2bHDhVLaJOpaM2B312VRjoZEn++x nT43CpxevDuvhdO74XusYV3hHc/HEAc7LSQu9uVJKMfLMamSFP43iupsf7IZSN4psIjRNc N0c21V3t5Tb9AM+wm8eDKVGcb5wwLbJJJXaAqMT/l9cE7mX+2tzLB74zVEld00yOFRm2b4 enu3XsV9j2r89nx7aCk+UEuWcMB5ffc7w536xMGf9LDOrCjYaqoY4UhoSWRavw== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1736259847; a=rsa-sha256; cv=none; b=B8j7iFLAZ+Mm9zHnjiqNCK9fBtLHl9yn6lrF/gQwEIgDJY6A6ZUM4ZzrZyXfG2j9sWD/Pk AoimtZ283x5oaVS0Q7WRXN9WAix6mX+QxnY4PrqedrkPzL31+d6NZ4aoLoeRPUkLDVOIUL uJ0xjXYM65E34mtFCnT6u04yr0jJvYYhaVCH9Fcj8JE8rxSIAkXYDQuc+bigvDO0LTcEcV Nnov5OOYrzcwAtzpVMflLn7XYSljrXruTbdT86y7ovPV40rykKVa3LB5WWMlMIxTiWIH2c 2jR8eD1cNdZXMr50RxZKxo8NGRa14zk4nZwpIAjVC71IDoTzm0H2ILAB/4bpzg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4YSCwR35zZz1CkJ for ; Tue, 07 Jan 2025 14:24:07 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 507EO7JZ086864 for ; Tue, 7 Jan 2025 14:24:07 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 507EO7xs086863 for fs@FreeBSD.org; Tue, 7 Jan 2025 14:24:07 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 283583] makefs(8) -t zfs Assertion on unexpected devfs mount in directory Date: Tue, 07 Jan 2025 14:24:07 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 14.2-RELEASE X-Bugzilla-Keywords: crash X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: markj@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: markj@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status assigned_to Message-ID: In-Reply-To: References: Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Filesystems List-Archive: https://lists.freebsd.org/archives/freebsd-fs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-fs@FreeBSD.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D283583 Mark Johnston changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |Open Assignee|fs@FreeBSD.org |markj@FreeBSD.org --- Comment #2 from Mark Johnston --- There's no real way for makefs to handle device nodes except to skip them or create dummy files. I think printing a warning and skipping is probably the more useful behaviour. --=20 You are receiving this mail because: You are the assignee for the bug.= From nobody Tue Jan 7 17:32:13 2025 X-Original-To: fs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4YSJ5T3gnmz5kt2W for ; Tue, 07 Jan 2025 17:32:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YSJ5T1s9wz4dyR for ; Tue, 7 Jan 2025 17:32:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1736271133; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=hl4gGAMRCEIcErVK5Q0N0fIW9AjfIkancoHOCVq9IyU=; b=blmr7Bj2kcIlCOrrooJTUpMdmXFz4JiXVtNbvvlbuwOGHOXRSVySRcb35bgJUN3uhQm5gK UUz08oap6y4Il8HHv35Yz1MyTpydvtWmpL5m4VsMZNr/Aho3KJVhWUzLdCWciAMKWCl4Pw b6mOf8l0/0FWqcj6ysMO44kdhy6Baz2uIV73pJeko+AZ97YhEDDvxi7aSNSujW0A1GDUCi K1hD6jmpYrK9qxDpl1I+pMx4B7OvBeo3RrC5ynUft6MEuhJLaPoLNnSMXWhm9+EkLEibLI V/5fLAXzemrHhuUTW8pOZik8fh/WRnV6ykbAzc3hUhMYLyPbu83xqMWZheNsqQ== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1736271133; a=rsa-sha256; cv=none; b=LfrgBTg14z1StymHUWF2hjkFwCrG9MvfL5cQC2mDsROWe2yDvuuG7VqIbGqbD2VdOEkhCb 3OcBbdZNN+WG8hP/V8ILTgBc90lU3w/dz0aB9KquFl3/uGDRJl8LSQVg8lwYltkOzq50ZX etyZshJZcHWvrJhATUNPbhoADaB00CWWosArdTZvihtWuuNAMvmhS5iwpRaB2+DPck02gF 527xt1vvSwtbTACNSjnx/RjNadq+LtDxPgcgvr0JJbOU3/Bqv90cjLyygaPc4ohJGIb4/Q VwrSv8TkIEnJ+PrJSc1XtvgKsIqow5NX8H5AV9R2kwe16s384q1usGVEJk0iZQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4YSJ5T1RKBz4WT for ; Tue, 07 Jan 2025 17:32:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 507HWD1w039528 for ; Tue, 7 Jan 2025 17:32:13 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 507HWDjS039527 for fs@FreeBSD.org; Tue, 7 Jan 2025 17:32:13 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 283583] makefs(8) -t zfs Assertion on unexpected devfs mount in directory Date: Tue, 07 Jan 2025 17:32:13 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 14.2-RELEASE X-Bugzilla-Keywords: crash X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: grahamperrin@gmail.com X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: markj@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Filesystems List-Archive: https://lists.freebsd.org/archives/freebsd-fs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-fs@FreeBSD.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D283583 Graham Perrin changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fs@FreeBSD.org --=20 You are receiving this mail because: You are on the CC list for the bug.= From nobody Tue Jan 7 21:22:26 2025 X-Original-To: fs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4YSPC7421cz5k0Rd for ; Tue, 07 Jan 2025 21:22:27 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YSPC65qf2z4B7k for ; Tue, 7 Jan 2025 21:22:26 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1736284946; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=YDIFNeOqjPi4YpT5xrXCUw6DOt48Psjj0hZ6k+7pusU=; b=ot3zvwtTi4ctNLCvqxHdltNEwA6IEBt+fDj0Jj3+/bULDQBb2vY05ySat3Z5FhtYRD2Jt+ 4bXJrNEtmpkOWsDCzLAXQKFCC466nIQ+W0YG1dpycpE22SP7ushbGQ6cBBrZGh+QxkVWAk vMqSvZ2A+/lUT7ZbhnlTdHS7YMN8xu5H1vCHeLHYogC3eInS6+Z4KPx2jlE1qrEdKdAM1Z Xt0LoQwWX3FUE9tyg+GeV50fc8PbMJL6eHiMPDyZccI0U2jRLLCCAuxHQVFlq3DQTczhyA o+1AbndbESD2Eej9uvrguwc0d7qk31ZtDjnYJIlobr+q42MsxqCtGNwXUjJpow== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1736284946; a=rsa-sha256; cv=none; b=pgPDB3jNBY7VXHGeq+dW0qqxI6YVWDfHpBLSqYUlRxFmydqN0niEd4FPXJ/qyMcCNU7X+q G5wsrfvKIb9OFCXXTbEQI0G3pT9+4XXhLL2QPd21bjbYY6O4F9DVbt0Aayj56xh0VbGUVB HIstwXs/cCoisO/vvn6x9n07kyWnP3G7G5NKJ8pC4eB6fFZe6dACtQbjHETaJ9EbLS+nLR GyfputTosyOQ3j3TzE9TO4u4QWP5sT+v2ryleulhrbMjRQqOaruWRaI+CMhUOwAWVAOR/J 2U44BQFtoDWbPIAbr7j2h3JiyXR6KUpnPNdEKiWZ4oXrGbzgLiu+89/XHteF4g== ARC-Authentication-Results: i=1; mx1.freebsd.org; none Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4YSPC65DWlzBJx for ; Tue, 07 Jan 2025 21:22:26 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 507LMQ2H076543 for ; Tue, 7 Jan 2025 21:22:26 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 507LMQeQ076540 for fs@FreeBSD.org; Tue, 7 Jan 2025 21:22:26 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 283583] makefs(8) -t zfs Assertion on unexpected devfs mount in directory Date: Tue, 07 Jan 2025 21:22:26 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 14.2-RELEASE X-Bugzilla-Keywords: crash X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: editor@callfortesting.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: markj@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Filesystems List-Archive: https://lists.freebsd.org/archives/freebsd-fs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-fs@FreeBSD.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D283583 --- Comment #4 from Michael Dexter --- THANK YOU!!! --=20 You are receiving this mail because: You are on the CC list for the bug.= From nobody Tue Jan 7 23:45:37 2025 X-Original-To: freebsd-fs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4YSSNf3wpKz5kBNt for ; Tue, 07 Jan 2025 23:45:54 +0000 (UTC) (envelope-from rick.macklem@gmail.com) Received: from mail-ed1-x52a.google.com (mail-ed1-x52a.google.com [IPv6:2a00:1450:4864:20::52a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YSSNf0lvxz4N8d for ; Tue, 7 Jan 2025 23:45:54 +0000 (UTC) (envelope-from rick.macklem@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b=LkeE7NCH; spf=pass (mx1.freebsd.org: domain of rick.macklem@gmail.com designates 2a00:1450:4864:20::52a as permitted sender) smtp.mailfrom=rick.macklem@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-ed1-x52a.google.com with SMTP id 4fb4d7f45d1cf-5d7e3f1fc01so4584523a12.2 for ; Tue, 07 Jan 2025 15:45:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1736293553; x=1736898353; darn=freebsd.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=SImdlqRtmMt8WhW3myj11iS97Qv7b9Gj2Y42sisMhxQ=; b=LkeE7NCHbpS7qtax3270J/tI51HnjdZcqe1LbWNCNjAjARMSWGXBpctDfaE7NhE3Rk GtF+vr56BpkzsI80Z43walVrdI1MNJlyUBf6ZyBFJCQ4FyCr8YZHGvyK9504kxftTDGz FLriEURfRTOd4hE4WhSehbpMOw+mA3NZyxFCli/L2tXdllyLPBIzKCUDdk+Nt+EBqIPj p0vN7ZUugKfT338PIzYLo9Ggll9Ong68tBrSBT11pGRWyUpqhwMtg/jCo6T1ehYmRWa7 NApgZImIhOeTvxqNizyOXPuG2/wJxwPmzg5Go1i5hK9Qt2UspPKgEvDPZzmpWpBCOXw/ rv0A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1736293553; x=1736898353; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=SImdlqRtmMt8WhW3myj11iS97Qv7b9Gj2Y42sisMhxQ=; b=NW8aOPBOuOSVndcJ8hPW1dN2DLVwXK5vncBoecKH/UcRqDupZv7wesMGFfZyr3W+zj 09KhmEAs1a63RMvUiNxHEeSkwbBBJtkaGEPisyJ92BbLvVJS4tcE8pTYqM9BSGowgYgZ /LBcQQN5o5Lar3k/R7MTXiRwvTPN5RRGghRePbK/qv+jOcPTzWlPeXznJ6G4viU8H6Jw d86YuS+ZWAIo7k/OLkNgoP05b7fxETat1U1L7I7Uc4YgqD0VdllQcbY8hnJXqKABTxhz Lsv53sLp9KaQKy78jouEfBL9eueFaVOX61OtIEC0SUn4r7tgmb828K/kya47RrI/Mchx hajw== X-Gm-Message-State: AOJu0YwKv39NMjw/ewp0j8Yot1HQW4zXNv+lugL7sZtve50gRk5vHprA co0vomp0uzBEDwGSNWX2lbd0Tgu10omAcUAl0z02PPsYlVrvrFBQC7QbxLNqTVZ8y3thR6o2BNo U+4ZJIGOoYVTP6aNJRv4JYmJpwoO0 X-Gm-Gg: ASbGnctt0QlrImslhSXcZk82HYNMgTv7j3V4yWLPcseqnRwCz6aSS96X1/y/16mo1yR RGSh5vziiOA71BDHO/ZcYBD2+km8oa457qoE+xA1ydnuKpnV8qiqK0LZesIhIXeHeKD7rL4E= X-Google-Smtp-Source: AGHT+IGr0DFuky2FPbQ2Yg3ORfBBHFETbTj1pCq/N1PWQOmJX7z7jGUuciAsT5NfhDFooTRBCD2ImHWREroXcYfnW1s= X-Received: by 2002:a05:6402:518f:b0:5d0:abb8:79d with SMTP id 4fb4d7f45d1cf-5d972e083f8mr544600a12.14.1736293552678; Tue, 07 Jan 2025 15:45:52 -0800 (PST) List-Id: Filesystems List-Archive: https://lists.freebsd.org/archives/freebsd-fs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-fs@FreeBSD.org MIME-Version: 1.0 References: In-Reply-To: From: Rick Macklem Date: Tue, 7 Jan 2025 15:45:37 -0800 X-Gm-Features: AbW1kvZuYgaCRfNPl_pqSR1hq-AxbJK6QeaevH-GAzqqwUCMcBUniCIeq255Ey4 Message-ID: Subject: Re: system stalled, no I/O but 100% CPU from nfs To: "Peter 'PMc' Much" Cc: freebsd-fs@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4YSSNf0lvxz4N8d X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.99 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.995]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20230601]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; TAGGED_FROM(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; TO_DN_SOME(0.00)[]; FROM_HAS_DN(0.00)[]; MISSING_XM_UA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; PREVIOUSLY_DELIVERED(0.00)[freebsd-fs@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; MID_RHS_MATCH_FROMTLD(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; MLMMJ_DEST(0.00)[freebsd-fs@freebsd.org]; RCVD_COUNT_ONE(0.00)[1]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::52a:from] On Mon, Jan 6, 2025 at 8:45=E2=80=AFAM Peter 'PMc' Much wrote: > > On Mon, Jan 06, 2025 at 05:53:38AM -0800, Rick Macklem wrote: > ! On Sun, Jan 5, 2025 at 8:45=E2=80=AFPM Peter 'PMc' Much > ! wrote: > > ! > This doesn't look good. It goes on for hours. What can be done about= it? > ! > (13.4 client & server) > ! > > ! > > ! > 44 processes: 4 running, 39 sleeping, 1 waiting > ! > CPU: 0.4% user, 0.0% nice, 99.6% system, 0.0% interrupt, 0.0% idl= e > ! > Mem: 21M Active, 198M Inact, 1190M Wired, 278M Buf, 3356M Free > ! > ARC: 418M Total, 39M MFU, 327M MRU, 128K Anon, 7462K Header, 43M Othe= r > ! > 332M Compressed, 804M Uncompressed, 2.42:1 Ratio > ! > Swap: 15G Total, 15G Free > ! > > ! > PID USERNAME THR PRI NICE SIZE RES STATE TIME WCPU CO= MMAND > ! > 417 root 4 52 0 12M 2148K RUN 20:55 99.12% nf= scbd > ! Do you have delegations enabled on your server > ! (vfs.nfsd.issue_delegations not 0)? > > Not knowingly: > > # sysctl vfs.nfsd.issue_delegations > vfs.nfsd.issue_delegations: 0 > > ! (If you do not, I have no idea why the server would be doing > ! callbacks, which is what nfscbd > ! handles.) > > Me neither. ;) The cpu being associated with nfscbd might just be a glitch. NFS uses kernel threads and it is hard to know what process they might get associated with for these stats. When you do: # ps axHl it will show the kernel threads. If it happens again, it might turn out that the thread(s) racking up CPU aren't actually doing callacks. rick > > The good news at this point is, it is a single event. At first I > thought the whole cluster got slow (it is always too slow ;) ), but > it was only this node - the others have no cpu consumption on > nfscbd. > > The bad thing is, I cannot remember why I did switch that thing > on. > > ! Also, "nfsstat -m" on the client shows you/us what your mount > ! options are. > > It had to be destroyed, as effects got worse. > > What I figured is: it didn't issue any syscalls, and it didn't > act on kill -9. > Which means: most likely it found an infinite loop inside the > kernel, aka a never-returning syscall. > > ! The above suggests that there is still some activity on the client, but= the > ! info. is limited. > > Yes, it got ever slower. The NFS mount is for /usr/ports, and I did > fix some ports there. At some point a "make clean" would start to > take minutes to complete, and there I noticed something is wrong. > Finally it didn't even echo on the console (I had only one cpu > available, and then when something is stuck within the kernel, all > depends on preemption). > > ! If the client is still in this state, you can collect more info via: > ! # tcpdump -s 0 -w out.pcap host > ! run for a little while. > > I had to destroy it. I tried to run dtrace to pinpoint exactly where > that thing does execute, but it didn't startup. At that point I didn't > consider it feasible to try further investigation. > These are temporary building guests, they get destroyed after > completion anyway. > > So, as apparently it was a single event, I might suggest we just > remember that nfscbd /can do this/ (under yet unclear circumstances) > and otherwise hope for the best. > > And probably I should get rid of that daemon altogether. I think I > read something about these delegations, and it looked suitable for the > usecase, but I didn't realize that it would need to be activated > on the server also. > (The usecase is, a snapshot + clone is created from the ports repo, > then switched to a desired tag/branch, and that filetree is then > used by a single guest, exclusively.) > > > Thanks for Your help! > > cheerio, > PMc From nobody Thu Jan 9 00:39:36 2025 X-Original-To: freebsd-fs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4YT5XY1cNFz5kKV6 for ; Thu, 09 Jan 2025 00:39:57 +0000 (UTC) (envelope-from rick.macklem@gmail.com) Received: from mail-ed1-x52a.google.com (mail-ed1-x52a.google.com [IPv6:2a00:1450:4864:20::52a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YT5XW4Z20z4wf6 for ; Thu, 9 Jan 2025 00:39:55 +0000 (UTC) (envelope-from rick.macklem@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b="c+R/lOL/"; spf=pass (mx1.freebsd.org: domain of rick.macklem@gmail.com designates 2a00:1450:4864:20::52a as permitted sender) smtp.mailfrom=rick.macklem@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-ed1-x52a.google.com with SMTP id 4fb4d7f45d1cf-5d982de9547so522711a12.2 for ; Wed, 08 Jan 2025 16:39:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1736383193; x=1736987993; darn=freebsd.org; h=cc:to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=yAJAVCTkzRDRzN7Gm0MZmL1pkpuctqpePuPNUUzqvaA=; b=c+R/lOL/JwvrUJP7/N/HJjEGXLCub1qIdBaJXlyd7ykBtZ1cvIkJaH1am5sxcjZOR1 xap10yV9Van8mihrbJcjn6KVyca5Zqbi4vbRv+X2zoEfLYOOkMhCrGMl90fp7sAINM5O N7BwBhOu4JiFYB9cifSU009dtrhwpdn7w2USBhhNVO5qtU96G6XTtLv5vXA+J04bmHCR ZDHvD0BrtiUl3+5B2+9P2V52F/Iup8cVhjHQ/vTUc4K6ia3JSHFULei8V0esAo77XOki s2KbbH3xNS0xTdEMtqekco4pX5EtH87EFTRsAaotGl9puG+y0YsU6DmlnDjeH3/+9Lgw Rmyg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1736383193; x=1736987993; h=cc:to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=yAJAVCTkzRDRzN7Gm0MZmL1pkpuctqpePuPNUUzqvaA=; b=gEHPKm+tKrgBdzG6GmPFoRPAHcziag1rh1FHNRa9dRgCCRRuZAYOrOxS64681SYd8T 4gn8gV6LI+cu8vCxKoHPaqRMPWcAabTOGQcTTFxeUYVlyER+9HLjcSMMtyTgxvceBS1F CuBHaA7rqWiLkRJWUgAstEwcbSgMdwlEvPNwnpeQpuTN54ZXnoJ0xIvuG6V41XG7ksIa INoIxJ9OPJbtWUDp3a3WViDlnZ7xcnORMn4H2MQ2GWXlJDXbDOBqdOfFXGP5DUK8bWRf QfKa8/Z9R2dyiJqxDgwNC4QFa+3S5twwNDVfCqDSXRST3KuFlsJ/4u+2+bIRHM0Tud7h mOYA== X-Gm-Message-State: AOJu0YzeVtv6UR48kJrQtuBaFgNeAbdnczk+MYJaWW5t9g6ly109XK/g /t3i0O81KDpX7M4I9stKlrqX2oteLxPinZxQczIQK1uSkoAwR1lenIeYV0MjGwcDNvve8TaE/2E xpRcEorlE3qsmhbneFEsrp5UiRm4+ X-Gm-Gg: ASbGnctHHAPEnZz0bDyb8b/WDxwPI4HWsIrI6+p75myEBl4TdkT1MfY4eGJpBiEwz+c HHqIiVzikbWf+IrmqdzlwevTs9pVk5vEBHmBBNQNpeAwc8/IJzVOtGaswj+MK8knc8UQAat8= X-Google-Smtp-Source: AGHT+IGxx4ronAPB+SfPHxZKCHcyH6l4tp77Zaa5OMzVPQrHaPJOdy2U69tC2tXUL7+q+vW4GqR99b9cKTs5bumUMzA= X-Received: by 2002:a05:6402:400e:b0:5d2:729f:995b with SMTP id 4fb4d7f45d1cf-5d972e479cdmr4311510a12.24.1736383192720; Wed, 08 Jan 2025 16:39:52 -0800 (PST) List-Id: Filesystems List-Archive: https://lists.freebsd.org/archives/freebsd-fs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-fs@FreeBSD.org MIME-Version: 1.0 From: Rick Macklem Date: Wed, 8 Jan 2025 16:39:36 -0800 X-Gm-Features: AbW1kva5isrXh5m_lG_YpJjjZN98t8d0UL3nCTfQO5Kc8CahPxlk1a_6OFTDnh8 Message-ID: Subject: RFC: Marking file system va_filerev style To: Freebsd fs Cc: richard@kojedz.in Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4YT5XW4Z20z4wf6 X-Spamd-Bar: --- X-Spamd-Result: default: False [-4.00 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.999]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20230601]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; TAGGED_FROM(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; TO_DN_SOME(0.00)[]; FROM_HAS_DN(0.00)[]; MISSING_XM_UA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; PREVIOUSLY_DELIVERED(0.00)[freebsd-fs@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; MID_RHS_MATCH_FROMTLD(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; MLMMJ_DEST(0.00)[freebsd-fs@freebsd.org]; RCVD_COUNT_ONE(0.00)[1]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::52a:from] Hi, Back in Sept. Richard reported a problem with a FreeBSD server serving NFSv4 to Linux clients, where the file attributes would get messed up sometimes. (I can't recall if he posted me or a mailing list.) Anyhow, He tried a patch I gave him that told the Linux client that the Change attribute (va_filerev) increments for each change. --> This appears to have fixed the problem. However, this patch should really report what the exported fs does w.r.t. va_filerev and not just guess that it increments it. So, the question is, how do I have file systems report how they generate va_filerev? My current thought is a new MNTK_xxx flag set by the filesystem in its mount point to indicate it increments it upon each change (which is what UFS and ZFS currently does, I think?) Does this sound reasonable? Thanks for any comments, rick From nobody Thu Jan 9 01:36:53 2025 X-Original-To: freebsd-fs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4YT6pP4L7mz5kQYX for ; Thu, 09 Jan 2025 01:37:01 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4YT6pN5BBDz53rH for ; Thu, 9 Jan 2025 01:37:00 +0000 (UTC) (envelope-from kostikbel@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=none; spf=softfail (mx1.freebsd.org: 2001:470:d5e7:1::1 is neither permitted nor denied by domain of kostikbel@gmail.com) smtp.mailfrom=kostikbel@gmail.com; dmarc=fail reason="No valid SPF, No valid DKIM" header.from=gmail.com (policy=none) Received: from tom.home (kib@localhost [127.0.0.1] (may be forged)) by kib.kiev.ua (8.18.1/8.18.1) with ESMTP id 5091ar5B088978; Thu, 9 Jan 2025 03:36:56 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua 5091ar5B088978 Received: (from kostik@localhost) by tom.home (8.18.1/8.18.1/Submit) id 5091ar1C088977; Thu, 9 Jan 2025 03:36:53 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Thu, 9 Jan 2025 03:36:53 +0200 From: Konstantin Belousov To: Rick Macklem Cc: Freebsd fs , richard@kojedz.in Subject: Re: RFC: Marking file system va_filerev style Message-ID: References: List-Id: Filesystems List-Archive: https://lists.freebsd.org/archives/freebsd-fs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-fs@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FORGED_GMAIL_RCVD,FREEMAIL_FROM, NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=4.0.1 X-Spam-Checker-Version: SpamAssassin 4.0.1 (2024-03-26) on tom.home X-Rspamd-Queue-Id: 4YT6pN5BBDz53rH X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.97 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-0.99)[-0.991]; NEURAL_HAM_SHORT(-0.98)[-0.981]; DMARC_POLICY_SOFTFAIL(0.10)[gmail.com : No valid SPF, No valid DKIM,none]; MIME_GOOD(-0.10)[text/plain]; ARC_NA(0.00)[]; TAGGED_RCPT(0.00)[]; ASN(0.00)[asn:6939, ipnet:2001:470::/32, country:US]; MIME_TRACE(0.00)[0:+]; MISSING_XM_UA(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; TO_DN_SOME(0.00)[]; HAS_XAW(0.00)[]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; R_SPF_SOFTFAIL(0.00)[~all:c]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; FREEMAIL_TO(0.00)[gmail.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_TLS_LAST(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; MLMMJ_DEST(0.00)[freebsd-fs@freebsd.org]; RCPT_COUNT_THREE(0.00)[3] On Wed, Jan 08, 2025 at 04:39:36PM -0800, Rick Macklem wrote: > Hi, > > Back in Sept. Richard reported a problem with a > FreeBSD server serving NFSv4 to Linux clients, > where the file attributes would get messed up > sometimes. (I can't recall if he posted me or a mailing > list.) > > Anyhow, He tried a patch I gave him that told the > Linux client that the Change attribute (va_filerev) > increments for each change. > --> This appears to have fixed the problem. > > However, this patch should really report what the > exported fs does w.r.t. va_filerev and not just guess > that it increments it. > > So, the question is, how do I have file systems report > how they generate va_filerev? > My current thought is a new MNTK_xxx flag set by > the filesystem in its mount point to indicate it increments > it upon each change (which is what UFS and ZFS currently > does, I think?) > > Does this sound reasonable? Is this a per-mount property, or a generic filesystem-type property (for me, the nature of the indicated feature tends to mean per-type). Then it might be that a VFCF_ flag is the more natural solution than MNTK_ one. From nobody Thu Jan 9 01:45:47 2025 X-Original-To: freebsd-fs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4YT70s44myz5kQvW for ; Thu, 09 Jan 2025 01:46:05 +0000 (UTC) (envelope-from rick.macklem@gmail.com) Received: from mail-ed1-x535.google.com (mail-ed1-x535.google.com [IPv6:2a00:1450:4864:20::535]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YT70s145zz54bS for ; Thu, 9 Jan 2025 01:46:05 +0000 (UTC) (envelope-from rick.macklem@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ed1-x535.google.com with SMTP id 4fb4d7f45d1cf-5d7e3f1fc01so623604a12.2 for ; Wed, 08 Jan 2025 17:46:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1736387164; x=1736991964; darn=freebsd.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=czZUTHGcfC4o31lkJR0PQwhPJ2dTyi9nXRZict2FhEU=; b=jUEO9CWXMup3bQBlZJYgkdzBANqOmu8/P12PlWpCVMGuh7w0Kdfipq2vjEm0HAnkk9 hLAg6xKV03fgQOnN6nZpXaLIPz857ARdlu7N+IxbFQ74JRIiq1ON/dUNWR/shA2CX4+I WiOzShBAOD8kiBKEjzSmkD+izBhxuWpT6dFs7himXZs8RPsQ2Amst+MIdmlyU7Se9zYo GlBOjkmQcNvpMPY7IaqptGxcU57B71Wjeq13sEsfoH+tC8DTSb6SJH4YWynUUWeIf/Rt lW2OQBedy8MRmGjN9prhvdQ5fhHWSjJDLi8b9biEntwRJOtruuw+JVeHbfSh+f3gioOQ CwRQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1736387164; x=1736991964; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=czZUTHGcfC4o31lkJR0PQwhPJ2dTyi9nXRZict2FhEU=; b=A+B90hPya2pNG8p9w1qLElyR1ZJk0RUfL4CEimsmzpoxV1wMeqbJ2bKPoMGQJjCVd1 2WpoHLxo3mbleA7HwZRmLkxfHcgErsPBTUu2Tux7Rbn91HZoOjJEy6Z+SkuiqRGqWPeX j4piXpPfLwSNmppJI9fbp/kt9zimhFHkXVnuNymWVq5TFPRIwvXYfsXfEG04vRCxeZbo kZlpK0yo3gDC6ZQPNdZgNn70MSHOVOu4HJ8NPEK33LoNR3r7OTdg+8xtxY4ednONof8O wu/KaJiV7ErcoLwynf4zSGoTDZreRyZ231uYpD1/7Q/d+4qkEsuaKjVfuCDMeYgdzrd4 hKgg== X-Gm-Message-State: AOJu0YynScs9JhiNV3VMeWB3ZwjoKc+C8EWRI6N7QG+4Fb4J9m4XVN6Y dGj1N4YrQ5lV15E3qS5Bdh5p3E9iU18o61j1ikmjoEeFqbq6GMUd7WIa0t1KL1H9/qs2yZrOqDc 76FjzMtN24RLPX59TJpFOqinDnA== X-Gm-Gg: ASbGncuOhKd8D9oxlUUcbom9brHv+EbwfqyJEoiaVXg4WFjXO/CfMPJHPhocnVmqmTu zGzfDcv002BtMWefAOxdl5YVQW/qteYQWydwM9FgzK3PFnSVfG3/HHZw2P/ygig2dSUjNTXE= X-Google-Smtp-Source: AGHT+IFHuOi1l3kxbaEJrk2tEMsLfaS9u3MhRH8qte2QJXz5rXYKWhzjaDCeq3Vzo508UsyLsv7Tt9vXd8fB0xQaxT4= X-Received: by 2002:a05:6402:5243:b0:5d3:ce7f:ac05 with SMTP id 4fb4d7f45d1cf-5d972e6e675mr4128105a12.31.1736387163682; Wed, 08 Jan 2025 17:46:03 -0800 (PST) List-Id: Filesystems List-Archive: https://lists.freebsd.org/archives/freebsd-fs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-fs@FreeBSD.org MIME-Version: 1.0 References: In-Reply-To: From: Rick Macklem Date: Wed, 8 Jan 2025 17:45:47 -0800 X-Gm-Features: AbW1kvZO42xl3VHaMFsPtnkI19O0d2zkTaEo_c0peCdoXJUh3AP4ElzI_fnW5_o Message-ID: Subject: Re: RFC: Marking file system va_filerev style To: Konstantin Belousov Cc: Freebsd fs , richard@kojedz.in Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4YT70s145zz54bS X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; TAGGED_FROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] On Wed, Jan 8, 2025 at 5:37=E2=80=AFPM Konstantin Belousov wrote: > > On Wed, Jan 08, 2025 at 04:39:36PM -0800, Rick Macklem wrote: > > Hi, > > > > Back in Sept. Richard reported a problem with a > > FreeBSD server serving NFSv4 to Linux clients, > > where the file attributes would get messed up > > sometimes. (I can't recall if he posted me or a mailing > > list.) > > > > Anyhow, He tried a patch I gave him that told the > > Linux client that the Change attribute (va_filerev) > > increments for each change. > > --> This appears to have fixed the problem. > > > > However, this patch should really report what the > > exported fs does w.r.t. va_filerev and not just guess > > that it increments it. > > > > So, the question is, how do I have file systems report > > how they generate va_filerev? > > My current thought is a new MNTK_xxx flag set by > > the filesystem in its mount point to indicate it increments > > it upon each change (which is what UFS and ZFS currently > > does, I think?) > > > > Does this sound reasonable? > > Is this a per-mount property, or a generic filesystem-type property (for > me, the nature of the indicated feature tends to mean per-type). Then > it might be that a VFCF_ flag is the more natural solution than MNTK_ one= . > Yes, it is a file system property. Thanks for the suggestion. (I'll come up with a patch and put it on phabricator.) Thanks, rick From nobody Fri Jan 10 14:13:08 2025 X-Original-To: fs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4YV3XQ6DBhz5kPMF for ; Fri, 10 Jan 2025 14:13:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YV3XQ2JDNz4pSw for ; Fri, 10 Jan 2025 14:13:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1736518390; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=qSrNSDMeeHljWHY533ENdb1aqIHnG4HDMG+f5ZcbNMM=; b=nMlQen7VnObl1xy+F5EhQA94zWcctQx/XZfBR532+1mWGj6qsoQ9hHYNzLwYzqw7OT5Nt1 iDA3Hc5muaIb26wHUAmgpccKlV41vwddmrngCpShjqySv8TmxjJyxRbge9Y7NwjLH6D27b 6yVvKhp1AAbhwBHvKVj2HTGkdewOwQvqGS/9DTuwUsieX6V/u/uwXJxHKdP4+I7dzadujM zo+KC8qhxWepGlqSUAuDg0cJWk8elWIt8gmx0ItDJY/z/ykjguHi/wzQnHbZ3SbWBdtZKJ QvAywSdG/dNPW085vOIKqVJ5Yc1ZvkWHL34VnlUZpQCWFYJkKilnDRysdlt1+Q== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1736518390; a=rsa-sha256; cv=none; b=m0CfyG2+fPMSOqo+ypR0oikQp13akTtpJLQmXNEpVeHP3v8E1rbwkklxcR28d9pJdciQbK QdbWqEGTJy2Lg34vBt0wSfGk7d05JOS1vlSv+F5KJYJyKVJfuh5vwivBEQiD6hpsA15vsN psuTTGZya3tPlAIk1P4O2+2j0ux0io19YQ4GZI+zAsprBDqXdUPOdUS+QRHXMPUeCvyF6Q bYkIBNh/3v0gQ18h9gSqZukkS/SIMIEeufeiRDJhXebItiLvrilEcRwyEvHQPcAhaamVqa t1LRo7psISKItQIPGbT1o8hB7Usvabx1gSJ2JRwrWXbO++krYs8gd5iiDAyepA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4YV3XQ1w05z19V for ; Fri, 10 Jan 2025 14:13:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 50AEDAjl028004 for ; Fri, 10 Jan 2025 14:13:10 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 50AEDAHf028003 for fs@FreeBSD.org; Fri, 10 Jan 2025 14:13:10 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 267028] kernel panics when booting with both (zfs,ko or vboxnetflt,ko or acpi_wmi.ko) and amdgpu.ko Date: Fri, 10 Jan 2025 14:13:08 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 13.1-RELEASE X-Bugzilla-Keywords: crash, needs-qa X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: george@m5p.com X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Filesystems List-Archive: https://lists.freebsd.org/archives/freebsd-fs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-fs@FreeBSD.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D267028 --- Comment #352 from George Mitchell --- So far, this problem has not recurred since my upgrades at the beginning of= the year. But I have been rebuilding ALL my ports for 14.2-RELEASE and I haven= 't had a chance to try really stressing my system out. But when I get that chance, it seems likely I will close this as "overcome by events." --=20 You are receiving this mail because: You are on the CC list for the bug.= From nobody Fri Jan 10 15:11:53 2025 X-Original-To: fs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4YV4r95b2Kz5kTnB for ; Fri, 10 Jan 2025 15:11:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YV4r93VZCz542K for ; Fri, 10 Jan 2025 15:11:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1736521913; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=2rZMUge0WTOGedHs2Etiq/RapdwWY5y3qP68hzHOoQ0=; b=bi1IjVp24k6Oh/skA+SJT6R6qwpwsG2BxD0tDHcFs5tLI4zP8ib6muTvhA79U9vj/RzdEu S1EDjC9Elv4BuBW8uTt/UAc+XFvTDwD/xqKcm6Q407tFO5XS0wsXnnyhj2PkrX9H8+xbCu huIhx7KzsDvDGGLstIDm47aWxA5S5VOcXCfNrJYWLmRKpKXXnH2F9dl566efLNSQWvG0CW M+G15QyzF/FlRO2JfEgtuFNE5X/YnvOh92x/pajmKBHDlNXmfymZ/vgxbVWsAAwvYF9kmr mZluynef/pyYVauiTxQbEYezOeS++hw5znk3Em3RivxpM3aZFSGlwRmZEpkOsg== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1736521913; a=rsa-sha256; cv=none; b=bWh0R1TOCNUNbEIt2GZG0bfvjDU4ImzYgDe51+GzryRumDXOCOcyFJhwXhB/6+flZ/qTxi 1fbEPSwx9SrnhB0EKOhT7Im4POCODBizR4UJYuuechR/0SR4v0V5sac4PsrR77YxnXaSph SHev4P+OS3SZABBmtZYtfNakwAPi8FCH3xTaJBGCEurpwhgu/E++yyQm/ykwoBEiMHcZaX wxwl4uYHxBt1d9KyD52hPt+LydSs/IedM0MFOyCQJtfKWpIBMvBbOeTQ1df+9ORNBsDLk7 KBerIzDDBCtKgICfuc04OfBvVYpn8hmRcxCm/+XSpUO9H/UyDlhwREuxD2XT6w== ARC-Authentication-Results: i=1; mx1.freebsd.org; none Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4YV4r936Lfz2KH for ; Fri, 10 Jan 2025 15:11:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 50AFBr6h022759 for ; Fri, 10 Jan 2025 15:11:53 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 50AFBrIx022758 for fs@FreeBSD.org; Fri, 10 Jan 2025 15:11:53 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 280500] raidz expansion causes panic Date: Fri, 10 Jan 2025 15:11:53 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 15.0-CURRENT X-Bugzilla-Keywords: crash X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: markj@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Filesystems List-Archive: https://lists.freebsd.org/archives/freebsd-fs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-fs@FreeBSD.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D280500 --- Comment #3 from Mark Johnston --- Should be fixed by https://github.com/openzfs/zfs/pull/16942 --=20 You are receiving this mail because: You are the assignee for the bug.= From nobody Fri Jan 10 18:52:43 2025 X-Original-To: freebsd-fs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4YV9l82Qp0z5kL6w for ; Fri, 10 Jan 2025 18:52:52 +0000 (UTC) (envelope-from andy@time-domain.co.uk) Received: from mail0.time-domain.net (mail0.time-domain.net [62.3.122.138]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4YV9l73pkHz4JXw for ; Fri, 10 Jan 2025 18:52:51 +0000 (UTC) (envelope-from andy@time-domain.co.uk) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of andy@time-domain.co.uk designates 62.3.122.138 as permitted sender) smtp.mailfrom=andy@time-domain.co.uk; dmarc=none Received: from mail0.time-domain.net (localhost [127.0.0.1]) by mail0.time-domain.net (8.15.2/8.15.2) with ESMTP id 50AIqhNS055955 for ; Fri, 10 Jan 2025 18:52:44 GMT (envelope-from andy@time-domain.co.uk) Received: from localhost (andy-tds@localhost) by mail0.time-domain.net (8.15.2/8.15.2/Submit) with ESMTP id 50AIqhdx055952 for ; Fri, 10 Jan 2025 18:52:43 GMT (envelope-from andy@time-domain.co.uk) X-Authentication-Warning: mail0.time-domain.net: andy-tds owned process doing -bs Date: Fri, 10 Jan 2025 18:52:43 +0000 (GMT) From: andy thomas X-X-Sender: andy-tds@mail0.time-domain.net To: freebsd-fs@freebsd.org Subject: How can I tell when ZFS has finished creating a snapshot? Message-ID: User-Agent: Alpine 2.22 (BSF 395 2020-01-19) List-Id: Filesystems List-Archive: https://lists.freebsd.org/archives/freebsd-fs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-fs@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset=US-ASCII X-Rspamd-Queue-Id: 4YV9l73pkHz4JXw X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.16 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.86)[-0.863]; R_SPF_ALLOW(-0.20)[+ip4:62.3.122.136/29]; MIME_GOOD(-0.10)[text/plain]; ASN(0.00)[asn:13037, ipnet:62.3.64.0/18, country:GB]; MIME_TRACE(0.00)[0:+]; RCPT_COUNT_ONE(0.00)[1]; R_DKIM_NA(0.00)[]; FREEFALL_USER(0.00)[andy]; MLMMJ_DEST(0.00)[freebsd-fs@freebsd.org]; HAS_XAW(0.00)[]; RCVD_TLS_LAST(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; DMARC_NA(0.00)[time-domain.co.uk]; RCVD_COUNT_TWO(0.00)[2]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-fs@freebsd.org]; ARC_NA(0.00)[] Is there any way I can find out when a ZFS snapshot has completed and can be used, say, for replicating to another server? Using the 'zfs snapshot -r ...' command, the command prompt re-appears almost immediately suggesting the command has completed and using the 'zfs list -t snapshot' command the 'USED' column will initially report zero and then it will slowly grow over the next few hours. But it seems to take a long time with no zfs-related processes being reported by 'ps ax'. For example, after 3 hours, a snapshot of a 80TB raidz1 pool with only a little over 3 TB used has reported 17.4MB used: NAME USED AVAIL REFER MOUNTPOINT clustor2/ma@2025-01-10_14.45.00 17.4M - 3.09T - but over the next hour, this 17.4MB usage figure has not increased at all. So I don't know whether to wait another few hours before using 'zfs send' or 'zxfer' to copy the snapshot to a backup server, or whether the snapshot has in fact finished. Is there a way to find out the status of a snapshot creation? Thanks in advance for any suggestions, Andy From nobody Fri Jan 10 19:00:28 2025 X-Original-To: freebsd-fs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4YV9tD2HVmz5kLsF for ; Fri, 10 Jan 2025 18:59:00 +0000 (UTC) (envelope-from heas@shrubbery.net) Received: from sea.shrubbery.net (sea.shrubbery.net [129.250.47.99]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4YV9tC6zQbz4Kb5 for ; Fri, 10 Jan 2025 18:58:59 +0000 (UTC) (envelope-from heas@shrubbery.net) Authentication-Results: mx1.freebsd.org; none Received: by sea.shrubbery.net (Postfix, from userid 7053) id C3268196233; Fri, 10 Jan 2025 19:00:28 +0000 (UTC) Date: Fri, 10 Jan 2025 19:00:28 +0000 From: heasley To: andy thomas Cc: freebsd-fs@freebsd.org Subject: Re: How can I tell when ZFS has finished creating a snapshot? Message-ID: References: List-Id: Filesystems List-Archive: https://lists.freebsd.org/archives/freebsd-fs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-fs@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-PGPkey: http://www.shrubbery.net/~heas/public-key.asc X-note: live free, or die! X-homer: i just want to have a beer while i am caring. X-Claimation: an engineer needs a manager like a fish needs a bicycle X-reality: only YOU can put an end to the embarrassment that is Tom Cruise X-Rspamd-Queue-Id: 4YV9tC6zQbz4Kb5 X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:2914, ipnet:129.250.0.0/16, country:US] Fri, Jan 10, 2025 at 06:52:43PM +0000, andy thomas: > Is there a way to find out the status of a snapshot creation? it should be near-instantaneous. "USED" would only change if files in the snapshot are deleted or overwritten. From nobody Fri Jan 10 19:01:26 2025 X-Original-To: freebsd-fs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4YV9xm73VBz5kMVR for ; Fri, 10 Jan 2025 19:02:04 +0000 (UTC) (envelope-from karl@denninger.net) Received: from colo1.denninger.net (colo1.denninger.net [104.236.120.189]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4YV9xl2KH5z4LMR for ; Fri, 10 Jan 2025 19:02:03 +0000 (UTC) (envelope-from karl@denninger.net) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of karl@denninger.net designates 104.236.120.189 as permitted sender) smtp.mailfrom=karl@denninger.net; dmarc=pass (policy=none) header.from=denninger.net Received: from denninger.net (syn-071-015-252-132.res.spectrum.com [71.15.252.132]) by colo1.denninger.net (Postfix) with ESMTP id 061EC2110FB for ; Fri, 10 Jan 2025 14:01:32 -0500 (EST) Received: from [192.168.10.23] (D13.Denninger.Net [192.168.10.23]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by denninger.net (Postfix) with ESMTPSA id BE97E163A1D for ; Fri, 10 Jan 2025 14:01:26 -0500 (EST) Message-ID: <44c10641-8f1b-476f-ba5b-29d4a5f28c9c@denninger.net> Date: Fri, 10 Jan 2025 14:01:26 -0500 List-Id: Filesystems List-Archive: https://lists.freebsd.org/archives/freebsd-fs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-fs@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: How can I tell when ZFS has finished creating a snapshot? To: freebsd-fs@freebsd.org References: Content-Language: en-US From: Karl Denninger In-Reply-To: Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-512; boundary="------------ms070504040700060209050308" X-Rspamd-Queue-Id: 4YV9xl2KH5z4LMR X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.78 / 15.00]; SIGNED_SMIME(-2.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_SHORT(-0.99)[-0.992]; DMARC_POLICY_ALLOW(-0.50)[denninger.net,none]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.20)[multipart/signed,multipart/alternative,text/plain]; MIME_BASE64_TEXT(0.10)[]; XM_UA_NO_VERSION(0.01)[]; RCVD_TLS_LAST(0.00)[]; HAS_ATTACHMENT(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; ARC_NA(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FREEFALL_USER(0.00)[karl]; RCVD_VIA_SMTP_AUTH(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:+,3:~,4:~]; TO_DN_NONE(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:14061, ipnet:104.236.64.0/18, country:US]; PREVIOUSLY_DELIVERED(0.00)[freebsd-fs@freebsd.org]; R_DKIM_NA(0.00)[]; MLMMJ_DEST(0.00)[freebsd-fs@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[] This is a cryptographically signed message in MIME format. --------------ms070504040700060209050308 Content-Type: multipart/alternative; boundary="------------oTzI0uyimmQ3WPJKa25I3gcU" --------------oTzI0uyimmQ3WPJKa25I3gcU Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: base64 DQpPbiAxLzEwLzIwMjUgMTo1MiBQTSwgYW5keSB0aG9tYXMgd3JvdGU6DQo+IElzIHRoZXJl IGFueSB3YXkgSSBjYW4gZmluZCBvdXQgd2hlbiBhIFpGUyBzbmFwc2hvdCBoYXMgY29tcGxl dGVkIGFuZCANCj4gY2FuIGJlIHVzZWQsIHNheSwgZm9yIHJlcGxpY2F0aW5nIHRvIGFub3Ro ZXIgc2VydmVyPw0KPg0KPiBVc2luZyB0aGUgJ3pmcyBzbmFwc2hvdCAtciAuLi4nIGNvbW1h bmQsIHRoZSBjb21tYW5kIHByb21wdCByZS1hcHBlYXJzIA0KPiBhbG1vc3QgaW1tZWRpYXRl bHkgc3VnZ2VzdGluZyB0aGUgY29tbWFuZCBoYXMgY29tcGxldGVkIGFuZCB1c2luZyB0aGUg DQo+ICd6ZnMgbGlzdCAtdCBzbmFwc2hvdCcgY29tbWFuZCB0aGUgJ1VTRUQnIGNvbHVtbiB3 aWxsIGluaXRpYWxseSByZXBvcnQgDQo+IHplcm8gYW5kIHRoZW4gaXQgd2lsbCBzbG93bHkg Z3JvdyBvdmVyIHRoZSBuZXh0IGZldyBob3Vycy4gQnV0IGl0IA0KPiBzZWVtcyB0byB0YWtl IGEgbG9uZyB0aW1lIHdpdGggbm8gemZzLXJlbGF0ZWQgcHJvY2Vzc2VzIGJlaW5nIHJlcG9y dGVkIA0KPiBieSAncHMgYXgnLiBGb3IgZXhhbXBsZSwgYWZ0ZXIgMyBob3VycywgYSBzbmFw c2hvdCBvZiBhIDgwVEIgcmFpZHoxIA0KPiBwb29sIHdpdGggb25seSBhIGxpdHRsZSBvdmVy IDMgVEIgdXNlZCBoYXMgcmVwb3J0ZWQgMTcuNE1CIHVzZWQ6DQo+DQo+IMKgwqDCoMKgTkFN RcKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC oMKgwqAgVVNFRMKgIEFWQUlMwqAgUkVGRVIgTU9VTlRQT0lOVA0KPiBjbHVzdG9yMi9tYUAy MDI1LTAxLTEwXzE0LjQ1LjAwwqAgMTcuNE3CoMKgwqDCoMKgIC3CoCAzLjA5VMKgIC0NCj4N Cj4gYnV0IG92ZXIgdGhlIG5leHQgaG91ciwgdGhpcyAxNy40TUIgdXNhZ2UgZmlndXJlIGhh cyBub3QgaW5jcmVhc2VkIGF0IA0KPiBhbGwuIFNvIEkgZG9uJ3Qga25vdyB3aGV0aGVyIHRv IHdhaXQgYW5vdGhlciBmZXcgaG91cnMgYmVmb3JlIHVzaW5nIA0KPiAnemZzIHNlbmQnIG9y ICd6eGZlcicgdG8gY29weSB0aGUgc25hcHNob3QgdG8gYSBiYWNrdXAgc2VydmVyLCBvciAN Cj4gd2hldGhlciB0aGUgc25hcHNob3QgaGFzIGluIGZhY3QgZmluaXNoZWQuDQo+DQo+IElz IHRoZXJlIGEgd2F5IHRvIGZpbmQgb3V0IHRoZSBzdGF0dXMgb2YgYSBzbmFwc2hvdCBjcmVh dGlvbj8NCj4NCj4gVGhhbmtzIGluIGFkdmFuY2UgZm9yIGFueSBzdWdnZXN0aW9ucywNCg0K VGhlIHNuYXBzaG90IGlzIGNvbXBsZXRlIHdoZW4gdGhlIGNvbW1hbmQgcmV0dXJucyAtLSB3 aXRoaW4gdGhlIA0KZmlsZXN5c3RlbSBhIHNuYXBzaG90IGlzIGFuIGF0b21pYyBvcGVyYXRp b24uDQoNCi9PbmNlIG1hZGUgYWxsIHdyaXRlcyB0byB0aGF0IGZpbGVzeXN0ZW0gYXJlIGNv cHktb24td3JpdGUgL3NvIGFzIHRpbWUgDQpnb2VzIG9uIHRoZSAiVXNlZCIgYW1vdW50IGlu Y3JlYXNlcyAoYW5kIHRoZSBmcmVlIHNwYWNlIGdvZXMgZG93biBieSBhbiANCmVxdWFsIGFt b3VudCkgYmVjYXVzZSBlYWNoIGJsb2NrIHRoYXQgaXMgbW9kaWZpZWQgKGFuZCBvbmx5IHRo YXQgYmxvY2spIA0KaXMgY29waWVkLg0KDQotLSANCkthcmwgRGVubmluZ2VyDQprYXJsQGRl bm5pbmdlci5uZXQNCi9UaGUgTWFya2V0IFRpY2tlci8NCi9bUy9NSU1FIGVuY3J5cHRlZCBl bWFpbCBwcmVmZXJyZWRdLw0K --------------oTzI0uyimmQ3WPJKa25I3gcU Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On 1/10/2025 1:52 PM, andy thomas wrote:
Is there any way I can find out when a ZFS snapshot has completed and can be used, say, for replicating to another server?

Using the 'zfs snapshot -r ...' command, the command prompt re-appears almost immediately suggesting the command has completed and using the 'zfs list -t snapshot' command the 'USED' column will initially report zero and then it will slowly grow over the next few hours. But it seems to take a long time with no zfs-related processes being reported by 'ps ax'. For example, after 3 hours, a snapshot of a 80TB raidz1 pool with only a little over 3 TB used has reported 17.4MB used:

=C2=A0=C2=A0=C2=A0=C2=A0NAME=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 USED=C2=A0 A= VAIL=C2=A0 REFER=C2=A0 MOUNTPOINT
=C2=A0=C2=A0=C2=A0=C2=A0clustor2/ma@2025-01-10_14.45.00<= /a>=C2=A0 17.4M=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 -=C2=A0 3.09T=C2=A0 -

but over the next hour, this 17.4MB usage figure has not increased at all. So I don't know whether to wait another few hours before using 'zfs send' or 'zxfer' to copy the snapshot to a backup server, or whether the snapshot has in fact finished.

Is there a way to find out the status of a snapshot creation?

Thanks in advance for any suggestions,

The snapshot is complete when the command returns -- within the filesystem a snapshot is an atomic operation.

Once made all writes to that filesystem are copy-on-write s= o as time goes on the "Used" amount increases (and the free space goes down by an equal amount) because each block that is modified (and only that block) is copied.

--
Karl Denninger
karl@denninger.net
The Market Ticker
[S/MIME encrypted email preferred]<= /div> --------------oTzI0uyimmQ3WPJKa25I3gcU-- --------------ms070504040700060209050308 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgMFADCABgkqhkiG9w0BBwEAAKCC C4owggWZMIIDgaADAgECAhRZU8dKdMneRI1Vq5kv0k54Q5rQuDANBgkqhkiG9w0BAQsFADB2 MQswCQYDVQQGEwJVUzESMBAGA1UECAwJVGVubmVzc2VlMRYwFAYDVQQKDA1EZW5uaW5nZXIu TmV0MRcwFQYDVQQDDA5EZW5uaW5nZXIgUm9vdDEiMCAGCSqGSIb3DQEJARYTYWRtaW5AZGVu bmluZ2VyLm5ldDAeFw0yNDA1MDkyMTA4MDNaFw00NDA1MDQyMTA4MDNaMF0xCzAJBgNVBAYT AlVTMRIwEAYDVQQIDAlUZW5uZXNzZWUxFjAUBgNVBAoMDURlbm5pbmdlci5uZXQxIjAgBgNV BAMMGURlbm5pbmdlci5OZXQgU2lnbmluZyBJbnQwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAw ggEKAoIBAQDbR0tSiuLG5HPfo+cWtdeYQ8jc8Bjfuo0GTcNRT0glHnH1apUtInIktUknEZDH ohahInN+mMBdKg54FCHOiYZrJbyxBIo9FwX7hRmOc+spxmSYWnOd2E/YcGInMK4ZpjPzldzB Yt1n3zygkhx2bssxTJS3x4nv1qAXfLSZd1VwqoQufifEoPyTtymkkvHLv86vLgqAqooM/cXc 4LSIQ5u2uM308n42r8RkKtp7X1v9fJW8oRZN2XnFZtiUPH44YY2rHqyN2Hea9Y3+TXbldXjo xhPHTA+JYVFq8KTmbQBqU7YcMhlIG0cSxPeFLMxnP6pqPcIVTAlK+a6YGRFppfjZAgMBAAGj ggE2MIIBMjAdBgNVHQ4EFgQUH+VuxXhBxaJAQrvDekwkH91hBi4wgbMGA1UdIwSBqzCBqIAU RFYC4p6L6KITnEvrpx2cyt+PcMmheqR4MHYxCzAJBgNVBAYTAlVTMRIwEAYDVQQIDAlUZW5u ZXNzZWUxFjAUBgNVBAoMDURlbm5pbmdlci5OZXQxFzAVBgNVBAMMDkRlbm5pbmdlciBSb290 MSIwIAYJKoZIhvcNAQkBFhNhZG1pbkBkZW5uaW5nZXIubmV0ghQZE7NBItWtQsCouuwU6jZ+ HPPwnjAPBgNVHRMBAf8EBTADAQH/MA4GA1UdDwEB/wQEAwIBBjA6BgNVHR8EMzAxMC+gLaAr hilodHRwOi8vd3d3LmRlbm5pbmdlci5uZXQvcm9vdC1yZXZva2VkLmNybDANBgkqhkiG9w0B AQsFAAOCAgEAfFbhPc82AfhyUqONs7IccYD36w+OP4nQgwfC4IWf3y/aQAZ2Zk6IITzYqwf7 PFM0bJRT3zi7xyetolqHDhfMJvnOQWpITZiyM/FSKwIvuBsy/uJUqPuqui4XQMYoSbAA1qmI MW/z7VZZHwaRFoeWE40UirYcf0fNcooBZ72bmd+iBaVyjtZvky0Vgcz0eC6e6LR5kNb23yC6 TkyQIlGyQkK5/afXUYFzk49rOHVbVyxW3oXRfq8Ow6HCrpDGAS8p84S04MFwBVAUfbe4aXs3 bampaI2LzKgkVywyFP14LSvvdjCfLYfnLy1Z9hm2EHMqNHA2tCGdRhWp2d7aZC1MYFqng0ZS fjPJjqHrI1qPU0p6k9A1GxAtrQlL2v/IUzUnMZkiawFV3qlxMGZf/kTYTUOcJhx1KU4zSLHu 80qO7ldRpp5gHssCAGFbeTu2gp6LxfmaFhLPDBJ1VGfdPx9lUrU/9OcoHczcl5x2Rb8IUZyX 9elzP5WdAU8p5R/DLlOAq24VcabhFtYBCA2dOESLupSfWKNQuJCN/1gz7ysSc+mjnnPV77IO mpszJfkFFJEDNJlGIVKX1vwwygtC/9Ulox8frgbZlRAYAgDc/YbOBFxticVVre0Y3Ujx6Kzb tkgZRlgfdZWbT1W5smncqJxg5qAL8e/yTb3fCe2nJ0jhiP4wggXpMIIE0aADAgECAhMAmNFt CiCF3j+FwQLYtBTmGjzkMA0GCSqGSIb3DQEBCwUAMF0xCzAJBgNVBAYTAlVTMRIwEAYDVQQI DAlUZW5uZXNzZWUxFjAUBgNVBAoMDURlbm5pbmdlci5uZXQxIjAgBgNVBAMMGURlbm5pbmdl ci5OZXQgU2lnbmluZyBJbnQwHhcNMjQwNTEwMTkyNjU5WhcNMjkwNTA5MTkyNjU5WjBXMQsw CQYDVQQGEwJVUzESMBAGA1UECAwJVGVubmVzc2VlMRcwFQYDVQQKDA5LYXJsIERlbm5pbmdl cjEbMBkGA1UEAwwSa2FybEBkZW5uaW5nZXIubmV0MIICIjANBgkqhkiG9w0BAQEFAAOCAg8A MIICCgKCAgEAvh1UssVbSYctzobPjwBkbjv/w4WvQNepeRTwE6+sLnXvc41+X9pa5EclPL4Q l02Vu1m71mSqXGfK9HbWZoivbhefBHOoYb35MSc24PelhwcORbpneWoWc7giQ7QgFlvEe/yj fs8M0H9fgdzFS5m2lwBQbis8kioSjHB2yt/8I1GE4Mvt1Cur9kga6ML5FAQvo8TYN1stdhrE 13FEv/BWCF4FVT4H2Wa2ySW+R1jkKb74SC6Twg98bGCRTShD5bVylh0+0LXNhzaopIDcI/KK jm/j3mRjIlmqbGrSpvJsbjjhjhAYQKE1U8FB5TDU4OkFAibblhQit/KjgspPR2o/vOpVFPER uhZEV1oDGzUJtZlkREIcN2sYBi0p7Y4585ya+b7L10mEenPlyi3eSkGXEuiy/BR2DY6lShwW DPoQ5602TKmttCSwBdWGoLrQ4jEVEVNt4lku2wPbTHF3KpHJU0g7RbcWoUYn10SOxKathkir hF3v9U32+QhPELGwqRrH0sL9rWf0qalRtPDHUYl8TebZmYkFqNeSMlqHijl5f4SsQPSj7gx5 4F19Ntm9ZcvuWTmW8QQGWTKHeMuG+BYkVIUSPe6/ZQsbD/xDx7rkyGfNgWIa4W7Wm/B7kaNq H53tk3wFmNgZQOxMTPF0oTHfW0T2azU6JD0D1AlgoAnSAE0CAwEAAaOCAaYwggGiMDoGCCsG AQUFBwEBBC4wLDAqBggrBgEFBQcwAYYeaHR0cDovL29jc3AuZGVubmluZ2VyLm5ldDo3Nzc3 MAwGA1UdEwEB/wQCMAAwDgYDVR0PAQH/BAQDAgXgMB0GA1UdJQQWMBQGCCsGAQUFBwMCBggr BgEFBQcDBDAzBglghkgBhvhCAQ0EJhYkT3BlblNTTCBHZW5lcmF0ZWQgQ2xpZW50IENlcnRp ZmljYXRlMB0GA1UdDgQWBBSxJZjVnlYLAT3uzvDYgc4742J6UTCBswYDVR0jBIGrMIGogBQf 5W7FeEHFokBCu8N6TCQf3WEGLqF6pHgwdjELMAkGA1UEBhMCVVMxEjAQBgNVBAgMCVRlbm5l c3NlZTEWMBQGA1UECgwNRGVubmluZ2VyLk5ldDEXMBUGA1UEAwwORGVubmluZ2VyIFJvb3Qx IjAgBgkqhkiG9w0BCQEWE2FkbWluQGRlbm5pbmdlci5uZXSCFFlTx0p0yd5EjVWrmS/STnhD mtC4MB0GA1UdEQQWMBSBEmthcmxAZGVubmluZ2VyLm5ldDANBgkqhkiG9w0BAQsFAAOCAQEA TrQ45/tBN3SiuqItFv/V+CF3h7Hxe0YLsL+A/P+q9ZhxIscaNjaclgQhPA+rUr+l8DGoXJ/w yAl1E0SSBK+9phIc/9xFOBg3rCy4ngubzP+lHS1t03nMCBSUNsu5qPzqLBPiKaPabUu3Gr9o koRezSszgM3/zNJfr8cMO93csCK/fBccsMx5q+3nxB5XeT7UciicjfEzUA4m2mQxBmGk9SSU 147Gy8UmdSq57Tw82KqUrQ1pJ6IOzVPLREpwlqGbHykSU3MwtPYPtfQeFVjvO/XcWvoFQjbV UyhzAqMMYFudxoVLlJQiAgU38OScTLDgKxCO41h7VOjb2mss0zHndzGCBZUwggWRAgEBMHQw XTELMAkGA1UEBhMCVVMxEjAQBgNVBAgMCVRlbm5lc3NlZTEWMBQGA1UECgwNRGVubmluZ2Vy Lm5ldDEiMCAGA1UEAwwZRGVubmluZ2VyLk5ldCBTaWduaW5nIEludAITAJjRbQoghd4/hcEC 2LQU5ho85DANBglghkgBZQMEAgMFAKCCAvIwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAc BgkqhkiG9w0BCQUxDxcNMjUwMTEwMTkwMTI2WjBPBgkqhkiG9w0BCQQxQgRAVB5k673NN0i0 dhHVwQzGyvVJHxlDCBGjLfiWI/O+TVNHnTGLWwYAofLwWjO1sX1w3U+DqdDhcUVdANB5ey/6 CTCBgwYJKwYBBAGCNxAEMXYwdDBdMQswCQYDVQQGEwJVUzESMBAGA1UECAwJVGVubmVzc2Vl MRYwFAYDVQQKDA1EZW5uaW5nZXIubmV0MSIwIAYDVQQDDBlEZW5uaW5nZXIuTmV0IFNpZ25p bmcgSW50AhMAmNFtCiCF3j+FwQLYtBTmGjzkMIGFBgsqhkiG9w0BCRACCzF2oHQwXTELMAkG A1UEBhMCVVMxEjAQBgNVBAgMCVRlbm5lc3NlZTEWMBQGA1UECgwNRGVubmluZ2VyLm5ldDEi MCAGA1UEAwwZRGVubmluZ2VyLk5ldCBTaWduaW5nIEludAITAJjRbQoghd4/hcEC2LQU5ho8 5DCCAVcGCSqGSIb3DQEJDzGCAUgwggFEMAsGCWCGSAFlAwQBKjALBglghkgBZQMEAQIwCgYI KoZIhvcNAwcwDQYIKoZIhvcNAwICAQUwDQYIKoZIhvcNAwICAQUwBwYFKw4DAgcwDQYIKoZI hvcNAwICAQUwBwYFKw4DAhowCwYJYIZIAWUDBAIBMAsGCWCGSAFlAwQCAjALBglghkgBZQME AgMwCwYJYIZIAWUDBAIEMAsGCWCGSAFlAwQCBzALBglghkgBZQMEAggwCwYJYIZIAWUDBAIJ MAsGCWCGSAFlAwQCCjALBgkqhkiG9w0BAQEwCwYJK4EFEIZIPwACMAgGBiuBBAELADAIBgYr gQQBCwEwCAYGK4EEAQsCMAgGBiuBBAELAzALBgkrgQUQhkg/AAMwCAYGK4EEAQ4AMAgGBiuB BAEOATAIBgYrgQQBDgIwCAYGK4EEAQ4DMA0GCSqGSIb3DQEBAQUABIICADmn7B06oO8Yu8Nl JqSy9arZN12RGawAobAbxmXrONjGrEng48D03fQtVpskftMR4YPL+ukgwAlLfJ6S8OkrUM/Y /OLOWTxUaP2QWmS94slM96gd15dp2vsxQFvhbOjGfoYzzPYIIACpR4ZpCFt67WtPfC5snDmh 1akJnB4V6ZDcaUZJSsXDXd+HgtHQloeYRK02j/MgA6Cd94Knu4JdXZkQdy3JJXYHVsPyRgFz dEIkIlc5S/jZr7FLNoNTX9b8UlOFMl/HHiK2K/jyXZnL/BhnUkxLK7px5NkUvxvufLnlPJlm +x+2BOgZd0EnBPlqc1pZc0JCm7MREAwZCcWTEfBsB3kEcdKNQkKV9KqfZV333cbekG2QK0wP rQnjODo8EWTnvK0fSHC9bLZYKo95tleedczNtDepqkf9UmeOeEeZApMFDEJ/ie3lvXf+fx6L PBUS2HVlzcSMSmSVkN2UJwPfwYYnU0ltcAutXOwDhDCHM3uy6RTZ5stjg8eUxGz0sXpAkH2c X1R0U3Z6nZwvII2utxDaJvC6rR7d2MCbKlUDg8WQuga/TyhQlWUxLDD2Zcampp68OObmMqHr qcK34dRAbPPnQJr4Y6+Xd+wn3gkBUfYMmn2KKy/7Z/p7g6Vk2GRrdtrtGMYpm4+DsAZKdjb7 orFdGZALPFoWnMRy6fLEAAAAAAAA --------------ms070504040700060209050308-- From nobody Sat Jan 11 10:39:50 2025 X-Original-To: freebsd-fs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4YVZlt0fNWz5k2lM for ; Sat, 11 Jan 2025 10:39:54 +0000 (UTC) (envelope-from andy@time-domain.co.uk) Received: from mail0.time-domain.net (mail0.time-domain.net [62.3.122.138]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4YVZls4jzqz4D5D for ; Sat, 11 Jan 2025 10:39:53 +0000 (UTC) (envelope-from andy@time-domain.co.uk) Authentication-Results: mx1.freebsd.org; none Received: from mail0.time-domain.net (localhost [127.0.0.1]) by mail0.time-domain.net (8.15.2/8.15.2) with ESMTP id 50BAdpHQ063992; Sat, 11 Jan 2025 10:39:51 GMT (envelope-from andy@time-domain.co.uk) Received: from localhost (andy-tds@localhost) by mail0.time-domain.net (8.15.2/8.15.2/Submit) with ESMTP id 50BAdoP5063989; Sat, 11 Jan 2025 10:39:51 GMT (envelope-from andy@time-domain.co.uk) X-Authentication-Warning: mail0.time-domain.net: andy-tds owned process doing -bs Date: Sat, 11 Jan 2025 10:39:50 +0000 (GMT) From: andy thomas X-X-Sender: andy-tds@mail0.time-domain.net To: heasley cc: freebsd-fs@freebsd.org Subject: Re: How can I tell when ZFS has finished creating a snapshot? In-Reply-To: Message-ID: References: User-Agent: Alpine 2.22 (BSF 395 2020-01-19) List-Id: Filesystems List-Archive: https://lists.freebsd.org/archives/freebsd-fs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-fs@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-Rspamd-Queue-Id: 4YVZls4jzqz4D5D X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:13037, ipnet:62.3.64.0/18, country:GB] But what could be increasing the size of the snapshot after it was created? Right now, yesterday's snapshot made at 14:45 UTC (nearly 22 hours ago) has grown to 468MB: root@clustor2:~ # date Sat Jan 11 10:31:05 GMT 2025 root@clustor2:~ # zfs list -t snapshot NAME USED AVAIL REFER MOUNTPOINT clustor2/ma@2025-01-10_14.45.00 468M - 3.09T - It's true the size this file system reported by 'zfs list' has increasesd from 3.09TB yesterday to 3.10TB now (it's used for storing user data in an HPC that currently has about 700 jobs running on it) but it's very strange that a snapshot supposedly "set in stone" at the time it is created should continue to grow afterwards! Andy On Fri, 10 Jan 2025, heasley wrote: > Fri, Jan 10, 2025 at 06:52:43PM +0000, andy thomas: >> Is there a way to find out the status of a snapshot creation? > > it should be near-instantaneous. "USED" would only change if files in > the snapshot are deleted or overwritten. > > ----------------------------- Andy Thomas, Time Domain Systems Tel: +44 (0)7815 060872 https://www.time-domain.co.uk From nobody Sat Jan 11 11:03:59 2025 X-Original-To: freebsd-fs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4YVbHm267nz5k4Kc for ; Sat, 11 Jan 2025 11:04:04 +0000 (UTC) (envelope-from SRS0=qBys=UD=klop.ws=ronald-lists@realworks.nl) Received: from smtp-relay-int.realworks.nl (smtp-relay-int.realworks.nl [194.109.157.24]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4YVbHl54SFz4G3Z for ; Sat, 11 Jan 2025 11:04:03 +0000 (UTC) (envelope-from SRS0=qBys=UD=klop.ws=ronald-lists@realworks.nl) Authentication-Results: mx1.freebsd.org; none Date: Sat, 11 Jan 2025 12:03:59 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=klop.ws; s=rw2; t=1736593441; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to; bh=7ouKzws2Sbs4lf1YzlcBB8GVUHHqWPxr+l2uIcB5qQE=; b=I+uy1sl/Sd6BMsF48Az4Q/v0Nz0y5YrMhG/5ICES5roIT5Tx99ioxrz0865tR8n4o5yISV azLqwIz/nspwoTB0IXtIyEm5Pkbb5VQT0YSMMgvt87ju+R/Pl+ocGpEYXQypeHKS/I+Is7 +ffvrzyzTZ2Mw7d36WNQsu0rjTPPNEbcuiS7CI9K/Crv6oWbfyHjEfpD+a6DTDXihmvhaA RH/fHJWx6vB/Jwj7rFY30KfQhkZ4d6QtP4wefjZo373JMYqbI/ijUhOvi9fUROBkpZosDb bUsczPgBtZj3CXGZaERVgsEXf4n2oMdwN46+/0wPT7fVZMlfg7l3uA+uzIzAiQ== From: Ronald Klop To: andy thomas Cc: freebsd-fs@freebsd.org, heasley Message-ID: <856588185.13572.1736593439701@localhost> In-Reply-To: Subject: Re: How can I tell when ZFS has finished creating a snapshot? List-Id: Filesystems List-Archive: https://lists.freebsd.org/archives/freebsd-fs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-fs@FreeBSD.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_13571_438639477.1736593439698" X-Mailer: Realworks (733.112) Importance: Normal X-Priority: 3 (Normal) X-Rspamd-Queue-Id: 4YVbHl54SFz4G3Z X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:3265, ipnet:194.109.0.0/16, country:NL] ------=_Part_13571_438639477.1736593439698 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable For example: After creating a snapshot you delete a file in the original file system. Th= e file is still in the snapshot. So the size of the file will be accounted = to the snapshot. Modifying a file will give similar effect. The =E2=80=98old=E2=80=99 parts = of the file are only available via the snapshot so will be accounted to the= snapshot. Regards,Ronald. Van: andy thomas Datum: 11 januari 2025 11:40 Aan: heasley CC: freebsd-fs@freebsd.org Onderwerp: Re: How can I tell when ZFS has finished creating a snapshot? >=20 >=20 > But what could be increasing the size of the snapshot after it was create= d? Right now, yesterday's snapshot made at 14:45 UTC (nearly 22 hours ago) = has grown to 468MB: >=20 > root@clustor2:~ # date > Sat Jan 11 10:31:05 GMT 2025 > root@clustor2:~ # zfs list -t snapshot > NAME USED AVAIL REFER MOUNTPOINT > clustor2/ma@2025-01-10_14.45.00 468M - 3.09T - >=20 > It's true the size this file system reported by 'zfs list' has increasesd= from 3.09TB yesterday to 3.10TB now (it's used for storing user data in an= HPC that currently has about 700 jobs running on it) but it's very strange= that a snapshot supposedly "set in stone" at the time it is created should= continue to grow afterwards! >=20 > Andy >=20 > On Fri, 10 Jan 2025, heasley wrote: >=20 > > Fri, Jan 10, 2025 at 06:52:43PM +0000, andy thomas: > >> Is there a way to find out the status of a snapshot creation? > > > > it should be near-instantaneous. "USED" would only change if files in > > the snapshot are deleted or overwritten. > > > > >=20 >=20 > ----------------------------- > Andy Thomas, > Time Domain Systems >=20 > Tel: +44 (0)7815 060872 > https://www.time-domain.co.uk >=20 >=20 >=20 >=20 >=20 ------=_Part_13571_438639477.1736593439698 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable For example:

After creat= ing a snapshot you delete a file in the original file system. The file is s= till in the snapshot. So the size of the file will be accounted to the snap= shot.

Modifying a file will give similar effect. = The =E2=80=98old=E2=80=99 parts of the file are only available via the snap= shot so will be accounted to the snapshot.

Regard= s,
Ronald.

Van: andy thomas <andy@time-domain.co.uk>
Datum= : 11 januari 2025 11:40
Aan: heasley <heas@= shrubbery.net>
CC: freebsd-fs@freebsd.org
Onderwerp: Re: How can I tell when ZFS has finished creating a sn= apshot?

But what could be increasing the size of the snapshot after it was cr= eated? Right now, yesterday's snapshot made at 14:45 UTC (nearly 22 hours a= go) has grown to 468MB:

    root@clustor2:~ # date
    Sat Jan 11 10:31:05 GMT 2025
    root@clustor2:~ # zfs list -t snapshot
    NAME        &nbs= p;            &= nbsp;        USED  AVAIL  = ;REFER  MOUNTPOINT
    clustor2/ma@2025-01-10_14.45.00   468M &n= bsp;    -  3.09T  -

It's true the size this file system reported by 'zfs list' has increasesd f= rom 3.09TB yesterday to 3.10TB now (it's used for storing user data in an H= PC that currently has about 700 jobs running on it) but it's very strange t= hat a snapshot supposedly "set in stone" at the time it is created should c= ontinue to grow afterwards!

Andy

On Fri, 10 Jan 2025, heasley wrote:

> Fri, Jan 10, 2025 at 06:52:43PM +0000, andy thomas:
>> Is there a way to find out the status of a snapshot creation?
>
> it should be near-instantaneous.  "USED" would only change if fil= es in
> the snapshot are deleted or overwritten.
>
>


-----------------------------
Andy Thomas,
Time Domain Systems

Tel: +44 (0)7815 060872
https://www.time-domain.co.uk=




------=_Part_13571_438639477.1736593439698-- From nobody Sat Jan 11 11:21:34 2025 X-Original-To: freebsd-fs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4YVbhd3YSxz5k6BC for ; Sat, 11 Jan 2025 11:22:09 +0000 (UTC) (envelope-from Alexander@Leidinger.net) Received: from mailgate.Leidinger.net (bastille.leidinger.net [89.238.82.207]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature ECDSA (P-256) client-digest SHA256) (Client CN "mailgate.leidinger.net", Issuer "E6" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YVbhc3R5pz4HQ8 for ; Sat, 11 Jan 2025 11:22:08 +0000 (UTC) (envelope-from Alexander@Leidinger.net) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=leidinger.net header.s=outgoing-alex header.b=HjomgPw2; spf=pass (mx1.freebsd.org: domain of Alexander@Leidinger.net designates 89.238.82.207 as permitted sender) smtp.mailfrom=Alexander@Leidinger.net; dmarc=pass (policy=quarantine) header.from=leidinger.net List-Id: Filesystems List-Archive: https://lists.freebsd.org/archives/freebsd-fs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-fs@FreeBSD.org MIME-Version: 1.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leidinger.net; s=outgoing-alex; t=1736594519; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=cN2E7EMEZwTwDSBgAf/7EYRfs2vf7/oDbcUEwV3qUHc=; b=HjomgPw2U7HWnRMANoBRqQ95ojN5LkNEjC1f2lPGu9/eoddFjNde8nfOdYkyRQKNt97QS3 As5amIaLrJl5s8YpYDIzIIJKQe7S0IKU0nDT8h4LClKF0i/XghzZ3cwplXdhZFP6kMRwKI /I2SCqptKJz/t31GubdE6QtEOZrtxfwWRFdMYo/9Z/DB3GjuRpROKxby8RrG+9zqMktqjf TH3oZYpBdB/nhQWMB2Iz0+ZjHYEcHyCAlfeusHJITM6mjkVXz872VcdRVVc7+joS/CNuxE 4mCu2H5+WcaZTlk7kHqGscZ3wRZlGfGidhhaacxhXEZk2zEeTLs6sQPsogC1Sw== Date: Sat, 11 Jan 2025 12:21:34 +0100 From: Alexander Leidinger To: andy thomas Cc: freebsd-fs@freebsd.org Subject: Re: How can I tell when ZFS has finished creating a snapshot? In-Reply-To: <856588185.13572.1736593439701@localhost> References: <856588185.13572.1736593439701@localhost> Message-ID: <357554e1ae8745a7dfc8701d4bbb45ac@Leidinger.net> Organization: No organization, this is a private message. Content-Type: multipart/signed; protocol="application/pgp-signature"; boundary="=_93c3eae43c412c4537a29bd1381e61a4"; micalg=pgp-sha256 X-Rspamd-Queue-Id: 4YVbhc3R5pz4HQ8 X-Spamd-Bar: ----- X-Spamd-Result: default: False [-5.10 / 15.00]; SIGNED_PGP(-2.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_SHORT(-1.00)[-0.999]; DMARC_POLICY_ALLOW(-0.50)[leidinger.net,quarantine]; R_SPF_ALLOW(-0.20)[+mx]; R_DKIM_ALLOW(-0.20)[leidinger.net:s=outgoing-alex]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; TO_DN_SOME(0.00)[]; ARC_NA(0.00)[]; HAS_ORG_HEADER(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:34240, ipnet:89.238.64.0/18, country:DE]; DKIM_TRACE(0.00)[leidinger.net:+]; MID_RHS_MATCH_FROM(0.00)[]; MISSING_XM_UA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCVD_COUNT_ZERO(0.00)[0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; MLMMJ_DEST(0.00)[freebsd-fs@freebsd.org]; HAS_ATTACHMENT(0.00)[] This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --=_93c3eae43c412c4537a29bd1381e61a4 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed Am 2025-01-11 12:03, schrieb Ronald Klop: > For example: > > After creating a snapshot you delete a file in the original file > system. The file is still in the snapshot. So the size of the file will > be accounted to the snapshot. > > Modifying a file will give similar effect. The 'old' parts of the file > are only available via the snapshot so will be accounted to the > snapshot. Or in other words, the snapshot does not grow at all, it is read-only. Space is attributed to a snapshot if the live dataset doesn't reference a piece of data. Data which is removed or changed in the live dataset since the snapshot was taken is what you see in USED. You can use "zfs diff" to see where data has changed. I'm not sure if such data is attributed to the oldest or the most recent snapshot, but it's one of both (I guess to the oldest). Bye, Alexander. > Regards, > Ronald. > > Van: andy thomas > Datum: 11 januari 2025 11:40 > Aan: heasley > CC: freebsd-fs@freebsd.org > Onderwerp: Re: How can I tell when ZFS has finished creating a > snapshot? > >> But what could be increasing the size of the snapshot after it was >> created? Right now, yesterday's snapshot made at 14:45 UTC (nearly 22 >> hours ago) has grown to 468MB: >> >> root@clustor2:~ # date >> Sat Jan 11 10:31:05 GMT 2025 >> root@clustor2:~ # zfs list -t snapshot >> NAME USED AVAIL REFER MOUNTPOINT >> clustor2/ma@2025-01-10_14.45.00 468M - 3.09T - >> >> It's true the size this file system reported by 'zfs list' has >> increasesd from 3.09TB yesterday to 3.10TB now (it's used for storing >> user data in an HPC that currently has about 700 jobs running on it) >> but it's very strange that a snapshot supposedly "set in stone" at the >> time it is created should continue to grow afterwards! >> >> Andy >> >> On Fri, 10 Jan 2025, heasley wrote: >> >>> Fri, Jan 10, 2025 at 06:52:43PM +0000, andy thomas: >>>> Is there a way to find out the status of a snapshot creation? >>> >>> it should be near-instantaneous. "USED" would only change if files >>> in >>> the snapshot are deleted or overwritten. >>> >>> >> >> ----------------------------- >> Andy Thomas, >> Time Domain Systems >> >> Tel: +44 (0)7815 060872 >> https://www.time-domain.co.uk >> >> ------------------------- -- http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF --=_93c3eae43c412c4537a29bd1381e61a4 Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc; size=833 Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEER9UlYXp1PSd08nWXEg2wmwP42IYFAmeCVE0ACgkQEg2wmwP4 2IYNzBAAhOV/ESYtjZ1l85hp567dXK5Dc0JId+YwYJc1dHQ13l+tFLIGXmKbVsve z5/a5c3pk9McoSh8QGlTIM7PuPl3fHpgQZJHNLyAQht9TfMolAUuvur6T2jis01K TdVSHttgSEiyaUmIMXuniq4gkU2l9s+70/yL5sv/zIH/l+Yvlf6uC7M5MYnX30cC W3gjZ2TABuMQ5/sUe7BP+crR9se9e4vmQ4RvAyTECwGbISjO5sKWXNjGPOGizDdR SEKl9DwadusiKeGdulLHLFBKaujrac/ULSMabnb3B5U2phgLGqhP1gvJ9P3Qey5P gVNFIQ1TnPoTuK4WyeZQd2cD/7HMKbB2PbEUUpyXwO0zfboJKMCa8oAwCJn2Ylg8 MWmHUutyFC/8G4OEP/OTxBm8osQcR8mSnSKH3BqBZovAiWAbMUNonhqCwkUUfy5a A941SaL+ek2ubogcf2m7n953XoD8ATyNhqSEeVQhQBev8bqecTPE5/r0SiceDm+I oYBrkGfjM1oeemS41jBw1vG/wmOxatkgs1O4Cf4YUakARW8Psu0FWUtkSmiQWn9B OOBddmg5TNNvOl1KyTbyUdiLBPHojfNIA+laW14lKD/C2LKZ27qSYj6Wf2oZZkhT flMrfpYRDDeh2kyITwn0T0nGdmkbpAECbQTpF1gsEnFQE4f4XQ0= =QsO9 -----END PGP SIGNATURE----- --=_93c3eae43c412c4537a29bd1381e61a4-- From nobody Sun Jan 12 20:55:56 2025 X-Original-To: fs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4YWSNF54NJz5jnmp for ; Sun, 12 Jan 2025 20:55:57 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YWSNF30blz4Xxt for ; Sun, 12 Jan 2025 20:55:57 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1736715357; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Y3vuMuPcLUooUAcOtdrfGjxdduumnbs3lm0dnfWI4y0=; b=bSxEZHuTECr883+ofo5ESN8S0AwhNy8BDJfI7a+kOO6qPulQ8pIOGSYMBcTCiZEbrQHhKR uLfciBpOAlRjoO1fG2JielNkirmqxjw6qkmSBZG6puzOOAdtvuVNY0gw3IZ/bj0yRN4cji U3GOtkTiNAv+T2OrAbpykeMzOGDKl63eJSmqlUe7tj/Dm5S9jM1HWsjqZaowNbuWILUtTs lU4dzODDsQ+6xiP5PSe10pdnurmj+1AFUO1i+vT4VLDiIIkSs7yl3X2Cwl72iiB5Z8chbh sCoOZLUAUFBoF02WSoxtmLBCk6jqTCE8q1En6ORJXqhDOStvezUJGh3C2Xcgrg== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1736715357; a=rsa-sha256; cv=none; b=UddywdcmGvnKos31gePl8uTP02ZTjMw94loMBJ6UgocXY55ihpYZiEwOb5eIPRpXmoATm3 fPKDkefF7CipUwsb4CMjStPkP6ASQnqZDLL7V3C9fCgGTErIyBT90lwLij43irSWmd6F95 oG5LpHSKFHj5YkRQSdcNJc1J/Gr7ISHc2A/bG5F2PIZ+BF6WlWcxWML7yS9o5W3/KGOh8+ EkT3q+BpRPVNn905fddeOBWdQdE5HzhvYwmOq0R4qThnwlWT5JHSQfd0K6BfOatKo7cePj v/0L2/DVdh0n5DpsDkhRXVet6yZpILrrbAmQOQnmMrfoJYUhAe/uO8Heqprxnw== ARC-Authentication-Results: i=1; mx1.freebsd.org; none Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4YWSNF2BNCz11Fd for ; Sun, 12 Jan 2025 20:55:57 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 50CKtvXD086065 for ; Sun, 12 Jan 2025 20:55:57 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 50CKtvTE086064 for fs@FreeBSD.org; Sun, 12 Jan 2025 20:55:57 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 266409] 13.1-RELEASE amd64 crashes in: sa_handle_destroy at zfs/sa.c:1368 > zfs_znode_dmu_fini at zfs/zfs_znode.c:390 Date: Sun, 12 Jan 2025 20:55:56 +0000 X-Bugzilla-Reason: CC AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 13.1-RELEASE X-Bugzilla-Keywords: crash, needs-qa X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: 000.fbsd@quip.cz X-Bugzilla-Status: Closed X-Bugzilla-Resolution: Overcome By Events X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? maintainer-feedback? X-Bugzilla-Changed-Fields: resolution bug_status Message-ID: In-Reply-To: References: Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Filesystems List-Archive: https://lists.freebsd.org/archives/freebsd-fs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-fs@FreeBSD.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D266409 Miroslav Lachman <000.fbsd@quip.cz> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |Overcome By Events Status|Open |Closed --=20 You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.=