-
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
zdb gives Input/Output error #1997
Comments
@FransUrbo The history code changed substantially with the libzfs_core changes which went in just after 0.6.2. It would be helpful to instrument |
It is the Doing a blame on spa.c, I see a lot of rougue's hand here. I'll have a talk to @lundman about this... --EDIT-- Actually, that seems to be wrong. It looked a little weird, so I did a diff between my version and the vanilla ZoL code and no spa_history_log* stuff is touched. |
Disabling On an exported pool:
Which is the same as on an imported pool:
|
I'm closing this, because it's now quite obvious that it's the zfs-crypto patch that fucked everything up. |
(Possibly) related to #1848, #1862 and #1933.
Any attempt to run (most) zdb commands gives Input/Output error. Trying on an exported pool, with the cache file removed, gives a segmentation fault:
Running it through gdb shows:
The text was updated successfully, but these errors were encountered: