TW
Hmm, that does not look like a borg error, but rather that the repo disk fs or disk hw was confused somehow. Borg never writes such json content to the...
Need to have a deeper look there. But I guess a missing fsync does not explain that it showed the data from a completely different file.
Oh, it gets more weird. :-) Could you copy the repo to a different disk / different enclosure and reproduce with that?
BTW, `SaveFile` internally uses `SyncFile` which does flush and `os.fdatasync` (and falls back to `os.fsync` if platform has no `os.fdatasync`) internally before closing the file.
One approach to debug this would be to add a logger.debug() to the locking code. IIRC it is the lock.roster file that has this json content.
Guess the filesystem confusion seen here has nothing to do with borg, so we can't do anything about it. But, what we can do is to produce a better error...
The logs show some things: - mtime changed from 1699991999675344006 to 1700078399414387394. that means that the file's content was modified. - UNKNOWN: no file metadata in cache for: b'/mnt/domains/reflinks/vm_geneious-license-mcd.raw' -...
https://borgbackup.readthedocs.io/en/stable/faq.html#i-am-seeing-a-added-status-for-an-unchanged-file https://borgbackup.readthedocs.io/en/stable/faq.html#it-always-chunks-all-my-files-even-unchanged-ones
The age starts with 0 (== fresh, 0 generations old) and increases per backup run. If a file is not seen, the age of its files cache entry increases. If...