Hi!

It appears that, by some sort of backuppc misbehaviour, my cpool went
from 100 to 500G from one day to the other.

What's more strange to me, is that the disk space before compression and
pooling remained the same...

Digging a little bit into the documentation, I see that I made a mistake
some months ago when migrating my backuppc version from Debian's 3.3.2
to self-installed by hand 4.2.1, having not changed the cpool version
PoolV3Enabled when I upgraded the binaries, which leads me to think I
might missed more than that alone too....

I'm tempted to think that, since I manually deleted some backups when
upgrading backuppc version, I might have left some cpool's file oprhan
at some point.

Is there a way to go through all the cpool to pickup orphan/unreferenced
files to gain that space back?


Thanks in advance!

_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

Reply via email to