Re: [BackupPC-users] Pool Size is Zero

[Kimball L. <ki...@mi...>]

Actually, I may have answered my own question somewhat:

It appears (based on my reading of a message here:
http://www.mail-archive.com/bac...@li.../msg09017.html
) that my pool is hosed.

Specifically, my cpool directory has several gigs of data in it, but  
my "pool" directory is completely empty.  Consequently, when it  
attempts to create the cpool directory, the creation fails as the dir  
already exists (I'm just guessing here).

So, what exactly is the relationship between the cpool and pool  
directory?  How safe is it (I assume NOT safe at all) to remove the  
contents of cpool?

Thanks!

-- Kimball 


On Feb 27, 2008, at 1:11 PM, Les Mikesell wrote:

> Kimball Larsen wrote:
>>>> I notice that the cpool directory is owned by root.  Should it  
>>>> be   owned by the backuppc user instead?
>>> Yes, it must be writable by the backuppc user.  Your logs are   
>>> probably full of "unable to link" errors.
>>>
>> Yeah, I've been getting stuff like this:
>> 2008-02-27 11:51:16 BackupPC_link got error -4 when calling   
>> MakeFileLink( ....
>> I've changed the permissions... how soon should I expect to see  
>> some  items wind up in the pool?
>
> They should be linked during/after each backup run.  You won't see  
> much space benefit from the pooling until your old archives where  
> the link attempt failed are expired, though.
>
> -- 
>  Les Mikesell
>   les...@gm...
>