* remote.uncache: skip a file overwritten since the walk read it
The uncache cleared the chunks of the entry its directory walk returned and
wrote it back unconditionally. A file overwritten after the walk read it
was reset to the remote pointer, and its new chunks were dropped, so an
acknowledged write was lost. Write back only while the filer still holds
the entry as read, and report the file as skipped otherwise.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* remote.meta.sync: keep files written locally after the directory listing
meta.sync lists each local directory once and works from that listing.
A changed remote file was written back over the listed entry
unconditionally, and a name missing from the listing was created without
O_EXCL, so a file written locally in between was replaced by the remote
pointer either way. Update only while the filer still holds the listed
entry, create exclusively, and report such files as skipped. The create
now also surfaces errors the filer returns in its response.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* remote.cache: keep files written locally after the lookup
The metadata step looks each file up and then either rewrites it from the
remote unconditionally or creates it without O_EXCL, so a local write
landing between the lookup and the write was replaced by the remote
pointer. Reuse doSaveRemoteEntry, which updates only while the filer still
holds the looked-up entry, create exclusively, and report such files as
skipped.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* remote.meta.sync: do not descend into a name a local file took
When the exclusive create of a remote directory finds the name taken, the
sync still descended into it, and creating the remote children under a
local file would turn that file into a directory. Descend only when the
name now holds a directory.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* remote.meta.sync: delete only the file version it listed
The type-change and -deleteStale paths removed a remote-backed file
unconditionally, so a local write landing after the directory listing was
deleted with it. Condition the delete on the listed mtime, as fs.verify
and volume.fsck do; the filer then keeps a file written since.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* remote.meta.sync: condition directory and mtime-less deletes too
The listed-mtime cutoff was only sent for files, so a remote-backed
directory replaced locally by a file between the emptiness check and the
delete was removed unconditionally, and so was a file listed without an
mtime. Send the cutoff for directories as well, and for an entry listed
without an mtime keep it once a write has set one.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* filer: test that DeleteEntry applies the request's mtime cutoff
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* remote.meta.sync: keep the listed nanoseconds as the cutoff of an epoch mtime
An entry listed at the epoch with a sub-second mtime was sent a 1 ns
cutoff, so the filer kept it unchanged although the old code deleted it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* remote.meta.sync: report an entry the filer kept instead of deleting it
The filer answers a delete it skipped under the mtime cutoff with
success, so the sync printed (delete) for an entry a local write kept.
deleteLocalEntry now looks the name up after the delete and prints the
outcome, and a replaced file that was kept is not recreated.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
