-
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
No more "can only attach to mirrors and top-level disks" protection, crashing zdb #15536
Comments
After some bisection, here is some commit range. A known FreeBSD good version:
First known FreeBSD bad version:
|
I guess it may be a fallout from #15022 , since AFAIK it used |
Will take a look on Linux using the above script... I can reproduce on Linux with a modified version of the script (to account for device management differences). I have an idea what's going on and should be able to fix. |
The test, |
I isolated the issue and have a fix. I'll open a PR after some additional testing. We don't seem to have a test case covering attaching to a child of a raidz vdev. Here's the proposed fix:
|
attach-issue-linux.txt |
Reviewed-by: Richard Yao <[email protected]> Reviewed-by: Brian Behlendorf <[email protected]> Signed-off-by: Don Brady <[email protected]> Closes openzfs#15536 Closes openzfs#15564
System information
Describe the problem you're observing
Regression since about 1-2 months:
Previously we could not attach a disk to a non-top-level disks, and even a FreeBSD regression tests was checking for this limitation.
https://cgit.freebsd.org/src/tree/tests/sys/cddl/zfs/tests/replacement/replacement_002_pos.ksh
But since recently on FreeBSD current, we could create some mirror. But later zdb is panicing trying to check those zpool.
Describe how to reproduce the problem
Here is a FreeBSD shell script to reproduce it:
Include any warning/errors/backtraces from the system logs
zdb panic error message:
The text was updated successfully, but these errors were encountered: