Kimball Larsen wrote:
> Actually, I may have answered my own question somewhat:
>
> It appears (based on my reading of a message here:
> http://www.mail-archive.com/[email protected]/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?
Pool is used if you don't have compression enabled, cpool if you do.
Whichever is used must be on the same filesystem as the pc directory
tree so that hardlinks work between them. If you are getting errors
making the links, check that you have space (df) and inodes available
(df -i), and that the directory is writable by the backuppc user.
--
Les Mikesell
[EMAIL PROTECTED]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
BackupPC-users mailing list
[email protected]
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
