Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

1
  • 1
    This looks to me as if the second instance initially attempted to sync, skipping one file due to it having been modified during sync, and only then trying to update archives and failing because archives are locked. This may need a large set of files to be noticeable (in my case, around 1 million files, 1 TB in size, about 25,000 files/80 GB changed, over a 3 Mbit network). Besides, the only lock files I am seeing (named lk followed by a 128-bit hash) are 9 months old on both sides, even while files are being transferred (on Unison 2.52.1).
    – user149408
    Commented May 16 at 18:47