Skip to content
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

Encrypted ZFS restore Problem #6806

Closed
dotmanila opened this issue Nov 1, 2017 · 2 comments
Closed

Encrypted ZFS restore Problem #6806

dotmanila opened this issue Nov 1, 2017 · 2 comments
Assignees
Labels
Status: Stale No recent activity for issue

Comments

@dotmanila
Copy link

System information

Type Version/Name
Distribution Name Ubuntu 16.04
Distribution Version AWS r4.xlarge instance with 2 EBS volumes 20GB each
Linux Kernel Linux ip-10-1-2-117 4.4.0-1039-aws
Architecture x86_64
ZFS Version v0.7.0-157_gc9427c4, ZFS pool version 5000, ZFS filesystem version 5
SPL Version version: 0.7.0-20_g35a44fc

Describe the problem you're observing

When restoring an encrypted volume/pool I can either get a crash (AWS instance crashes and restarts)

Nov  1 16:27:14 ip-10-1-2-117 kernel: [ 9752.942899]  xvdb: xvdb1 xvdb9
Nov  1 16:27:14 ip-10-1-2-117 kernel: [ 9752.948188]  xvdb: xvdb1 xvdb9
Nov  1 16:32:39 ip-10-1-2-117 kernel: [    0.000000] Initializing cgroup subsys cpuset```

Or an error about key echange:

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

@tcaputi tcaputi self-assigned this Nov 1, 2017
@tcaputi
Copy link
Contributor

tcaputi commented Nov 7, 2017

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.

@stale
Copy link

stale bot commented Aug 25, 2020

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.

@stale stale bot added the Status: Stale No recent activity for issue label Aug 25, 2020
@stale stale bot closed this as completed Nov 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Stale No recent activity for issue
Projects
None yet
Development

No branches or pull requests

2 participants