Alex,
First you should check to see what's left in the v3 cpool, eg:
cd /data/BackupPC/cpool
ls -lR [0-9a-f]
du -s ?/?/?
Next you could pick a file and find its inode number and number of links:
ls -li 0/1/2/1234567890abcdef
Are there any files with >1 links? If so, you could
Ray,
Sorry about the delay in replying. I'm not sure why those two directories
are still around; BackupPC_backupDelete didn't report any errors. It also
didn't delete the XferLOG.[56].z files.
It looks like #3 was correctly deleted, and XferLOG.3.z too.
What's in those directories? Are they o
Bob,
There doesn't seem to be anything untoward in the log information you sent.
To figure out why /home is empty, you should post the specific rsync_bpc
commands (that are in the XferLOG file).
Note that for 4.1.2, I added --one-file-system to the default
$Conf{RsyncArgs}, and it also adds that
The strace is showing the dynamic linking during startup of ssh, which
isn't particularly relevant. It's not showing the files being backed up.
What we are missing is the log output from XferLOG. That has the more
detailed information (eg, exact rsync / ssh args). Can you send that
please? You
Any value is allowed, but the meaningful values are between 0 and 10.
Increasing the value generates more log output. At XferLogLevel == 1 you
should get one line of output per file, and it goes up from there.
If I'm trying to track down a problem, I usually start at 7.
You can also get addition