Have you removed some PC from the backup list?
If you have, the folder to that PC is still available in /backup/pc/<pc
name> . You have to remove the folder manually.
I believe that will cause high disk usage, as it is not linking to the pool.
Note at the bottom of Edit Hosts:
To delete a host, hit the Delete button. For Add, Delete, and configuration
copy, changes don't take effect until you select Save. None of the deleted
host's backups will be removed, so if you accidently delete a host, simply
re-add it. *To completely remove a host's backups, you need to manually
remove the files below /var/lib/backuppc/pc/HOST
*
Thanks.
On Wed, Oct 30, 2013 at 8:21 AM, Craig O'Brien <cobr...@fishman.com> wrote:
> The folder /backup is the root of the disk. I mounted the disk there,
> doing the ls -l /backup showed all the root folders on the disk. Perhaps
> there is something going on with the PC folders, as the lost+found and
> trash folders are both empty.
>
> I'm not sure how I can go about determining if a particular backup is
> using the pool or just storing the files in the PC folder. What's the best
> way to check if a given backup set is represented in the pool or not? Would
> knowing the size of all the pc folders help narrow it down?
>
> I'm not sure if this is the best way to check the hard linking, but here's
> a test I thought might be helpful. I did this command to see if a common
> file in these backups are pointing to the same inodes.
>
> bash-4.1$ ls -i /backup/pc/*/*/ffileshare/fWindows/fexplorer.exe
>
> The output is long so I'll give a snippet:
>
> bash-4.1$ ls -i /backup/pc/*/*/ffileshare/fWindows/fexplorer.exe
> 635979167 /backup/pc/120p1m1/75/ffileshare/fWindows/fexplorer.exe
> 646452561 /backup/pc/7qk56d1/79/ffileshare/fWindows/fexplorer.exe
> 635979167 /backup/pc/120p1m1/76/ffileshare/fWindows/fexplorer.exe
> 646452561 /backup/pc/7qk56d1/80/ffileshare/fWindows/fexplorer.exe
> 635979167 /backup/pc/327kkn1/87/ffileshare/fWindows/fexplorer.exe
> 646452561 /backup/pc/7qk56d1/81/ffileshare/fWindows/fexplorer.exe
> 635979167 /backup/pc/327kkn1/88/ffileshare/fWindows/fexplorer.exe
> 646452561 /backup/pc/7qk56d1/82/ffileshare/fWindows/fexplorer.exe
>
> And it continued like that which shows me that a common file is going to
> the same inodes in these backups which tells me the pool should be working
> in theory. (I'm assuming the 2 variants account for different versions of
> windows.)
>
> So I'm pretty stumped at how to figure out what happened to it.
>
>
> Regards,
> Craig
>
>
> On Tue, Oct 29, 2013 at 6:07 PM, <backu...@kosowsky.org> wrote:
>
>> Les Mikesell wrote at about 16:51:12 -0500 on Tuesday, October 29, 2013:
>> > On Tue, Oct 29, 2013 at 4:30 PM, Timothy J Massey <tmas...@obscorp.com>
>> wrote:
>> > >
>> > >
>> > > 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.
>> >
>> > This could happen if the backups were originally on a different
>> > filesystem and were copied over without preserving the pool hardlinks.
>> > For example if you rsync an individual pc directory into place,
>> > subsequent rsync runs will link against those copies for existing
>> > files but will only make the pool links for new/changed files.
>> >
>> > --
>>
>> It also can happen if you have filesystems with flaky hard linking --
>> I once had that issue with a bad user-space nfs module.
>>
>>
>> ------------------------------------------------------------------------------
>> 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@lists.sourceforge.net
>> List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
>> Wiki: http://backuppc.wiki.sourceforge.net
>> Project: http://backuppc.sourceforge.net/
>>
>
>
>
> ------------------------------------------------------------------------------
> 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@lists.sourceforge.net
> List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
> Wiki: http://backuppc.wiki.sourceforge.net
> Project: http://backuppc.sourceforge.net/
>
>
--
Sharuzzaman Ahmat Raslan
------------------------------------------------------------------------------
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@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
