mirror of
https://github.com/seaweedfs/seaweedfs.git
synced 2026-10-13 09:38:36 +02:00
Alex Russell
81e220e979
When a remote-only entry is renamed over another remote-only file and the deferred copy fails, it reads the source key through its marker. Renamed again the same way, the marker keeps naming that source, but: - remote.sync completed each rename from the event's old key. For the second one that is the first target's old object, which it copied over the destination before clearing the marker. It now copies from the source the entry's marker names. - For the first rename it found no entry at the new path and deleted the old key, which the later entry still reads. When the event's new entry carried a marker and the path is gone, it now leaves the key to the entry that moved on. - When the filer copies a pending entry immediately on a later rename, it now also releases the source the copy read, after the commit and with the same checks as the old key.