-
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
PANIC at dsl_crypt.c:2441:dsl_crypto_populate_key_nvlist() #12439
Comments
A few data points:
If you'd like a pool in a file you can examine that will do this, here you go. |
This issue has been automatically marked as "stale" because it has not had any activity for a while. It will be closed in 90 days if no further activity occurs. Thank you for your contributions. |
I hit this yesterday, doing some checks in preparation for a restore from backup. I've been testing today, and its still present on master. However, I'm almost certain its a spurious ASSERT with Reproduction from scratch as follows. Create pool, encrypted dataset, put some data in, create a backup stream, and burn it all down. To be clear, it doesn't have to be a filesystem, a proper snapshot does the same thing.
Then, create a new pool, and try to recieve the stream:
If compiled with
If not, the stream will be accepted. Sending it back out appears to yield effectively the same stream:
So the answer may simply be that this assertion is erroneous, and should be removed. I haven't done the study to have any confidence though, and won't have time to do so for a while. The workaround appears to be to send a snapshot, not a filesystem. For me at least, this won't be a big deal - this is a backup host carrying snapshots (no key material), so snapshots are a thing I have plenty of. |
System information
Describe the problem you're observing
Someone said to me "hey, I tried
zfs send -w pool/encrypted/filesystem | zfs receive some/where
and it works, butzfs send -v -w pool/encrypted/filesystem | zfs receive some/where
errors out with Invalid argument, what gives", I went "I don't think I expect that to work", triedzfs send -w mypool/encroot > /dev/null
and the magic smoke came out.(Since I couldn't find any report of this before, I figured it was worth reporting for search results even if I try reproducing it on git master and it's been corrected.)
Describe how to reproduce the problem
Above.
Include any warning/errors/backtraces from the system logs
zfs get all phantasm/encroot:
dmesg | tail -n mumble
The text was updated successfully, but these errors were encountered: