Ok, sorry, i might have been a bit harsh... No, what i don't understand, really, is why rdiff-backup needs free space to clean up old snapshots: no it doesn't, my patch goes to show that if you treat the cleanup as a read-only operation, it will go through smoothly: it *doesn't* need any free space, the only thing that needed free space for the cleanup was creating a useless temporary file. Also, (this was a while ago, but if i remember correctly) if the tmpdir option did what it's told entirely (some temporary files were created in tmpdir, some in the backup root), you wouln't be in such a trouble when the disk is full. I wonder if anyone had a look at my patch, and if so if they think it's of any interest? or do they have any other suggestions? Thanks, John
Alex Samad <[email protected]> wrote on Monday 07 December 2009 > On Mon, Dec 07, 2009 at 03:22:22PM +1000, Gavin wrote: > > Mmm maybe or maybe just an admin flaw? > > I'm not an rdiff-backup developer mind just a user. > > > > I think you might find a few bits of software that crash if they run out > > of hard drive space. > > There are other alert programs that alarm when drive space is getting > > low. > > > > Sure it would be nice if rdiff-backup could recover and save one when > > this happens and it > > does happen. There was some discussion on list some time back about > > being able to specify > > temp space so that rdiff-backup could perform at least a roll back. > > Another option is to have rdiff-backup look for a certain amount of free > space (configurable) and fail if its not available > > Alex > > > Cheers > > Gavin > > [snip] >
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
