--verify fails on renamed backups
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
backup2l (Ubuntu) |
Fix Released
|
Undecided
|
Joachim Wiedorn |
Bug Description
--verify succeeds only on the most recent version of the full backup. The md5sum check fails because the filenames in the older .check files are not updated properly when the full backup versions are renamed.
--verify also fails when older full backups are purged and all subsequent backups are renamed. The associated .check files also don't updated accordingly.
For example:
This is a check file when I had 8 full backups and purged full backup
1-7, which renamed full backup 8 to 1:
8f1cd08f7474507
5a9c87c7ebba480
209847ac7775ed5
b1403dd30da8afb
37c91e1872728d1
4b4870721fb61a5
88a854a773fe980
As you can see, 801 did not get renamed to 101.
According to an open bug report upstream, there is a workaround:
"The filenames in the .check file are prepended by ./ while the sed command in backup2l looks for a leading space. Changed the sed command in backup2l to 'sed "s/ \.\/$VOLNAME.$SRC/ \.\/$VOLNAME.
https:/
However this workaround is not easy to apply because it isn't in a traditional patch form. There is no indication of a line number of where this change should be applied.
Related branches
Changed in backup2l (Ubuntu): | |
assignee: | nobody → Joachim Wiedorn (ad-debian) |
status: | New → Confirmed |
here is the patch which also come with version 1.5-6 (see Debian Sid):
diff -urN s05/backup2l s06/backup2l
fi
done
for CHK in $VOLNAME. $DST*.check ; do
mv $TMP.check $CHK
done
--- s05/backup2l 2012-04-27 16:15:33.880477880 +0200
+++ s06/backup2l 2012-04-27 20:45:23.736469131 +0200
@@ -404,7 +404,8 @@
- sed "s/ $VOLNAME.$SRC/ $VOLNAME.$DST/" < $CHK > $TMP.check
+ cat $CHK | sed "s/ \.\/$VOLNAME.$SRC/ \.\/$VOLNAME.$DST/" |\
+ sed "s/ $VOLNAME.$SRC/ $VOLNAME.$DST/" > $TMP.check
fi