Reproducible panic playing with zpool remove in FreeBSD 11.2-RELEASE.

Maurizio Vairani clover.informatica.it at gmail.com
Tue Jul 3 08:24:45 UTC 2018


Il 02/07/2018 17:47, Karli Sjöberg ha scritto:
>
>
> On July 2, 2018 5:35:28 PM GMT+02:00, Maurizio Vairani 
> <clover.informatica.it at gmail.com> wrote:
>
>     Il 02/07/2018 16:45, Karli Sjöberg ha scritto:
>>
>>
>>     On Jul 2, 2018 15:52, Maurizio Vairani
>>     <clover.informatica.it at gmail.com> wrote:
>>
>>         Hi,
>>
>>         boot the 11.2-RELEASE installation media in the .
>>         Insert an USB memory stick, suppose it is /dev/da5.
>>         # gpart create -s GPT da5
>>         # gpart add -t freebsd-zfs -a 1m -s 1g da5
>>         # gpart add -t freebsd-zfs -a 1m -s 1g da5
>>         # zpool create -O mountpoint=/tmp/ztest ztest da5p1 da5p2
>>         # cp /bin/* /tmp/ztest
>>         # zpool remove ztest da5p1
>>
>>
>>     How are you even able to remove a partition in a pool without
>>     redundancy?
>>
>>     I would've thought ZFS would complain about that and at least
>>     force you to have an '-f' or something in there...
>     This is a new feature in 11.2-RELEASE. From ZPOOL-FEATURES(7):
>     device_removal
>
>                GUID               com.delphix:device_removal
>                READ-ONLY COMPATIBLE    no
>                DEPENDENCIES           none
>
>                This feature enables the    "zpool remove" subcommand
>     to remove
>                top-level vdevs,    evacuating them    to reduce the
>     total size of
>                the pool.
>
>
> Ah, cool, I didn't know that!
>
> How big is 'bin' then? Because it ought to be smaller than 1 GB for 
> you to remove it, right?
>
Yes,
# du -sh /bin
1.3M     bin



More information about the freebsd-fs mailing list