"Chris Swan" writes:
> New to BackupPC, and I'm very impressed with it so far. I'd be more
> impressed if I could get a successful backup :)
Apparently you are easily impressed!
> TarExtract: mkdir /mnt/backup/pc/punky/new/fcdrive$/fDocuments and
> Settings/fSharon.PUNKY/fLocal Settings/fTemporary Internet
> Files/fContent.IE5/fRBSJOKJ3: No space left on device at
> /usr/local/backuppc/bin/BackupPC_tarExtract line 270
> Error writing to tar file - Connection reset by peer
> Didn't get entire file. size=2151250, nread=196560
> I still need to do some more troubleshooting, but does anyone seem to know
> if the error 'No space left on device' is just a bogus error? The drive
> it's writing to has plenty (200G+) of free space, and I've dismounted,
> checked it, and there are no errors on it.
> I'm using:
> BackupPC: 2.0.2
> Perl: 5.6.1
> Samba: Tried 2.2.8a, 3.0.0 with first bugzilla patch (the large files one),
> and unpatched 3.0.1pre1.
I've never seen this type of error. Quite mysterious.
The only thing I can suggest is to point BackupPC's data directory
at a different file system and try it there.
Ah, I just got your last email:
> Ah, damnit--I found the problem:
> Out of inodes :) I guess the problem was exacerbated by backuppc, because
> of the 'cpool' directory which consumes a heapin' helpin' of inodes. Maybe
> a note to add to the docs/FAQ? Or are most people intelligent enough to not
> try to manually set their amount of inodes? :)
BackupPC only uses one inode per unique file (the hardlinks point to the
same inode for repeated files) but, yes, that could still be millions of
files in a medium-side installation.
I'll add a note to the docs.