[Bug 167685] ZFS on USB drive prevents shutdown / reboot
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Sun, 20 Oct 2024 00:04:01 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=167685 Mark Millard <marklmi26-fbsd@yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marklmi26-fbsd@yahoo.com --- Comment #19 from Mark Millard <marklmi26-fbsd@yahoo.com> --- In my simple ZFS context I'v enver gotten such behavior. Here I'm using a da0 based UFS boot and later adding da1 and importing its pool: # gpart show -p da1 => 40 1875384928 da1 GPT (894G) 40 532480 da1p1 efi (260M) 532520 8152 - free - (4.0M) 540672 62914560 da1p2 freebsd-swap (30G) 63455232 184549376 da1p4 freebsd-swap (88G) 248004608 20971520 - free - (10G) 268976128 1468006400 da1p3 freebsd-zfs (700G) 1736982528 138402440 - free - (66G) # zpool import pool: zwdk23 id: 8373431646426325674 state: ONLINE status: Some supported features are not enabled on the pool. (Note that they may be intentionally disabled if the 'compatibility' property is set.) action: The pool can be imported using its name or numeric identifier, though some features will not be available without an explicit 'zpool upgrade'. config: zwdk23 ONLINE gpt/wdk23CA78Czfs ONLINE Note: I historically use a /usr/share/zfs/compatibility.d/openzfs-2.*-freebsd as the feature set -- or the likes of /usr/share/zfs/compatibility.d/openzfs-2.2 when there is no linux vs. freebsd distinction for where I have things set. Thus main tends to produce the some-not-enabled message. # zpool import -t -f -R /zptemp-mnt/ zwdk23 zptemp # zpool list -v NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT zptemp 696G 574G 122G - - 20% 82% 1.00x ONLINE /zptemp-mnt/ gpt/wdk23CA78Czfs 700G 574G 122G - - 20% 82.5% - ONLINE # zfs list # shortened listing via ". . ." for omissions NAME USED AVAIL REFER MOUNTPOINT zptemp 574G 100G 96K /zptemp-mnt//zwdk23 . . . zptemp/ROOT 4.94G 100G 96K none zptemp/ROOT/build_area_for-main-CA76 364K 100G 3.00G none zptemp/ROOT/main-CA76 4.94G 100G 2.88G none zptemp/poudriere 516G 100G 112K /zptemp-mnt//usr/local/poudriere zptemp/poudriere/data 516G 100G 128K /zptemp-mnt//usr/local/poudriere/data zptemp/poudriere/data/.m 112K 100G 112K /zptemp-mnt//usr/local/poudriere/data/.m zptemp/poudriere/data/cache 16.4M 100G 16.4M /zptemp-mnt//usr/local/poudriere/data/cache . . . zptemp/poudriere/ports 96K 100G 96K /zptemp-mnt//usr/local/poudriere/ports zptemp/tmp 14.8M 100G 14.8M /zptemp-mnt//tmp zptemp/usr 13.9G 100G 96K /zptemp-mnt//usr . . . zptemp/usr/home 906M 100G 906M /zptemp-mnt//usr/home zptemp/usr/local 2.37G 100G 2.37G /zptemp-mnt//usr/local . . . zptemp/usr/ports 6.81G 100G 6.81G /zptemp-mnt//usr/ports zptemp/usr/src 96K 100G 96K /zptemp-mnt//usr/src zptemp/var 47.0M 100G 96K /zptemp-mnt//var zptemp/var/audit 360K 100G 360K /zptemp-mnt//var/audit zptemp/var/crash 184K 100G 184K /zptemp-mnt//var/crash zptemp/var/db 42.0M 100G 96K /zptemp-mnt//var/db zptemp/var/db/pkg 41.8M 100G 41.8M /zptemp-mnt//var/db/pkg zptemp/var/db/ports 148K 100G 148K /zptemp-mnt//var/db/ports zptemp/var/log 2.75M 100G 2.75M /zptemp-mnt//var/log zptemp/var/mail 1.24M 100G 1.24M /zptemp-mnt//var/mail zptemp/var/tmp 404K 100G 404K /zptemp-mnt//var/tmp Over the years I've never had a problem with shutdown or reboot for such a context. But I've not used mirroring or other such. I experimented with ZFS to experiment with bectl use, not other usage that is typical. -- You are receiving this mail because: You are on the CC list for the bug.