Re: [rdiff-backup-users] bind/loop-mounted and cdrom filesystems, cache
Re: [rdiff-backup-users] bind/loop-mounted and cdrom filesystems, cache usage.
Sat, 26 Jan 2008 17:00:46 -0500
Oliver Hookins wrote:
>>If you are on BSD, you can use the patch implementing a
>>--include/exclude-mount-type option (which I think is what you want). It
>>uses a BSD specific field in statfs to make it very easy to implement.
>>Since it is non-portable, you can get it from the Wiki:
> Unfortunately we're on Linux. At the moment we're generating the exclude
> list by hand with a small script but this "exclude-mount-type" option sounds
> like exactly what we want. It definitely can't be done on Linux?
Yeah, on BSD the statfs() call returns a very friendly string
representation of the filesystem type that a given file is on.
Under Linux, it returns an integer. rdiff-backup would have to learn how
to handle those integers, which means that someone would have to keep
track of filesystem development on Linux in order for the translation to
stay up to date. Much easier for the user to parse their own filesystem
and generate the include/exclude lists!
Oddly enough, the way the string representation of the filesystem type
gets into /proc/mounts is by parsing and recording the filename of the
executable used to mount it! The `mount` command on Linux has a number
of "unusual" design choices.
Andrew Ferguson - owsla@xxxxxxxxxxxxx
rdiff-backup-users mailing list at rdiff-backup-users@xxxxxxxxxx
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki