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
snapshot restore fails spectacularly on btrfs #131
Comments
I will not be able to rework this in the next few weeks. I believe on the mailing list it was agreed that you would attempt a redesign, and I'll look at any patch you send. Otherwise I hope to look at this in february. |
Something like following seems to work fine for me. I'm guessing it's not going to work with unprivileged container case but on the other hand I'm not sure whether we support btrfs in that case at all. Pasting here for reference (aka until I find some time to test more and submit to the list)
|
fixes #131 changes since v1; * uses btrfs snapshot feature only if src and dest are on same fs Signed-off-by: S.Çağlar Onur <caglar@10ur.org> Acked-by: Serge E. Hallyn <serge.hallyn@ubuntu.com>
fixes lxc#131 changes since v1; * uses btrfs snapshot feature only if src and dest are on same fs Signed-off-by: S.Çağlar Onur <caglar@10ur.org> Acked-by: Serge E. Hallyn <serge.hallyn@ubuntu.com>
I created a snapshot on a btrfs filesystem and lxc-snapshot correctly
created a btrfs subvolume snapshot. However when restoring the
snapshot, I got this instead:
There are a couple of problems with that:
Even though the subvolume was no longer listed by
(presumably because the rsync had messed it up), but it was apparently
still marked as such in the filesystem metadata (even after a reboot).
I was able to clean up the mess via:
and move the snapshot back in place to restore access to my original
instance.
The text was updated successfully, but these errors were encountered: