I went into a filesystem problem on my cpool.
I checked my fs and restarted doing backups and restores regularly.
My problem now is that backuppc status page says that my pool is 100 gb
large but df (/var/lib/backuppc is on a dedicated filesystem) says 300
gb, and about 270 gb are in the cpool directory (I enabled compression
of the pool). The host summary page says that the backups are of total
size 280 GB prior to pooling and compression..
The cpool seems populated of files that are "lost" and unreferenced..
(and not removed my nightly processes). Another idea is that during the
fsck, some hardlink has been transformed to a whole file.. (ext3
Is there a way to :
-understand why deduplication seems not working if I read df and host
summary page, but seems working if I look at status page? (or, how the
status page and the summary page calculate the sizes?)
-how to remove sporious file from the pool. One way could be to do a
stat on each cpool file, and remove the file if it was created or
accessed before the oldest backup I made.. but this seems too greedy..
and will put my hardware to the knees for too much time. Also I done a
search for files that aren't owned by bakcuppc (spurious result of an
thanks a lot