#192 Unchanged files detected as changed

O. Givi

I am using DirSync Pro to synchronize a directory structure on a MacOSX laptop and the same structure on a USB memory stick. Whenever I synchronize, DirSyncPro diagnoses that a large number of files are different. But in reality they are not: they have the same size and timestamp, as shown in the "sync queue" window. Actually if I repeat the "analyze" step immediately after having run a synchronization, I get the same files diagnosed as different

Note that the source files are on the MacOS file system whereas the target is on FAT32. When source and target are both on MacOS then the synchronization works fine. Also when both are on FAT32.

My only explanation is that the timestamp comparison does not work well between the two file systems. Could it be that one of the file systems stores more information for file time stamps - like down to milliseconds for the MacOS file system vs seconds for FAT32 ?



  • O. Givi

    O. Givi - 2012-07-22

    Which version are you using? Please download the latest beta (1.45b6) and verify if your issue is solved there.

  • Albert Godfrind (Oracle)

    Thanks for the quick feedback.

    I actually found the advanced option that lets me set the granularity of timestamps for comparison.It was set to 0 seconds. I modified it to 1 second, and now the matching works fine between MacOS and FAT32.

    If you agree with my diagnostic about the difference in timestamp resolution, then you can close this bug.

  • Albert Godfrind (Oracle)

    Forgot this: I am running version 1.44.

  • O. Givi

    O. Givi - 2012-07-22
    • assigned_to: nobody --> ogivi
    • status: open --> closed-duplicate
  • O. Givi

    O. Givi - 2012-07-22

    There was an issue regarding agressiveness of comparission which is fixed in 1.45b6. If you use 1.45b6 you don't need to set up granularity of 1 second.

    I'm closing this thread.


Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks