From nobody Fri Nov 05 16:19:08 2021 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 102331803F9F for ; Fri, 5 Nov 2021 16:19:15 +0000 (UTC) (envelope-from cross+freebsd@distal.com) Received: from relay.wiredblade.com (relay.wiredblade.com [168.235.95.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Hm5LB4srWz3QKc for ; Fri, 5 Nov 2021 16:19:14 +0000 (UTC) (envelope-from cross+freebsd@distal.com) Received: from mail.distal.com (pool-108-48-165-176.washdc.fios.verizon.net [108.48.165.176]) by relay.wiredblade.com with ESMTPSA (version=TLSv1.2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256) ; Fri, 5 Nov 2021 16:19:11 +0000 Received: from smtpclient.apple ( [2001:420:c0c4:1005::15]) by tristain.distal.com (OpenSMTPD) with ESMTPSA id e4f60858 (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256:NO); Fri, 5 Nov 2021 12:19:10 -0400 (EDT) Content-Type: text/plain; charset=utf-8 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 (Mac OS X Mail 15.0 \(3693.20.0.1.32\)) Subject: Re: ZFS operations hanging, but no visible errors? From: Chris Ross In-Reply-To: <20211105115234.H95319@mulder.mintsol.com> Date: Fri, 5 Nov 2021 12:19:08 -0400 Cc: freebsd-fs Content-Transfer-Encoding: quoted-printable Message-Id: <0CB9C85C-867C-4501-A9DC-9B730303E388@distal.com> References: <20211105115234.H95319@mulder.mintsol.com> To: Walter Cramer X-Mailer: Apple Mail (2.3693.20.0.1.32) X-Rspamd-Queue-Id: 4Hm5LB4srWz3QKc X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; TAGGED_FROM(0.00)[freebsd] X-ThisMailContainsUnwantedMimeParts: N > On Nov 5, 2021, at 11:59, Walter Cramer wrote: >=20 >=20 > Any chance that you have output from an earlier `zpool status`, or = even `zpool list`, to give us a better sense of your situation? Sadly, no. I looked through my buffers and don=E2=80=99t. Have a few = df=E2=80=99s, but other than a showing a system with it=E2=80=99s few = filesystem including the 40T zfs one, it doesn=E2=80=99t help. Filesystem Size Used Avail Capacity Mounted on /dev/da0p2 3.5T 4.2G 3.2T 0% / devfs 1.0K 1.0K 0B 100% /dev /dev/da0p1 256M 1.7M 254M 1% /boot/efi /dev/ada1p1 445G 36K 423G 0% /ssd/scratch tank 49T 9.5T 40T 19% /tank I can say that the pool has three raidz vdevs in it, each with three = devices. 3 4TB disks, 3 6TB disks, and 3 18TB disks. > Might `dmesg -a` show any relevant errors? Nope, that shows just a clean boot from when I rebooted the system = yesterday. > (FWIW, I usually have a daily cron job log a few things like `zpool = status` to /var/backups/zfs, to help with situations like this.) Yeah. Maybe that should be in the normal daily job if the system is = using any ZFS volumes=E2=80=A6. - Chris=