ZFS zpool status lists 0 alloc on readonly pools

mro

mro

sh: 
$ zfs --version
zfs-2.2.7-FreeBSD_ge269af1b3
zfs-kmod-2.2.7-FreeBSD_ge269af1b3

$ zpool list
NAME                   SIZE  ALLOC   FREE  CKPOINT  EXPANDSZ   FRAG    CAP  DEDUP    HEALTH  ALTROOT
mro.name-2025-hdd-01   928G      0   928G        -         -     0%     0%  1.71x    ONLINE  -
zroot                  117G  61.3G  55.7G        -         -    43%    52%  1.00x    ONLINE  -

$ doas zpool export -f mro.name-2025-hdd-01 && doas zpool import mro.name-2025-hdd-01

$ zpool list
NAME                   SIZE  ALLOC   FREE  CKPOINT  EXPANDSZ   FRAG    CAP  DEDUP    HEALTH  ALTROOT
mro.name-2025-hdd-01   928G   513G   415G        -         -    10%    55%  1.71x    ONLINE  -
zroot                  117G  61.3G  55.7G        -         -    43%    52%  1.00x    ONLINE  -

is this intentional?
 
I assume from your comment in the first "zpool list" output the pool was readonly ... although it doesn't say that anywhere. Not showing allocated size and fragmentation seems silly and is likely a bug. Message on the mailing list, or file a PR?
 
zpool export -f forces the export. i don't see any reason to do that normally. if the pool won't export without force, you've got something using it. the docs also warn that it can cause corruption.
 
atax1a said:
zpool export -f forces the export. i don't see any reason to do that normally. if the pool won't export without force, you've got something using it. the docs also warn that it can cause corruption.
Click to expand...
atax1a sorry to insist. You elaborated on what I shouldn't do instead on what you "recommend as a normal type of activity".

And it feels OT.

btw: A readonly imported removable device feels legit to export -f for me. I do not expect data loss on the device.
 
generally speaking, we only use the -f option to any given command when the unforceful version doesn't work, it just seems unwise to make a habit out of forcibly exporting pools
 
You must log in or register to reply here.
Back
Top