On 08/23/2012 04:03 PM, Gregor Zattler wrote:
Hi Robert, * Robert Nichols<rnicholsnos...@comcast.net> [23. Aug. 2012]:Doing the exclude by name should avoid the problem. Simply excluding /mnt/* might suffice, since basically anything under /mnt should be a different file system.Ah. I didn't do this since I wanted the mount points to be included in the backup. Thanks for the explanation, though. If the same problem reoccurs I will follow you advise.
Any _active_ mount point directory is also going to be excluded by the
--exclude-other-filesystems option, so presumably you're just trying to
include mount point directories that are not currently in use.
If you want to exclude just the active mount points, you can parse those
from /proc/mounts. Doing that right gets messy because of possible
embedded white space in automatically generated mount point names, and
_really_ messy if you want embedded newlines handled safely. I've
attached a fragment of my backup script which does that. (It's just a
fragment, not directly usable on its own. Note the comments about ASCII
NUL separator.)
The other way, which includes _all_ mount point directories as they
exist in the parent file system, is to use the non-inclusive property of
bind-mounts:
mkdir /tmp/tmp-mount
mount --bind / /tmp/tmp-mount
If you now do a backup of /tmp/tmp-mount it will include everything that
is part of the root file system, including the (presumably empty) mount
point directories that were there before anything was mounted on them.
The downside is that you will include automatically generated mount
points like /media/*, and you probably didn't want those.
--
Bob Nichols "NOSPAM" is really part of my email address.
Do NOT delete it.
script-fragment.gz
Description: GNU Zip compressed data
_______________________________________________ rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/rdiff-backup-users Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
