On Sun, Feb 28, 2010 at 3:06 PM, Johannes H. Jensen
<[email protected]>wrote:
> Actually, one of the files in question is the fformat file of a .svn/
> directory which appears many times in one of the backed up
> filesystems. Since it will have the same md5 sum, BackupPC links it to
> the same file in cpool...
>
I highly doubt you are reaching the maximum number of hardlinks for a single
file but rather the maximum for the filesystem. I cant find any real
numbers on the maximum number of hardlinks for the filesystem or i'd post
it.
>
> This works fine in the local server since backuppc is aware of the
> link limit, but fails when rsyncing to the remote server since new
> backups would increase this link count...
>
If the disk size is different on one machine than the other, you might have
a different hardlink limit as i suspect that it is based on the number of
inodes but again, I didnt find and hard data on that floating around.
My suggestion is to split the backup load into smaller chunks on multiple
servers and either have a couple of remote servers *OR* a couple different
partitions/LVs on the remote system.
Either that or do something else on the remote end link a freebsd/ZFS
storage server which doesnt have hardlink limitations that are realstic to
hit in the next 20 years.
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
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/
