So then why is this not done automatically? I mean, if your software can't take it if it runs out of space, that's a design flaw you need to prepare for. The user will usually not guess the problem with the software until it's too late. Thanks John
Gavin <[email protected]> wrote on Saturday 05 December 2009 > A work around or way to protect against this is to create an appropriate > sized blank file in the backup partition. > I usually create a 1GB blank file: > > dd if=/dev/zero of=EmptyFile bs=1M count=1000 > > Then when the backup fails just delete the blank file and run the backup > again. > The added benefit of doing this is that it gives you a soft limit and > some time to re-organise your drives/partitions. > (Speaking of which it's about time for me to do just that) > > Cheers > Gavin > > John Soros wrote: > > Here (attached) is a quick fix i applied to rdiff-backup so i didn't have > > to start the backup all over, my disk got full and we are (unfortunately) > > still not using lvm. > > I am not sure as to the cleanliness of the patch, but it seems to be > > working fine, hopefully this can be helpful, as i think having a disk > > full with rdiff- backup is a PITA... > > > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > rdiff-backup-users mailing list at [email protected] > > http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users > > Wiki URL: > > http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki >
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ rdiff-backup-users mailing list at [email protected] http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
