-
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 hangs upon restore for RHEL 7 for failure to mount /run #619
Comments
The version of rear used is rear ver 1.17. |
Also the method of recovery used is Rear Recovery with TSM . |
@bibssun could you check within TSM if /run was back-up'ed? Also, when you are still in recovery mode you could inspect the file systems under /mnt/local whether all required mount points are present. |
On my centos7 system I have the following tmpfs file systems:
These are temporary file systems and are not tracked in the disklayout.conf file. The problem with TSM is that variable |
I think we need to do this in a more generic way and also restore the moint points with correct ownership and permissions. Therefore, we should make a new script in the prep work-flow and save the output for later and use it in the restore work-flow as input. |
A good starting point for the script could be: |
read some interesting comments from Schlomo in http://pikachu.3ti.be/pipermail/rear-users/2015-August/003138.html |
…/default/90_create_missing_directories.sh) issue #619
updated script: restore/default/90_create_missing_directories.sh Purpose is to list up all directories and permissions so we can recreate any missing dir after recovery which usually the case in combination with backup software (like TSM, bareos,...) See issue #619
@bibssun feel free to test out the new script committed. |
For RHEL 7 Server - rear restore appears to complete , but once the Server is rebooted - The Server hangs with the message "Failed to mount /run . No such file or directory."
The text was updated successfully, but these errors were encountered: