Bisync question

Help and Support
7

My best guess, according to your log, is that this file: Documents/!JOT/Book/images/300px-Schrödinger_cat.png was either added to Path1 or deleted from Path2 sometime during (not before) the approximately 4 minutes of your bisync run (from 2023/08/31 15:03:33 to 2023/08/31 15:07:17.)

If this is what happened, it is a known issue with the current version of bisync, and I'm working on a fix for it. Progress can be tracked in the following GitHub issues:

In the meantime, my recommendation is to use --check-sync=false and periodically do an independent integrity check as described here.

If you think this is NOT what happened, then I would be grateful for any other debug info you can provide (including, ideally, steps to reproduce the issue), so that I can look into this further and identify the cause.

Note that the error from your second log is a different error, and is expected:

2023/08/31 15:34:27 ERROR : Bisync critical error: cannot find prior Path1 or Path2 listings, likely due to critical error on prior run
2023/08/31 15:34:27 ERROR : Bisync aborted. Must run --resync to recover.

What this is saying is that because your prior run ended in a critical error, bisync refuses to run again until you run a --resync. This is a safety feature, to avoid making any further changes until the user has a chance to check things out and give the green light to proceed. Sometimes, running a --resync will be all that's needed to resolve things, but other times, you'll want to do some manual cleanup first, before running the --resync. Since bisync can't know which scenario it is, it takes the more cautious approach of asking the user to make the decision, rather than risk guessing incorrectly.

No. Generally, you should only include --resync in the following (rare) scenarios:

  1. It is your first bisync run (between these two paths)
  2. You've just made changes to your bisync settings (such as editing the contents of your --filters-file)
  3. There was an error on the prior run, and as a result, bisync now requires --resync to recover

The rest of the time, you should omit --resync. (Here's why.)

It shouldn't be. A path1 and path2 are out of sync error is only expected if changes were made during the run, not before it. So, if you're certain that nothing changed during the run, then more investigation is needed here.