|
Re: [BackupPC-users] Disk space used far higher than reported pool size
2013-10-29 15:12:26
"Craig O'Brien" <cobrien AT fishman DOT com>
wrote on 10/29/2013 01:53:31 PM:
> On the General Server Information page, it says "Pool is 2922.42GB
> comprising 6061942 files and 4369 directories," but our
pool file
> system which contains nothing but backuppc and is 11 TB in size is
100% full.
My strong guess is that, while you *think* nothing
else is out there, that is not the case! :)
> I'm confused how this happened and even ran the
BackupPC_nightly
> script by hand which didn't seem to clear up any space. Judging by
> the reported pool size it should be less than 30% full. I could
> really use some help. Thanks in advance for any ideas on how to go
> about troubleshooting this.
From the other message, it seems that the filesystem
you're worried about is /home. What is the TopDir of BackupPC? I
assume it's something like /home/backuppc (or I sure hope it is!). Go
to that path and type:
du -hs
This will take a *long* time: BackupPC has a
*lot* of files. I would also hope that you see a number very similar
to the pool size report above.
So, if you find that your BackupPC TopDir contents
(what you verified with du -hs) reports match the GUI, then you know that
there's something on the drive but *outside* of the BackupPC TopDir. Find
it and delete it.
Because du -hs of the pool takes so long, you could,
of course, do it the *other* way: do a du -hs of each directory *besides*
your TopDir and see how much space is being used by them. Depends
on how many other folders you have how hard that would be. But when
you see some other folder using 8TB, you'll know where the space went!
However, if you find that your du -hs does *not* match
your GUI report, then you have to look more closely. Have you *EVER*
done anything from the command line inside of the TopDir? Given that
you mention running BackupPC_nightly by hand, I suspect you of monkeying
with things, and that very well may have broken things. Tell us what
you did! :)
(It's not that you can't run BackupPC_nightly by hand;
you can. It's more that if you're brave enough to run it by
hand, there's no telling what *else* you might have done, and how you might
have broken things! :) ).
If you can't tell, I suspect something outside of
BackupPC has used the space, *or* that you moved/copied/etc. something
using tools outside of the BackupPC system and have broken things unintentionally.
It is very unlikely that BackupPC is wrong on its pool report. Most
likely it's something *else* that is consuming the space, and because of
that all the BackupPC_nightly in the world isn't going to free up the space.
Tim Massey
------------------------------------------------------------------------------
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/
|
|
|
