-
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
Null dereference while tyring to zpool remove #16786
Comments
Potentially relevant: #13552 It seems like
|
I think I've encountered this or similar issue that may be easier to reproduce due to a simpler pool layout (though, unfortunately, the pool is no longer available, so I cannot provide further logs). From the get-go it was a simple RAID0 pool of two full disks with mirrored log on separate partitions on two disks (i.e. zpool create tank /dev/disk/by-id/disk1 /dev/disk/by-id/disk2 log mirror /dev/disk/by-id/disk3-part2 /dev/disk/by-id/disk4-part2). Long ago I removed the mirrored log, so right before this issue it was a simple RAID0 pool of two full disks (i.e. zpool create tank /dev/disk/by-id/disk1 /dev/disk/by-id/disk2). I added the third disk to the pool (i.e. zpool add tank /dev/disk/by-id/disk5). Then I removed the first disk (i.e. zpool remove tank /dev/disk/by-id/disk1) - it succeeded as expected. Then I tried to remove the second disk (i.e. zpool remove tank /dev/disk/by-id/disk2) - the command itself was killed by the OS (outputting Killed) and the pool broke. Anything related to this pool after that, blocked forever (e.g. zpool status) and never produced any output. Even shutdown -r now blocked forever, and hard reset was required. After a forced reboot, the pool went up without a hitch, no data lost (at least as far as I could tell). Trying to remove the second disk led to the same result. After several attempts, I had to recreate the pool (because I needed to physically detach both disks ASAP) and restore data from backup (which was magnitudes slower than simply relocating data from the disk being removed). It took quite a while and was a major PITA. Long story short, here's the log from system log generated upon executing the removal of the second disk (i.e. zpool remove tank /dev/disk/by-id/disk2). I don't recall exactly on which ZFS version the pool was created - it was around the times of Fedora 35 IIRC. The ZFS version during removal attempt was 2.2.7 on Fedora 41. I hope it helps. |
System information
Describe the problem you're observing
I have the following pool:
I'm trying to:
Immediately I'm getting a stacktrace from the kernel:
I don't have a reproducer for this, as this only happens on a live pool. Previous removal of another mirror completed successfully.
The text was updated successfully, but these errors were encountered: