-
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
Recovery fails - Everything in disklayout file is commented out #1353
Comments
@schabrolles can this be caused by dd65bd0? You seem to be the only author of any change in 300_map_disks.sh recently. Test case is the recovery of the client VM from our rear-workshop. To test for yourself follow the instructions there to build the server and client VM, go to the client, install |
@schlomo Looks strange ... At a very quick look .... I think it is not related to my change (I just add multipath device to be proposed like a disk); but who know :) .... I'm gonna try to run your rear-workshop later today and have look |
@schlomo I quickly try Do you know how to force / configure vagrant to use box ? |
@schlomo Ok I've found it ... Now I got a network problem (or a conflict with my virtualbox configuration)
|
Do you have a locally attached network with 192.168.33.0/24? Then please change 192.168.33 to some other range in all the files of |
@schlomo ... It's running now :D ... I have to change the IP configuration in all Vagrant and scripts files from 192.168. to 192.167. to avoid conflict with my configuration. |
@schlomo There is a Typo in There is a space before disk
|
Can you please submit an update? Thanks a lot. |
Sure, I'm just finishing test before pushing the update. |
Haven't had the time to try again, but the fix seems very much legitimate to me. In any case I don't see any reason why the blank could be correct there so that that fix is for sure an improvement. |
ReaR Snapshot build from today (and now it pains that we don't have the exact git revision in the RPM :-() on CentOS 7.3
The recovery disk has a different size from the source disk.
Interestingly this version did not ask me to map a disk while our last release (2.00) does ask me to map a disk (which I find stupid since there is only once in any case).
Am I the only one who sees this?
Click to open the Recovery Log
The text was updated successfully, but these errors were encountered: