S3 backend with leftover file loops between preparing and cleaning
Bug #326017 reported by
Michael Terry
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Déjà Dup |
Fix Released
|
Critical
|
Michael Terry | ||
Bug Description
I tried to manually backup to my S3 backend, but it said Preparing, then Cleaning, then Preparing, etc. in a loop. I'm not sure why yet. Looking into it.
| Changed in deja-dup: | |
| importance: | Undecided → Critical |
| status: | New → In Progress |
Revision history for this message
| Michael Terry (mterry) wrote | #1 |
| Changed in deja-dup: | |
| assignee: | nobody → mterry |
| milestone: | none → 7.0 |
| status: | In Progress → Fix Released |
To post a comment you must log in.
I had a couple problems here, both solved in 7.4. First, I had been accidentally entering the wrong encryption password. Deja Dup parsed the error from that as indicating that a filename on the backend was invalid (bug #1). So it turned on --short-filenames. Second, it saw some short-filename cruft files and so kicked off a cleanup operation. This cleanup didn't turn on --short-filenames (bug #2) so it cleaned up any long filenames and went back to 'preparing' mode. Again, the short-filename cruft would be seen, and we'd kick off cleanup. Rinse and repeat.
To fix, I made sure cleanup got the --short-filenames argument if it had been turned on. And second, I made the error for a bad encryption password more distinct.