syncthing: Incorrect sequence entries created spontaneously

Something is bad with our sequencing stuff. This is my log for the last couple of days:

jb@kvin:~ % egrep -i 'my id|sequence' Library/Logs/Syncthing.log
...
[SYNO4] 14:08:12 INFO: My ID: SYNO4VL-TKVFF25-QKC2T3V-TTK4BGU-D2ZA5OT-PDKSI3R-3P4JQVS-BL4VXAC
[SYNO4] 14:51:08 WARNING: Non-increasing sequence detected: Checking and repairing the db...
[SYNO4] 14:51:08 WARNING: Non-increasing sequence detected: Checking and repairing the db...
[SYNO4] 14:51:08 INFO: Repaired 2738 sequence entries in database
[SYNO4] 14:51:08 INFO: Repaired 29491 sequence entries in database
[SYNO4] 21:51:27 WARNING: Non-increasing sequence detected: Checking and repairing the db...
[SYNO4] 21:51:27 INFO: Repaired 72 sequence entries in database
[SYNO4] 22:12:31 INFO: My ID: SYNO4VL-TKVFF25-QKC2T3V-TTK4BGU-D2ZA5OT-PDKSI3R-3P4JQVS-BL4VXAC
[SYNO4] 20:37:01 WARNING: Non-increasing sequence detected: Checking and repairing the db...
[SYNO4] 20:37:01 INFO: Repaired 117 sequence entries in database
[SYNO4] 20:37:04 WARNING: Non-increasing sequence detected: Checking and repairing the db...
[SYNO4] 20:37:04 INFO: Repaired 4459 sequence entries in database
[SYNO4] 20:37:10 WARNING: Non-increasing sequence detected: Checking and repairing the db...
[SYNO4] 20:37:10 INFO: Repaired 47953 sequence entries in database
[SYNO4] 03:53:33 WARNING: Non-increasing sequence detected: Checking and repairing the db...
[SYNO4] 03:53:33 INFO: Repaired 3668 sequence entries in database
[SYNO4] 04:29:33 WARNING: Non-increasing sequence detected: Checking and repairing the db...
[SYNO4] 04:29:33 INFO: Repaired 9 sequence entries in database
[SYNO4] 04:29:33 WARNING: Non-increasing sequence detected: Checking and repairing the db...
[SYNO4] 04:29:33 INFO: Repaired 343 sequence entries in database
jb@kvin:~ %

(“my id” lines to indicate when syncthing was or wasn’t restarted)

There are no dates, but the latest bursts are yesterday (~20:37) and during the night (03:53 and 04:29). There are no changes to my files at those times. There were likely rescans. Currently, this computer is busy scanning a lot of “changes” in one of my larger folders; because the file entries were rewritten perhaps? Which is why I noticed this, because of the activity and notices.

Screen Shot 2020-05-08 at 10 46 48

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 20 (20 by maintainers)

Commits related to this issue

Most upvoted comments

😦 Sorry about that.

We’re cool on this, we don’t have a release yet out with the bloom filter change. It’s just me being bleeding edge. But yeah, I’ll rather do that revert than bigger changes right now.

[SYNO4] 2020/05/08 11:40:43.136499 lowlevel.go:599: INFO: gc: new bloom filter with capacity 100000
[SYNO4] 2020/05/08 11:40:43.136600 lowlevel.go:609: INFO: gc: iterating files
[SYNO4] 2020/05/08 11:40:43.300000 lowlevel.go:636: INFO: gc: added 230322 block entries to filter, skipped 0 empty ones
[SYNO4] 2020/05/08 11:40:43.300014 lowlevel.go:641: INFO: gc: iterating block lists
[SYNO4] 2020/05/08 11:40:43.516113 lowlevel.go:669: INFO: gc: matched 400 block lists, dropped 60874 unused ones

🙄