mirror of
https://github.com/borgbackup/borg.git
synced 2026-10-12 02:11:36 +00:00
Thomas WaldmannandClaude Opus 5.5
07b8d0271c
acquire() creates its lock object, waits for the race recheck delay and lists the lock objects again to detect other clients racing for the lock. With list-after-write consistency (local filesystems, sftp, rest, AWS S3, MinIO), at least the client that created its lock object last sees the other's lock in its second listing, so the delay is not needed for correctness and the 0.01s default stays. Stores that only list a new object after a lag (e.g. NFS clients caching directory listings, some cloud storages via rclone) need a delay of at least that lag. That lag is a property of the storage, not of the request latency, so it is not measured, but set via BORG_LOCK_RECHECK_DELAY. Invalid values abort with an error. Co-Authored-By: Claude Opus 5.5 <[email protected]>