You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This problem is being caused by a problem with the raw send file format. This shouldn't be hard to fix, but it will require upgrading ZFS on both the source and the target machines (once I have a patch) to fix it.
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.
System information
Describe the problem you're observing
When restoring an encrypted volume/pool I can either get a crash (AWS instance crashes and restarts)
ubuntu@ip-10-1-2-87:/backups$ sudo cp zfskey /dev/shm/
ubuntu@ip-10-1-2-87:/backups$ sudo zfs load-key mysql-data
cannot open 'mysql-data': dataset does not exist
ubuntu@ip-10-1-2-87:/backups$ sudo zfs load-key mysql/data
ubuntu@ip-10-1-2-87:/backups$ sudo zfs load-key mysql/logs
ubuntu@ip-10-1-2-87:/backups$ sudo zfs mount -a
filesystem 'mysql/data' can not be mounted: Invalid exchange
cannot mount 'mysql/data': Invalid argument
ubuntu@ip-10-1-2-87:/backups$```
Describe how to reproduce the problem
This gist will walk through bootstrapping an instance, building ZFS running the tests up to the problem:
https://gist.github.com/dotmanila/82c1dc620149827fc81fafe6af30130d
The text was updated successfully, but these errors were encountered: