Re: [rdiff-backup-users] Full volume and rdiff-backup

[Carl Chenet]

Le samedi 10 octobre 2009 à 10:17 -0400, Daniel Einspanjer a écrit :
> I'm very new to rdiff-backup, so take my advice with a grain of salt, 
> but maybe it doesn't need a *lot* of space..
> Maybe you could move all the session_statistics*.data and 
> file_statistics.data.gz files out of the rdiff-backup-data directory 
> temporarily and then have enough space to --remove-older-than.
> 
> -Daniel

Yes, that's what I meant by "manually do some removals" but I think it
could be interesting if rdiff-backup could manage this situation by
itself, not relying on me :)

> 
> On 10/10/09 5:21 AM, Carl Chenet wrote:
> > Le lundi 07 septembre 2009 à 21:14 +0200, Carl Chenet a écrit :
> >    
> >> Le lundi 07 septembre 2009 à 21:10 +0200, Carl Chenet a écrit :
> >>      
> >>> Hi,
> >>>
> >>> If the backup target fills up, there's no way to recover.
> >>> --check-destination-dir and --remove-older-than both just
> >>> complain about lack of space.
> >>>
> >>> Is there a workaround for converting full rdiff-backup volumes into one
> >>> that --check-destination-dir or --remove-older-than can be run on?
> >>>        
> > # df -h
> > [...]
> > /dev/hda1             236M  236M     0 100% /boot
> > [...]
> > sid:/boot# rdiff-backup --remove-older-than now /boot/backup/
> > Fatal Error: Could not open rdiff-backup directory
> >
> > /boot/backup/rdiff-backup-data
> >
> > due to
> >
> > [Errno 28] No space left on device:
> > '/boot/backup/rdiff-backup-data/rdiff-backup.tmp.0'
> >
> > which means you're blocked, forced to manyally do some removals. Do you
> > consider rdiff-backup should clean the mess or has the user to deal with
> > it manually ?
> >
> > Bye,
> >    
> 
> 
> 
> _______________________________________________
> rdiff-backup-users mailing list at address@hidden
> http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
> Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
-- 
Carl Chenet