On Tue, 21 Apr 2020 at 07:17, Eric Lavarde <[email protected]> wrote: > > > On 20/04/2020 22:54, Gregor Zattler wrote: > > Hi Eric, > > * "Eric L. Zolf" <[email protected]> [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 see no output on two repos dating from > > 2012 for which rdiff-backup -l | wc -l shows 2386 and 2499 lines > > respectively. > > > > rdiff-backup is now on version 1.2.8 and both repos are local > > ones (meaning there was never a version mismatch of local and > > remote rdiff-backup programs involved). > > > OK, noted. Thanks. > > So we have currently a timespan of 2009-2011 for this issue. > > KR, Eric >
Despite the failed verifications, I have successfully recovered a largish (>150MB) file from December 2008 in the impacted repository. As there are 2806 later versions of this file (with changes in this file occurring between most of these versions), the recovery presumably involved applying 2806 reverse-diffs to the current file - pretty impressive work by rdiff-backup! (Sorry, still on v1.2.8)
