-
-
Notifications
You must be signed in to change notification settings - Fork 14.6k
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
ZFS kernel panic in 21.05 #134914
Comments
For reference: openzfs/zfs#12346 is a PR that backports two critical fixes (the crash mentioned above, and a persistent data corruption bug) for a prospective 2.0.6. It's not clear yet whether a 2.0.6 will actually happen, but that's the current upstream status. |
FYI |
Sure, but that's adopting a major new release of ZFS on a stable storage system. I'd be much happier with a targeted fix against a more mature release. For this particular dataset, I don't want to be the first to find the exciting new 2.1 bugs :) |
Perfectly understandable & reasonable, just wanted to make sure you're aware of this option :) |
I marked this as stale due to inactivity. → More info |
21.05 is EOL |
Describe the bug
My NAS runs
21.05.20210721.63ee5cd (Okapi)
, with the stable ZFS package (version2.0.5-1
). Yesterday, it kernel-panicked in ZFS block management code.I traced the panic back to openzfs/zfs#11531, which was fixed by openzfs/zfs@a81b812 and released in ZFS 2.1.0, but not backported to 2.0.x.
I filed openzfs/zfs#12494 to request a backport + 2.0.6 release upstream, so that downstream distros can pull the fix without having to upgrade a stable OS release to ZFS 2.1. I have no idea if the OpenZFS project continues maintaining prior minor releases for a while, or if they'll say that downstream distros should import the patch if they care.
Filing this bug to track either importing ZFS 2.0.6 if such a release happens, or to consider backporting the panic fix into NixOS as a downstream patch on 2.0.5.
Maintainer information:
The text was updated successfully, but these errors were encountered: