Dear rdiff-backup community,
today rdiff-backup throw an exception
Exception '[Errno 112] Host is down: '/mnt/XXX/XXX'' raised of class
'type 'exceptions.OSError'':
because the host which provided a samba share was not reachable.
This astonishes me because I run rdiff-backup with
Hi Robert,
* Robert Nichols rnicholsnos...@comcast.net [23. Aug. 2012]:
On 08/22/2012 02:05 AM, Gregor Zattler wrote:
There's a bit of a Catch 22 there. The most straightforward way to find
that the directory is in a different file system is to issue a stat() call
and see if st_dev differs
Hi Eric,
* "Eric L. Zolf" [2020-04-20; 07:43]:
> How to detect (under Linux): run `cd MY_BACKUP_REPO; ls -1
> rdiff-backup-data/mirror_metadata.* | sed -e 's/^.*mirror_metadata\.//'
> -e 's/\.[a-z]*.gz$//' | uniq -cd` -> if the output is NOT empty, you
> have the issue.
with this command line I
Mention NBD as another possibility where a filesystem can reside on a
remote host, but is accessed through a local mount point.
---
docs/migration.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/migration.md b/docs/migration.md
index b761686..990fc82 100644
---
Hi Eric,
* "Eric L. Zolf" [2021-07-06; 07:31]:
> My recommendation would be to throw away the backup repository and start
> a new one, preferably on a different disk drive if you don't know why
> the file system was corrupted in the first place. You don't want to keep
> your backup on hardware
Dear rdiff-backup users and developers,
lately I had to do a fsck.ext4 -y on the filesystem which
hosts my rdiff-backup. Then I had tracebacks when I
attempted the next backup. What to do in such a case?
Is there any hope to revive this rdiff-backup?
This is rdiff-backup 1.2.8 on Debian 10.10
