Problem with zpool remove of log device

Łukasz Wąsikowski lukasz at wasikowski.net
Fri May 26 10:30:17 UTC 2017


W dniu 2017-05-26 o 12:20, Karli Sjöberg pisze:
> 
> 
> Den 26 maj 2017 11:47 fm skrev Łukasz Wąsikowski <lukasz at wasikowski.net>:
> 
>     Hi,
> 
>     I cant remove log device from pool - operation ends ok, but log device
>     is still in the pool (bug?).
> 
>     # uname -a
>     FreeBSD xxx.yyy.com 11.0-STABLE FreeBSD 11.0-STABLE #0 r316543: Thu Apr
>     6 08:22:43 CEST 2017 root at xxx.yyy.com:/usr/obj/usr/src/sys/YYY amd64
> 
>     # zpool status tank
>     pool: tank
>     state: ONLINE
>     status: One or more devices are configured to use a non-native block
>     size.
>     Expect reduced performance.
>     action: Replace affected devices with devices that support the
>     configured block size, or migrate data to a properly configured
>     pool.
>     scan: scrub repaired 0 in 22h21m with 0 errors on Thu May 25
>     02:26:36 2017
>     config:
> 
>     NAME STATE READ WRITE CKSUM
>     tank ONLINE 0 0 0
>     mirror-0 ONLINE 0 0 0
>     ada2p3 ONLINE 0 0 0
>     ada3p3 ONLINE 0 0 0
>     logs
>     mirror-1 ONLINE 0 0 0
>     gpt/tankssdzil0 ONLINE 0 0 0 block size:
>     512B configured, 4096B native
>     gpt/tankssdzil1 ONLINE 0 0 0 block size:
>     512B configured, 4096B native
> 
>     errors: No known data errors
> 
>     When I try to remove log device operation ends without errors:
> 
>     # zpool remove tank mirror-1; echo $?
>     0
> 
> 
> You are missing the actual disk you want to remove from the mirror:
> # zpool remove tank gpt/tankssdzil1

# zpool remove tank gpt/tankssdzil0
cannot remove gpt/tankssdzil0: operation not supported on this type of pool

According to man zpool:

     zpool remove pool device ...

         Removes the specified device from the pool. This command
currently only supports removing hot spares, cache, and log devices. A
mirrored log device can be removed by specifying the top-level mirror
for the log.

So zpool remove tank mirror-1 should work. In fact in works fine on
other box with similar configuration.

-- 
best regards,
Lukasz Wasikowski


More information about the freebsd-fs mailing list