-
Notifications
You must be signed in to change notification settings - Fork 69
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
importing pools with special vdev give BSOD #313
Comments
Which special vdev? l2arc, slog? |
@lundman special vdev/special allocation class (feature GUID org.zfsonlinux:allocation_classes) openzfs/zfs#5182 |
Right right that one - last time there was a vdev issue it was missing a callback, but I don't think allocation classes uses them. Do you know how to get the crash log after a BSOD? |
For win - unfortunately no, I'll try this docs in a week https://docs.microsoft.com/en-us/troubleshoot/windows-client/performance/read-small-memory-dump-file |
https://openzfsonosx.org/wiki/Windows_BSOD If mdexter has kept it up to date :) |
@lundman wow, great, thank you! :) |
My bad, looks like zpool import commands now trigger something in Windows itself or it's a hardware fault, don't see anything zfsin-related
I'll close this issue then. |
I've imported this pool before special vdev addition with readonly=on successfully, but after special vdev it just gives BSOD now. What info may be interested here from Win, and how to get it?
Looks like special vdev is readonly-compatible https://openzfs.github.io/openzfs-docs/man/5/zpool-features.5.html?highlight=special%20alloc
Release 0.24.
The text was updated successfully, but these errors were encountered: