-
Notifications
You must be signed in to change notification settings - Fork 246
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
Rear recover doesn't work with SLES 12 SP1 btrfs subvolume #1095
Comments
Regardless of "quick response is not guaranteed with free support" Just write the basics as plain text here and I may have a look In case of real urgency use the official SUSE support contact |
I mean 'urgency' is at our end so please see if you can help us in getting this resolved. I came across some patch you have released but it seems currently its not in the download archive unless I am seeing it somethign different completely. |
Hi, I will need help in fidning any workaround to get this working on SLES 12 SP1. Could you please review below log files while recovering through rear image? Your help would be much appreciable. Thanks and regards,Vish rear-sles12_test.txt -----> this is after trying snapper and try to recover the image but still failed |
Yes, agree that it failed, but this time it failed with:
Let me warn you about possible implications though, guys in SuSE certainly had a reason for not enabling snapper for small partitions by default. |
@gozora, Yes we tried this solution from - #1036 - by enabling snapper for each LVM vol and then ran it and as you can see it ( test VM log) progressed from stopping at lvroot and then stuck in lvhome. Just wondering if we are missing anything in base OS, which is needed to complete BMR recovery. |
Whether you are missing something in base OS or not, is something I can't answer. I for example consider using btrfs on top of LVM as useless redundancy. Yes it works, but IMHO it just introduces another layer of complexity. see RFC: 1925 point 3 |
@gozora We had ran this using snapper for each FS/vol as attached in here. I have attached the log for your analysis and error is still same where it stuck in mounting /home while recovering. +++ btrfs subvolume set-default /mnt/local/home btrfs subvolume set-default: too few arguments usage: btrfs subvolume set-default Set the default subvolume of a filesystem 2016-11-18 12:01:11 An error occurred during layout recreation. |
Ahh! The error message in the above In both cases the partitioning and filesystems layout Unfortunately in both cases I have currently no time In general: When one likes to use ReaR for disaster recovery One can set up a system in zillions of ways Regarding "VM" in In particular on virtual machines I do not understand For example on KVM/QEMU with the qcow2 I wonder about all that complicated stuff with At least I currently fail to understand In general see In particular therein see the sections |
The error message in the above |
Also this issue should be fixed as described in |
Relax-and-Recover (rear) Issue Template
Please fill in the following items before submitting a new issue (quick response is not guaranteed with free support):
rear-ulvwasaw01.txt
Could you please let us know what can we do to get this working on SLES12 SP1? is there any specific patch or update need to be installed? We are stuck on a project where acceptable DR process needs to be hand over. if there is a workaround then kindly let us know.
Thanking in advance.
Vish
The text was updated successfully, but these errors were encountered: