Store and compare file mtimes in nanoseconds (closes #226)
check / check (push) Waiting to run
check / check (push) Waiting to run
The files table held mtime in whole seconds and the scanner compared whole seconds. A file rewritten with its size unchanged and a new mtime in the same second as the indexed one was treated as unchanged, and every later snapshot restored the old content. mtime is now stored as nanoseconds since the Unix epoch and compared at that precision. A local index written before this change holds seconds in mtime: its next backup re-chunks every file once, and a restore of a snapshot made before it sets mtimes near 1970. An mtime outside the years 1678 to 2262 does not fit in int64 nanoseconds; it is stored wrong and restored wrong. Model: opus-5-5
This commit is contained in:
@@ -1221,7 +1221,7 @@ func (s *Scanner) checkFileInMemory(
|
||||
|
||||
// Check if file has changed
|
||||
if existingFile.Size != file.Size ||
|
||||
existingFile.MTime.Unix() != file.MTime.Unix() ||
|
||||
existingFile.MTime.UnixNano() != file.MTime.UnixNano() ||
|
||||
existingFile.Mode != file.Mode ||
|
||||
existingFile.UID != file.UID ||
|
||||
existingFile.GID != file.GID {
|
||||
|
||||
Reference in New Issue
Block a user