On Sep 29, 2009, at 12:06 PM, Tony Schreiner wrote:

On Sep 28, 2009, at 10:00 PM, Holger Parplies wrote:


Tony Schreiner wrote on 2009-09-28 20:01:24 -0400 [[BackupPC-users]  
unclean pool]:
I have been running low on space on my __topdir__ volume, so several
times in recent weeks, I have moved numbered backup directories to  
__topdir__/trash folder and removed the appropriate line from the
corresponding backups file.

This has recovered a small amount of space but not nearly as much  
as I
expected. Today I looked at the pool directory and found that many  
a majority) of the files there have a single link, shouldn't
BackupPC_nightly be removing those?

yes, it should. Is BackupPC_nightly being run (check the log files  
$LogDir)? What are the values of



And as a follow up, are those file candidates for me to remove if
they're not being removed properly?

Well, yes, but you really need to fix whatever problem you're having  
than get yourself a night job as replacement for  
BackupPC_nightly ;-). You'd
also need to take care of pool chain renumbering and preventing  
from running while you're busy, so it's a bit more difficult than
'find pool cpool -nlinks 1 -exec rm {} \;' ...

I'm trying to investigate further why my cpool is (apparently) not getting cleaned up.  I'm  looking at the code to BackupPC_nightly, but I admit I'm not the l33test of perl programmers. I wonder if someone familiar with the code can help me a bit.

The GetPoolStatus routine is using the find function (from Lib?) to scan the pool. It appears in my case to enter each of the cpool/X/X directories, but does not appear to go deeper. I'm not clean on what is supposed be happening here.