-
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
missing nfs mountpoint after the recovery #818
Comments
Hi Pavol - good question: what was the reason? I cannot remember - is there any? |
Because in prep/default/40_save_mountpoint_details.sh Regardless of the reasoning behind I think the command ... mount | grep -vE '(cgroup|fuse|nfs|/sys/|REAR-000)' ... is wrong because it excludes any "mount" output line In general I wonder if a hardcoded list of what should If something cannot be implemented in a hardcoded way, In this case e.g. via a array variable in default.conf that is |
FYI how one could exclude mounted filesystem types findmnt -nrv -o TARGET -i -t 'nfs,cgroup' But "findmnt" is not available on older systems |
Hello! Maybe with something like this should help: mount -l -t "$(echo $(cat /proc/filesystems | grep -v nodev) | tr ' ' ',')" And also works for older systems |
@didacog nice trick. However, it wouldn't fix the NFS mounted file-systems. Perhaps, to catch all mounted file-systems (including the NFS ones) a simple |
@pavoldomin In your initial comment you wrote: After the recovery mountpoints for NFS mounts are missing. ... Work-around is trivial: mkdir manually. Only a blind guess what I think the issue could be: Usually directories should be restored from the backup. If my assumptions are true I wonder if it is really the What about missing directories in the backup that are Perhaps it would be better to improve how rear excludes FYI: I had the same issue for my #779 When moving away restored files that should not have been restored |
@gdha thanks! ;) If the problem is the exclude of basedir, maybe you can try using '/some_path/some_mount_point/*' in the exclude array definition, at least you can try using it as temporary workarround. :-P |
Sorry, again the problem where this thread was found in trash :) What is really happening here is, that I think the solution above outlined by @gdha: |
(NFS mount points are not recreated after a recover)
Relax-and-Recover (rear) Issue Template
After the recovery mountpoints for NFS mounts are missing. This will make nfs shares not mounted after the recovery (if they are referenced from fstab). Related to #619.
Particularly, in prep/default/40_save_mountpoint_details.sh, the collection of nfs mountpoints is explicitly excluded.
I assume there is reason for it, but cannot figure out which.
Work-around is trivial: mkdir manually.
The text was updated successfully, but these errors were encountered: