Re: [BackupPC-users] Disk space used far higher than reported pool size

"Craig O'Brien" <cobrien AT fishman DOT com> wrote on 10/29/2013 03:30:46 PM: > The topdir is /var/lib/BackupPC which is a link to /backup

I missed that in your previous e-mail. Stupid proportional fonts...

(And you might want add a -h for commands like du and df: the -h is for human-readable... When the numbers are for things in the *terabytes*, it's a lot of digits to manage...)

> If I do an ls -l /var/lib
> I get a bunch of other directories as well as:
> lrwxrwxrwx. 1 root root 7 Dec 17 2011 BackupPC -> /backup
> > bash-4.1$ ls -l /backup
> total 20
> drwxr-x---. 18 backuppc root 4096 Oct 25 21:01 cpool
> drwx------. 2 root root 4096 Dec 17 2011 lost+found
> drwxr-x---. 76 backuppc root 4096 Oct 24 16:00 pc
> drwxr-x---. 2 backuppc root 4096 Dec 24 2012 pool
> drwxr-x---. 2 backuppc root 4096 Oct 29 01:05 trash
> bash-4.1$

That is much clearer, thank you.

> It's only backuppc stuff on there. I did it this way to give the > backuppc pool a really large drive to itself.

Sounds reasonable.

> As far as things done > from the command line I've deleted computers inside of the pc > directory that I no longer needed to backup. From my understanding > that combined with removing the pc from the /etc/BackupPC/hosts file > would free up any space those backups used to use in the pool.

The way the pooling works is that any files with only one hardlink are deleted from the pool. Given that BackupPC is saying that the pool is only <3TB big, then your problem is *not* that there are things in the pool that aren't anywhere else. Your problem is the exact opposite: you have files somewhere else that are *not* part of the pool!

> I've > manually stopped and started the backuppc daemon when I've made > config changes, or added/removed a pc. At one point I had almost all > of the pc's being backed up with SMB, and switched them all to using rsync.

Again, I could imagine lots of ways this might explode your pool, but you have the exact opposite problem: your pool is too small!

Please run Jeff's command to find out where you have files that are not in the pool. That will be most informative.

> I ran the du -hs command you recommended, I'll post the results when > it eventually finishes. Thank you.

I doubt that will help if you did it from /backup. The point of that was to isolate other non-BackupPC folders.

Check lost+found and trash while you're at it and see what's in there. They should both be empty.

I'm with Jeff: I think that you have multiple PC trees that are not part of the pool. How you managed that I'm not sure. But you need to find those files and clean them up. Start with Jeff's command and go from there.

Tim Massey


Out of the Box Solutions, Inc. Creative IT Solutions Made Simple! http://www.OutOfTheBoxSolutions.com tmassey AT obscorp DOT com		22108 Harper Ave. St. Clair Shores, MI 48080 Office: (800)750-4OBS (4627) Cell: (586)945-8796

------------------------------------------------------------------------------
Android is increasing in popularity, but the open development platform that
developers love is also attractive to malware creators. Download this white
paper to learn more about secure code signing practices that can help keep
Android apps secure.
http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk

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