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...
# diff -u /tmp/Main.py /usr/share/python-support/rdiff-backup/rdiff_backup/Main.py
--- /tmp/Main.py 2009-11-26 19:05:14.000000000 +0100
+++ /usr/share/python-support/rdiff-backup/rdiff_backup/Main.py 2009-11-26 22:21:46.585994896 +0100
@@ -715,8 +715,10 @@
Log.FatalError(("Bad directory %s.\n" % (rp.path,)) +
"It doesn't appear to be an rdiff-backup destination dir")
try:
- Globals.rbdir.conn.fs_abilities.single_set_globals(Globals.rbdir,
- read_only)
+ if action == "remove-older-than":
+ Globals.rbdir.conn.fs_abilities.single_set_globals(Globals.rbdir, 1)
+ else:
+ Globals.rbdir.conn.fs_abilities.single_set_globals(Globals.rbdir,read_only)
except (OSError, IOError), exc:
print("\n")
Log.FatalError("Could not open rdiff-backup directory\n\n%s\n\n"
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
