Quote:
Originally Posted by BetterRed
...However I recall seeing another file sync tool that sprinkled stuff in the directories selected for syncing. So if you mirrored D:\Calibre\Calibre Library to E:\Calibre\Calibre Library, it would write 'control' data into those directories which would generate errors in Check Library. I can't recall if FFS was the culprit or the solution.
|
The already mentioned file sync.ffs_db gets written into the root of the synchronized library folder by FreeFileSync on both the source and target devices, so is in the same location as metadata.db. Calibre's Library Maintenance shows it as an Invalid Author but if one knows one is using a file sync application it is blindingly obvious what it is. Apart from that Calibre ignores it. If one deletes it the only outcome is that FreeFileSync will just create another next sync session with no issue that I have ever come across (and if there is some sync conflict FreeFileSync will resolve it or ask for guidance).
As already said, one can just tell Calibre Library Maintenance to ignore sync.ffs_db if wanted; I don't bother to do so.
EDIT: in case of confusion (or of a visiting pedant
), I should make clear that by "source device" I mean the device that the sync is run from e.g. that which FreeFileSync is running on.