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

Rear hangs upon restore for RHEL 7 for failure to mount /run #619

Closed
bibssun opened this issue Jul 13, 2015 · 8 comments
Closed

Rear hangs upon restore for RHEL 7 for failure to mount /run #619

bibssun opened this issue Jul 13, 2015 · 8 comments
Assignees
Labels
bug The code does not do what it is meant to do fixed / solved / done support / question
Milestone

Comments

@bibssun
Copy link

bibssun commented Jul 13, 2015

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."

@bibssun
Copy link
Author

bibssun commented Jul 13, 2015

The version of rear used is rear ver 1.17.

@bibssun
Copy link
Author

bibssun commented Jul 13, 2015

Also the method of recovery used is Rear Recovery with TSM .

@gdha gdha self-assigned this Jul 14, 2015
@gdha
Copy link
Member

gdha commented Jul 14, 2015

@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.
You could verify the /var/lib/rear/layout/disklayout.conf file to see if /run was a separate mount point?

@gdha gdha added the bug The code does not do what it is meant to do label Jul 24, 2015
@gdha gdha added this to the Rear v1.18 milestone Jul 24, 2015
@gdha
Copy link
Member

gdha commented Jul 24, 2015

On my centos7 system I have the following tmpfs file systems:

tmpfs                          12229932       92  12229840   1% /dev/shm
tmpfs                          12229932     9276  12220656   1% /run
tmpfs                          12229932        0  12229932   0% /sys/fs/cgroup

These are temporary file systems and are not tracked in the disklayout.conf file.

The problem with TSM is that variable MOUNTPOINTS_TO_RESTORE gets defined in script verify/TSM/default/40_verify_tsm.sh and afterwards as the variable is not empty in script restore/default/90_create_missing_directories.sh it will skip the creation of some critical mount points which are not backup'ed by TSM such as proc sys tmp dev/pts dev/shm.
Furthermore, I noticed that sys is missing in this list too.
Therefore, this is a bug, that needs to be fixed

@gdha
Copy link
Member

gdha commented Jul 24, 2015

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.

@gdha
Copy link
Member

gdha commented Jul 28, 2015

A good starting point for the script could be:
$ ls -ld $(mount | grep -vE '(cgroup|fuse|nfs|/sys/)' | awk '{print $3}') to get the list of mount points where we need to save the permissions and ownership

@gdha
Copy link
Member

gdha commented Aug 13, 2015

read some interesting comments from Schlomo in http://pikachu.3ti.be/pipermail/rear-users/2015-August/003138.html

gdha added a commit that referenced this issue Aug 26, 2015
…/default/90_create_missing_directories.sh)

issue #619
gdha added a commit that referenced this issue Nov 2, 2015
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
@gdha
Copy link
Member

gdha commented Nov 4, 2015

@bibssun feel free to test out the new script committed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug The code does not do what it is meant to do fixed / solved / done support / question
Projects
None yet
Development

No branches or pull requests

2 participants