"Stop after current file" with --usn-policy may never back up remaining files #3971
Closed
1 task done
Labels
Milestone
Environment info
Description
The "Stop after current file" ability added in v2.0.4.29-2.0.4.29_canary_2019-09-17 seems incompatible with --usn-policy using USN. Files which are not backed up before the Stop might be skipped forever.
See 2.0.4.31 “Stop after current file” with Windows USN never backs up some files on future backups, which speculated on cause, and invited user tests which didn't happen, so here's a formal bug report. Some of the specifics are erratic, but it's reproducible enough and sticky enough to get some debug.
Steps to reproduce
Backup may (often but not always) declare success, no longer be partial, but be missing many files.
Files are backed up.
Screenshots
Debug log
The text was updated successfully, but these errors were encountered: