A “Rescan Needed” error occurs in some scenarios involving a case sensitive fix

RV 3.7.1

Case Sensitivity Issue
j

johnsanc

2 years ago

There appears to be an error in the fixing logic that can result in a "Rescan Needed" error. This error occurs when the fix required only involves a rename to differing character case, meaning the name is exactly the same, but the character case differs, for example "A" to "a". This seems to occur most frequently with redump sets that have cue files. This is what appears to be happening based on the fixing status log:

  1. RV renames the archive with the improper case to proper case

  2. The cue file within the archive with the improper case should be removed to ToSort, so RV attempts to remove it

  3. A "File not found" error occurs because RV is looking for an archive with the new proper case, but the rename from step #1 may not have completed yet


Steps to reproduce:

  1. Cannot reproduce consistently since this appears to be a race condition. It is most frequently observed when there is significant file system latency (E.g. SMB share under heavy load or an rclone mount to a cloud drive)


Expected behavior:

  • When RV performs an archive rename action, it should ensure the archive is actually renamed before attempting to use a file from it.


(screenshot 1 | screenshot 2)

Activity

j

johnsanc changed the status to WIP Testing

2 quarters ago

j

johnsanc changed the status to RV 3.7.1

2 quarters ago

j

johnsanc marked this post as a duplicate of Case sensitive archive renames can cause an error while fixing

2 quarters ago


Powered by Convas