It appears that rdiff-backup is crashing because a
special directory is missing
ERROR: cannot open `/mnt/backup/debian1/mnt/backup/palace/dev/.static' (No
such file or directory)
ERROR: cannot open
`/mnt/backup/debian1/mnt/backup/palace/rdiff-backup-data/increments/.static'
(No such file or directory)
My understanding is that, unlike /dev, which
contains device files created dynamically at boot
time by initrd and udev, /dev/.static/dev contains
static device files that may be unused, and are
created by some kind of odd
$ mount --bind <dir1> <dir2>
command.
According to someone using the nickname "Wyzard"
on freenode's #debian IRC channel, it gives one a
view of the root filesystem that's free of any
other filesystems that might be mounted on top of
it. You see the real disk-based /dev, the empty
/proc that procfs is normally mounted on top of,
etc.
I don't know what all this means, but it seems to
me to be an odd coincidence that rdiff-backup is
missing a special directory, and I find myself
wondering whether rdiff-backup has a bug in
code related to descending into other mounted
filesystems.
Thanks,
Kingsley
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
