Date: Mon, 21 Aug 2023 20:47:52 +0000 From: bugzilla-noreply@freebsd.org To: usb@FreeBSD.org Subject: [Bug 167685] ZFS on USB drive prevents shutdown / reboot Message-ID: <bug-167685-19105-RP3dITMA4C@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-167685-19105@https.bugs.freebsd.org/bugzilla/> References: <bug-167685-19105@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D167685 John F. Carr <jfc@mit.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jfc@mit.edu --- Comment #13 from John F. Carr <jfc@mit.edu> --- Please reopen. I am seeing this bug today on 13.2-STABLE. I have a ZFS po= ol using five disks in a Sabrent enclosure. In terms of drivers, uhub5 on uhub0 uhub5: <VIA Labs, Inc. USB3.1 Hub, class 9/0, rev 3.20/90.13, addr 1> on us= bus0 uhub5: 4 ports with 4 removable, self powered usb_msc_auto_quirk: UQ_MSC_NO_GETMAXLUN set for USB mass storage device ASMT ASM235CM (0x174c:0x55aa) ugen0.3: <ASMT ASM235CM> at usbus0 umass0 on uhub5 umass0: <ASMT ASM235CM, class 0/0, rev 3.10/1.00, addr 2> on usbus0 umass0: SCSI over Bulk-Only; quirks =3D 0x0100 umass0:20:0: Attached to scbus20 da0 at umass-sim0 bus 0 scbus20 target 0 lun 0 da0: <ASMT ASM235CM 0> Fixed Direct Access SPC-4 SCSI device da0: Serial Number 915000000C05 da0: 400.000MB/s transfers da0: 5723166MB (11721045168 512 byte sectors) da0: quirks=3D0x2<NO_6_BYTE> Other devices appear as uhub6 on uhub5 umass1 on uhub6 [=3D da1] umass2 on uhub6 [=3D da2] umass3 on uhub6 [=3D da3] umass4 on uhub6 [=3D da4] I infer the enclosure has a hub connected to a disk and a second hub. The second hub has the other 4 disks. When I reboot the system I see (retyped from photo) All buffers synced. Uptime: 3d3h57m14s uhub0: detached ukbd0: detached ... umass0: detached umass1: detached Solaris: WARNING: Pool 'sabrent' has encountered an uncorrectable I/O failu= re and has been suspended. Then the system hangs. Within the not especially long limit of my patience there is no more output. No detach message for uhub5, uhub6, umass2, umass= 3, and umass4. I have failmode=3Dcontinue on this pool precisely to avoid having the system hang. There might be two bugs, shutdown order and failure to respect failmode=3Dcontinue. This is repeatable. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-167685-19105-RP3dITMA4C>