New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Regression of failed backup with long file names can result in assertion error #9
Comments
Thanks for the repro instructions, I'll test and investigate this today. Sorry for the long delay in responding |
Any update on this? |
I'd also be interested, as I have the same problem. |
If you could validate that this issue still happens when using the PR #53 that would be really nice. |
- add a regression test based on shell script provided by reporter (it might have to be re-written in Python, not sure it's worth the effort)
OK, the issue still happens with the master branch. I've already written a regression test script heavily based on the script provided by @zjw (thanks!), available for now from the work-in-progress branch ericzolf-regress-longname-9 (we might want to re-write it in Python like all the other tests but I don't know if it's worth the issue, we should definitely add it though to tox.ini once fixed). @anomaly256 are you still owning the issue and be available to fix it? |
- add a regression test based on shell script provided by reporter (it might have to be re-written in Python, not sure it's worth the effort)
- add a regression test based on shell script provided by reporter (it might have to be re-written in Python, not sure it's worth the effort)
FIX: longnames are correctly reversed when regressing a failed back-up, closes #9
- add a regression test based on shell script provided by reporter (it might have to be re-written in Python, not sure it's worth the effort) FIX: longnames are correctly reversed when regressing a failed back-up, closes #9
This bug was originally reported here:
http://lists.nongnu.org/archive/html/rdiff-backup-users/2016-08/msg00000.html
The bug can be reproduced with the following script:
As noted in the script, the problem is that regressing a backup using
--check-destination-dir
fails to completely clean up the repository when there are increment files stored underrdiff-backup-data/long_filename_data/
.A work-around for the bug is to use
--check-destination-dir
and then remove the problematic files underrdiff-backup-data/long_filename_data/
. This removal needs to be done judiciously, however. The only files removed are ones where the date in the file name matches the date in thecurrent_mirror
filename. Here's an example where there is a match:Here is the script output when run:
The text was updated successfully, but these errors were encountered: