-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
zpool cannot remove vdev #14312
Comments
Please show |
vdev mirror-1 was created in files which stored in ext4 fs (default blocksize=4k), The expected behavior would be that when adding vdev to a pool, zpool would automatically match the best pool ashift. |
|
scenario:
Current approach blocks removing of vdev if ashift will differ, that means user will have to rebuild whole pool |
I am having this problem right now. Seems illogical to allow mixed ashift when adding a disk, then complaining about it when trying to remove. Since mixed ashift pool apparently works, is there just a check that needs to be removed from EDIT: I see... removal operation needs to keep a block level mapping table for the removed vdev. I assume that's why it requires all vdev to have the same ashift. And it doesn't support removal of raidz vdevs either. Seems like a big trap for inexperienced user (like me) to fall into. |
Well this was awkward ... I was adding the wrong device to my zpool and suddenly I have to rebuild my entire pool from scratch because of this bug. I really appreciate the time and effort that is put into this project but I really hope this bug can be fixed. |
It's in the works: #15509 |
We've had that happen without user manually setting ashift, just by adding a hard disk Sooo it is unfixable and requires re-creating everything ?
why it works like that, it's a massive footgun. We just had junior admin following the usual instructions that happened to use the replacement drive that got ashift 12 instead of rest of the pool's 9 and now it is unfixable. |
Hi, Not sure if I have the same problem, but it seems my pool has the same ashift but I also couldn't remove a mirror special vdev. Also got the same error message.
Got an error removing a mirror special vdev:
zdb -C
|
@tkittich You was told "all top-level vdevs ... and not be raidz". Your pool has raidz2 vdev. |
zfs-2.1.4-1
zfs-kmod-2.1.5-1
when i try remove mirror-1 vdev i have error:
cannot remove mirror-1: invalid config; all top-level vdevs must have the same sector size and not be raidz.
How to reproduce:
My disk has:
my pool alocation:
mu pool ashift:
The text was updated successfully, but these errors were encountered: