Closed
Description
System information
| Type | Version/Name |
|---|---|
| Distribution Name | Debian |
| Distribution Version | buster with backports |
| Linux Kernel | 4.19.0-13-amd64 |
| Architecture | amd64 |
| ZFS Version | zfs-0.8.5-2~bpo10+1 |
| SPL Version | modinfo spl | grep -iw version: 0.8.5-2~bpo10+1 (but dpkg -l |grep spl reports 0.7.12-2+deb10u1) |
Describe the problem you're observing
According to #6900 it should be possible to remove a top-level vdev (implemented in v 0.8.5)
However, zpool remove results in "out of space".
Describe how to reproduce the problem
# dd if=/dev/zero bs=1M count=64 of=/ZFS5
# dd if=/dev/zero bs=1M count=64 of=/ZFS6
# dd if=/dev/zero bs=1M count=64 of=/ZFS7
# dd if=/dev/zero bs=1M count=64 of=/ZFS8
# zpool create zptest2 mirror /ZFS5 /ZFS6 mirror /ZFS7 /ZFS8
# zpool get feature@device_removal zptest2
NAME PROPERTY VALUE SOURCE
zptest2 feature@device_removal enabled local
# zpool status zptest2
pool: zptest2
state: ONLINE
scan: none requested
config:
NAME STATE READ WRITE CKSUM
zptest2 ONLINE 0 0 0
mirror-0 ONLINE 0 0 0
/ZFS5 ONLINE 0 0 0
/ZFS6 ONLINE 0 0 0
mirror-1 ONLINE 0 0 0
/ZFS7 ONLINE 0 0 0
/ZFS8 ONLINE 0 0 0
errors: No known data errors
# zpool remove zptest2 mirror-0
cannot remove mirror-0: out of space
# zpool remove zptest2 mirror-1
cannot remove mirror-1: out of space