From 87d0c14bc14b57de59c76c88bf22f15a4cbf1c7a Mon Sep 17 00:00:00 2001 From: bescoto Date: Tue, 9 Sep 2003 05:18:22 +0000 Subject: Added note on how to skip regressing git-svn-id: http://svn.savannah.nongnu.org/svn/rdiff-backup/trunk@417 2b77aa54-bcbc-44c9-a7ec-4f6cf2b41109 --- rdiff-backup/FAQ-body.html | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) diff --git a/rdiff-backup/FAQ-body.html b/rdiff-backup/FAQ-body.html index a6c59a9..6592560 100644 --- a/rdiff-backup/FAQ-body.html +++ b/rdiff-backup/FAQ-body.html @@ -27,8 +27,14 @@ bandwidth usage, as in rsync's --bwlimit option? memory leak?
  • I use NFS and keep getting some error that includes "OSError: [Errno 39] Directory not empty"
    • + +
  • For some reason rdiff-backup failed +while backing up. Now every time it runs it says "regressing +destination" and then fails again. What should I do?
    • + +

    Questions and Answers

      @@ -377,5 +383,24 @@ run rdiff-backup locally on both ends instead of over NFS. This should be faster anyway. + +
    1. For some reason rdiff-backup failed +while backing up. Now every time it runs it says "regressing +destination" and then fails again. What should I do? + +

      Firstly, this shouldn't happen. If it does, it indicates a +corrupted destination directory, a bug in rdiff-backup, or some other +serious recurring problem.

      + +

      However, here is a workaround that you might want to use, even +though it probably won't solve the underlying problem: In the +destination's rdiff-backup-data directory, there should be two +"current_mirror" files, for instance +current_mirror.2003-09-08T04:22:01-07:00.data and +current_mirror.2003-09-07T16:43:00-07:00.data. Just delete the one +with the earlier date. The next time rdiff-backup runs it won't try +regressing the destination. +

      2. +
    -- cgit v1.2.1