Ok, I found the problem.  Looks like my cpool is in the wrong place,  
apparently:

ln: creating hard link `/var/lib/backuppc/cpool/b/7/6/ 
b763efe12301fe7645e82fb46d53b4e3' to `/mnt/plump/backuppc/pc/ 
192.168.0.8/10/attrib': Invalid cross-device link

It looks like my cpool is in /var/lib/backuppc/cpool, but my backups  
are in /mnt/plump/backuppc.

How do I change that?  I thought everything was based on the topdir,  
which I've set to /mnt/plump/backuppc.

*confused*

-- Kimball




On Feb 27, 2008, at 2:48 PM, Les Mikesell wrote:

> Kimball Larsen wrote:
>>>> 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.
>>>
>>> Hmm....Something is definitely up with my inodes:
>>>
>>> [EMAIL PROTECTED]:/mnt/plump/backuppc# df -i
>>> Filesystem            Inodes   IUsed   IFree IUse% Mounted on
>>> /dev/sdc2                  0       0       0    -  /
>>> varrun                497169      77  497092    1% /var/run
>>> varlock               497169       2  497167    1% /var/lock
>>> udev                  497169    3232  493937    1% /dev
>>> devshm                497169       1  497168    1% /dev/shm
>>> lrm                   497169      13  497156    1% /lib/modules/ 
>>> 2.6.22-14-generic/volatile
>>> /dev/sda1                  0       0       0    -  /mnt/tubby
>>> /dev/sdb1                  0       0       0    -  /mnt/portly
>>> /dev/sde1                  0       0       0    -  /mnt/brick
>>> /dev/sdd1                  0       0       0    -  /mnt/plump
>>> /dev/sdf10           4294967295  975408 4293991887    1% /media/ 
>>> Hammer USB
>>>
>>> I notice that all my disks that are ReiserFS do not list any inode  
>>> info at all... is ReiserFS the problem, then? Should I change the  
>>> backuppc disk to be ext3?
>
> Reiserfs creates inodes as needed so that's not a problem.  Just  
> look at your logs and if you still see 'unable to link' errors, try  
> to find the reason.  Trying execute the same ln command as the  
> backuppc user might give you some sort of error message.
>
> -- 
>  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/

Reply via email to