# Some deletions and modifications getting stuck in sync since v1.27.5

**URL:** https://forum.syncthing.net/t/some-deletions-and-modifications-getting-stuck-in-sync-since-v1-27-5/21893
**Category:** Support
**Created:** [April 3, 2024, 9:15pm UTC](https://forum.syncthing.net/t/some-deletions-and-modifications-getting-stuck-in-sync-since-v1-27-5/21893 "2024-04-03T21:15:45Z")
**Posts on this page:** 20
**Page:** 1

<div class="post-metadata">

### Author: ![tomasz86](https://forum.syncthing.net/letter_avatar_proxy/v4/letter/t/96bed5/32.png) [@tomasz86](https://forum.syncthing.net/u/tomasz86)
#### Post date: [April 3, 2024, 9:15pm UTC](https://forum.syncthing.net/t/some-deletions-and-modifications-getting-stuck-in-sync-since-v1-27-5/21893/1 "2024-04-03T21:15:45Z")

</div>

There’s a possibility that the issue unrelated to the newest version of Syncthing, however since I upgraded to v1.27.5 on multiple devices yesterday, I’m starting to see some deletions getting seemingly “stuck” in sync as below.

 ![image](https://forum-uploads.syncthingcdn.net/original/3X/0/b/0b7028fd5a2e70e347320e5d78de20646d738bc2.png)

So far I’ve got rid of them by recreating the deleted files manually, then deleting them again. However, this is happening in multiple folders, and I’ve never seen such behaviour before v1.27.5.

I’m going to update the topic if I either manage to gather more information or find the actual culprit.

**Edit** :

I’ve gone through the commits between v1.27.4 and v1.27.5 and I’m thinking that maybe it’s related to [lib/model: Prevent infinite index sending loop (fixes #9407) (#9458) · syncthing/syncthing@73cc555 · GitHub](https://github.com/syncthing/syncthing/commit/73cc5553b623dbbe71b75ddd0add9b89dca6714a) but I’m not sure, especially without testing. However, I’ve also now checked all my devices, and I’m seeing files that are seemingly stuck in sync in multiple folders, on multiple devices. They are also not all deletions, as some of them are just modifications.

For the record, it seems that they are only “stuck” in the GUI, as the actual changes have synced, i.e. the deleted files themselves have been deleted, etc.

---

<div class="post-metadata">

### Author: ![tomasz86](https://forum.syncthing.net/letter_avatar_proxy/v4/letter/t/96bed5/32.png) [@tomasz86](https://forum.syncthing.net/u/tomasz86)
#### Post date: [April 4, 2024, 6:55am UTC](https://forum.syncthing.net/t/some-deletions-and-modifications-getting-stuck-in-sync-since-v1-27-5/21893/2 "2024-04-04T06:55:10Z")

</div>

I reverted [lib/model: Prevent infinite index sending loop (fixes #9407) (#9458) · syncthing/syncthing@73cc555 · GitHub](https://github.com/syncthing/syncthing/commit/73cc5553b623dbbe71b75ddd0add9b89dca6714a) in my personal build a few hours ago and installed it on all devices, and since then nothing got “stuck” in sync, so I’d say the linked commit is the culprit, but the question still remains why… 😕

---

<div class="post-metadata">

### Author: ![calmh](https://forum.syncthing.net/user_avatar/forum.syncthing.net/calmh/32/15311_2.png) [@calmh](https://forum.syncthing.net/u/calmh)
#### Post date: [April 4, 2024, 7:10am UTC](https://forum.syncthing.net/t/some-deletions-and-modifications-getting-stuck-in-sync-since-v1-27-5/21893/3 "2024-04-04T07:10:55Z")

</div>

Since you’re in there hacking, could you add a print for the case where the two sequence numbers mismatch and see if that triggers for you?

---

<div class="post-metadata">

### Author: ![tomasz86](https://forum.syncthing.net/letter_avatar_proxy/v4/letter/t/96bed5/32.png) [@tomasz86](https://forum.syncthing.net/u/tomasz86)
#### Post date: [April 4, 2024, 9:51pm UTC](https://forum.syncthing.net/t/some-deletions-and-modifications-getting-stuck-in-sync-since-v1-27-5/21893/4 "2024-04-04T21:51:06Z")

</div>

I am into hacking but also, to be honest, I’ve got little idea what I’m doing when it comes to the Go code.

Should I add something like this?

```plaintext
	if s.prevSequence != f.Sequence {
		l.Warnln("current sequence:", f.Sequence, ", previous sequence:", s.prevSequence)
	}

```

I’m going to play with this in my test environment, as I can confirm 100% now that the problem is gone with the commit reverted, however it was a major pain to get rid of all the files that were “stuck” in my real Syncthing setup (as I had to track each of them separately, recreate, then delete again, etc.) and I really don’t want to do it again.

---

<div class="post-metadata">

### Author: ![calmh](https://forum.syncthing.net/user_avatar/forum.syncthing.net/calmh/32/15311_2.png) [@calmh](https://forum.syncthing.net/u/calmh)
#### Post date: [April 4, 2024, 10:08pm UTC](https://forum.syncthing.net/t/some-deletions-and-modifications-getting-stuck-in-sync-since-v1-27-5/21893/5 "2024-04-04T22:08:54Z")

</div>

`if snap.Sequence(protocol.LocalDeviceID) != f.Sequence { ... badness }`

note that some badness is expected as per the comment in the commit, e.g., you might see this trigger for reverted files in receive only folder or whatever.

---

<div class="post-metadata">

### Author: ![tomasz86](https://forum.syncthing.net/letter_avatar_proxy/v4/letter/t/96bed5/32.png) [@tomasz86](https://forum.syncthing.net/u/tomasz86)
#### Post date: [April 4, 2024, 10:36pm UTC](https://forum.syncthing.net/t/some-deletions-and-modifications-getting-stuck-in-sync-since-v1-27-5/21893/6 "2024-04-04T22:36:15Z")

</div>

Thanks, I’ve added it like this:

```plaintext
	if snap.Sequence(protocol.LocalDeviceID) != f.Sequence {
		l.Warnln(snap.Sequence(protocol.LocalDeviceID), f.Sequence)
	}

```

I’ve set two local Syncthing instances that sync the real folder where the problem happened but only between each other. If I can’t reproduce the issue this way, then I’m probably going to do it in my real configuration again, dealing with the consequences.

---

<div class="post-metadata">

### Author: ![tomasz86](https://forum.syncthing.net/letter_avatar_proxy/v4/letter/t/96bed5/32.png) [@tomasz86](https://forum.syncthing.net/u/tomasz86)
#### Post date: [April 5, 2024, 9:53am UTC](https://forum.syncthing.net/t/some-deletions-and-modifications-getting-stuck-in-sync-since-v1-27-5/21893/7 "2024-04-05T09:53:26Z")

</div>

As often is the case when trying to reproduce an issue, nothing has happened in my test environment which ran for about ~10 hours. I’ve now began testing the “debug” version on two of my real devices, which suffered from the original issue previously.

The whole code looks like this:

```plaintext
	// Use the sequence of the snapshot we iterated as a starting point for the
	// next run. Previously we used the sequence of the last file we sent,
	// however it's possible that a higher sequence exists, just doesn't need to
	// be sent (e.g. in a receive-only folder, when a local change was
	// reverted). No point trying to send nothing again.
	if snap.Sequence(protocol.LocalDeviceID) != f.Sequence {
		l.Warnln(snap.Sequence(protocol.LocalDeviceID), f.Sequence)
	}
	s.prevSequence = snap.Sequence(protocol.LocalDeviceID)

```

So far, I’ve only noticed that upon starting Syncthing, there are always a few of these recorded.

![image](https://forum-uploads.syncthingcdn.net/original/3X/c/2/c29d2692070b45912f14aa39cf1905c1d3b18254.png)

---

<div class="post-metadata">

### Author: ![imsodin](https://forum.syncthing.net/user_avatar/forum.syncthing.net/imsodin/32/3317_2.png) [@imsodin](https://forum.syncthing.net/u/imsodin)
#### Post date: [April 5, 2024, 10:44am UTC](https://forum.syncthing.net/t/some-deletions-and-modifications-getting-stuck-in-sync-since-v1-27-5/21893/8 "2024-04-05T10:44:58Z")

</div>

Edit: I wrote this before noticing the latest post by @tomasz86 .

There are two bits of info here I can’t really reconcile:

> [@tomasz86](#):
>
> For the record, it seems that they are only “stuck” in the GUI, as the actual changes have synced, i.e. the deleted files themselves have been deleted, etc.

> [@tomasz86](#):
>
> I reverted [lib/model: Prevent infinite index sending loop (fixes #9407) (#9458) · syncthing/syncthing@73cc555 · GitHub](https://github.com/syncthing/syncthing/commit/73cc5553b623dbbe71b75ddd0add9b89dca6714a) in my personal build a few hours ago and installed it on all devices, and since then nothing got “stuck” in sync, so I’d say the linked commit is the culprit, but the question still remains why… 😕

If the actual changes propagate, and it’s “just” the web UI being out of sync, to me that would indicate an issue with the api or events, not actual index handling. If the index information doesn’t propagate properly, the syncing shouldn’t either. Unless a 3rd device with the same folder is involved, then then the information can propagate that way.  
And reverting is a pretty strong indicator, however given the non-reproducible nature I don’t think it’s out of the question that the reset incurred by the rebuild and restart had an impact and it’s a red herring. Not saying it is, just an option.  
Maybe you can be more specific as to what happened that indicated it was UI only?

---

<div class="post-metadata">

### Author: ![imsodin](https://forum.syncthing.net/user_avatar/forum.syncthing.net/imsodin/32/3317_2.png) [@imsodin](https://forum.syncthing.net/u/imsodin)
#### Post date: [April 5, 2024, 10:46am UTC](https://forum.syncthing.net/t/some-deletions-and-modifications-getting-stuck-in-sync-since-v1-27-5/21893/9 "2024-04-05T10:46:51Z")

</div>

> [@tomasz86](#):
>
> So far, I’ve only noticed that upon starting Syncthing, there are always a few of these recorded.

~~These are send-receive folders?~~

Never mind, these are expected: We call `sendIndexTo` once always when establishing a new connection. If there is nothing to send, what’s seen in those logs is expected: Snapshot shows the current sequence, while there is no file and thus seq zero there.

---

<div class="post-metadata">

### Author: ![tomasz86](https://forum.syncthing.net/letter_avatar_proxy/v4/letter/t/96bed5/32.png) [@tomasz86](https://forum.syncthing.net/u/tomasz86)
#### Post date: [April 5, 2024, 11:10am UTC](https://forum.syncthing.net/t/some-deletions-and-modifications-getting-stuck-in-sync-since-v1-27-5/21893/10 "2024-04-05T11:10:40Z")

</div>

> [@imsodin](#):
>
> Maybe you can be more specific as to what happened that indicated it was UI only?

I’m sorry if I wasn’t clear enough. It was only about the GUI, because the GUI had the files still “stuck” in sync, while in reality, the deletions did propagate and the files themselves were already gone from the disk. In other words, it seemed as if Syncthing was trying to sync the deletions twice. The same was true for the modifications.

> [@imsodin](#):
>
> If the actual changes propagate, and it’s “just” the web UI being out of sync, to me that would indicate an issue with the api or events, not actual index handling. If the index information doesn’t propagate properly, the syncing shouldn’t either. Unless a 3rd device with the same folder is involved, then then the information can propagate that way.

The test environment, where nothing unusual happened, consisted of three devices connected as A → B → C, while the normal setup, where the issue was happening, is a much more complex one with 15+ devices, but not all are interconnected. I was seeing the same issue on multiple of them, in several folders.

---

<div class="post-metadata">

### Author: ![tomasz86](https://forum.syncthing.net/letter_avatar_proxy/v4/letter/t/96bed5/32.png) [@tomasz86](https://forum.syncthing.net/u/tomasz86)
#### Post date: [April 5, 2024, 11:56am UTC](https://forum.syncthing.net/t/some-deletions-and-modifications-getting-stuck-in-sync-since-v1-27-5/21893/11 "2024-04-05T11:56:07Z")

</div>

I think I’ve got something.

- ![image](https://forum-uploads.syncthingcdn.net/original/3X/b/3/b38863732f5400b4b54766542f2b6c67f7dfb011.jpeg)
- ![image](https://forum-uploads.syncthingcdn.net/original/3X/1/8/1806c42c3f06018b95a4f52672452e3433df9309.png)
- ![image](https://forum-uploads.syncthingcdn.net/original/3X/5/e/5e73c22c61205842027383c50036effb182ec301.png)

There appears to be one modification that the GUI thinks is stuck in sync, however the file itself has already been synced onto the disk.

What do you think? I’ve got no additional debug logging enabled right now. Should I enable anything specific that could be helpful for troubleshooting?

**Edit** :

More screenshots from multiple devices and more deletions/modifications getting “stuck” in sync.

---

<div class="post-metadata">

### Author: ![calmh](https://forum.syncthing.net/user_avatar/forum.syncthing.net/calmh/32/15311_2.png) [@calmh](https://forum.syncthing.net/u/calmh)
#### Post date: [April 5, 2024, 1:46pm UTC](https://forum.syncthing.net/t/some-deletions-and-modifications-getting-stuck-in-sync-since-v1-27-5/21893/12 "2024-04-05T13:46:59Z")

</div>

So, when taking a “snapshot” we don’t hold the update lock:

> <https://github.com/syncthing/syncthing/blob/bdfd0f0548d2f6fc4b5500690dbd383baa3b0561/lib/db/set.go#L168-L184>

So there’s nothing in principle that prevents the sequence number from increasing between us creating the database snapshot and taking the metadata snapshot.

Now wether that matches the symptoms or not I don’t think (it would result in files not sent, so always out of sync on the peer from the sending point of view), but it’s not great.

---

<div class="post-metadata">

### Author: ![calmh](https://forum.syncthing.net/user_avatar/forum.syncthing.net/calmh/32/15311_2.png) [@calmh](https://forum.syncthing.net/u/calmh)
#### Post date: [April 5, 2024, 1:49pm UTC](https://forum.syncthing.net/t/some-deletions-and-modifications-getting-stuck-in-sync-since-v1-27-5/21893/13 "2024-04-05T13:49:49Z")

</div>

@tomasz86 see if this has any effect

```diff
 lib/db/set.go | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/lib/db/set.go b/lib/db/set.go
index 84cfb3452..fb4a9fda5 100644
--- a/lib/db/set.go
+++ b/lib/db/set.go
@@ -168,6 +168,10 @@ type Snapshot struct {
 func (s *FileSet) Snapshot() (*Snapshot, error) {
 	opStr := fmt.Sprintf("%s Snapshot()", s.folder)
 	l.Debugf(opStr)
+
+	s.updateMutex.Lock()
+	defer s.updateMutex.Unlock()
+
 	t, err := s.db.newReadOnlyTransaction()
 	if err != nil {
 		s.db.handleFailure(err)

```

(next we’ll see if we ever try to take a snapshot from within a write transaction :p)

---

<div class="post-metadata">

### Author: ![imsodin](https://forum.syncthing.net/user_avatar/forum.syncthing.net/imsodin/32/3317_2.png) [@imsodin](https://forum.syncthing.net/u/imsodin)
#### Post date: [April 5, 2024, 3:21pm UTC](https://forum.syncthing.net/t/some-deletions-and-modifications-getting-stuck-in-sync-since-v1-27-5/21893/14 "2024-04-05T15:21:12Z")

</div>

Oh what a great find. It nicely fits that the reverted commit made this worse, as we before didn’t care about the snapshot sequence. Also the overall symptoms seem plausible:

1. DB write in progress.
2. Index sending at the same time: DB snapshot: index at A
3. DB write commits new stuff.
4. Index sending: Meta snapshot: seq at A+1 (I’d have expected A + index-batch-size ?).
5. Index sending: Iterate over DB until index A.
6. Index sending: Update last seq to index from meta snapshot: A+1.

File with seq A+1 is never sent to remote.

---

<div class="post-metadata">

### Author: ![tomasz86](https://forum.syncthing.net/letter_avatar_proxy/v4/letter/t/96bed5/32.png) [@tomasz86](https://forum.syncthing.net/u/tomasz86)
#### Post date: [April 5, 2024, 8:16pm UTC](https://forum.syncthing.net/t/some-deletions-and-modifications-getting-stuck-in-sync-since-v1-27-5/21893/15 "2024-04-05T20:16:12Z")

</div>

I’ve added the lock and I’ve also added `f.Sequence > 0` to the other code to reduce the noise:

```plaintext
if f.Sequence > 0 && snap.Sequence(protocol.LocalDeviceID) != f.Sequence {
	l.Warnln(snap.Sequence(protocol.LocalDeviceID), f.Sequence)
}

```

It’s been running like that on all devices for a few hours now, and there have been zero warnings so far.

---

<div class="post-metadata">

### Author: ![calmh](https://forum.syncthing.net/user_avatar/forum.syncthing.net/calmh/32/15311_2.png) [@calmh](https://forum.syncthing.net/u/calmh)
#### Post date: [April 5, 2024, 9:44pm UTC](https://forum.syncthing.net/t/some-deletions-and-modifications-getting-stuck-in-sync-since-v1-27-5/21893/16 "2024-04-05T21:44:40Z")

</div>

I dropped an RC with the probable fix, for anyone who feel they be hit by this. Will roll it out on a couple of days unless someone screams.

---

<div class="post-metadata">

### Author: ![nikow](https://forum.syncthing.net/user_avatar/forum.syncthing.net/nikow/32/16327_2.png) [@nikow](https://forum.syncthing.net/u/nikow)
#### Post date: [April 7, 2024, 9:30pm UTC](https://forum.syncthing.net/t/some-deletions-and-modifications-getting-stuck-in-sync-since-v1-27-5/21893/17 "2024-04-07T21:30:30Z")

</div>

I think i am affected by the same bug, but in my case files are not synced for few days already (files itself has been sent, but not deleted after). I use syncthing to synchronize mainly WriteAheadFiles sender to receiver, but i have send&receive on both sides. From sender it looks like follows:

 ![image](https://forum-uploads.syncthingcdn.net/original/3X/9/e/9ed2a1cb713afb9d6d012725f5d6dc8db9305a08.png)

From receiver it looks more complicated. The folder sees different size and number of files:

 ![image](https://forum-uploads.syncthingcdn.net/original/3X/8/7/879ca9ae6acc09f5643a925d33a22fbfb7e5bc16.png)

And device view is stuck too:

 ![image](https://forum-uploads.syncthingcdn.net/original/3X/8/a/8a32163f57717704d87f988daf379ac34b2e1bc1.png)

And out of sync tab:

 ![image](https://forum-uploads.syncthingcdn.net/original/3X/1/6/162650aa81fe4113698d38adfbb6d3e3a06a6764.png)

Lucky for me date of creation of file contains datetime in YYYYMMDDHHmmss format, so i know exacly when files has been created. First one should be 40MB and second one 36MB.

I recovered the log audit and log files from the backup. The main log says it was synced and changed:

> syncthing.log.2024-04-03T18:36:25:[MKOIB] 2024/04/03 22:53:16 VERBOSE: Started syncing “utym6-2eckq” / “fn1\_hmd\_20240403225301.data” (update file) syncthing.log.2024-04-03T18:36:25:[MKOIB] 2024/04/03 22:55:01 VERBOSE: Finished syncing “utym6-2eckq” / “fn1\_hmd\_20240403225301.data” (update file): Success syncthing.log.2024-04-03T18:36:25:[MKOIB] 2024/04/03 22:55:01 VERBOSE: Remote change detected in folder “utym6-2eckq”: modified file fn1\_hmd\_20240403225301.data syncthing.log.2024-04-03T18:36:25:[MKOIB] 2024/04/03 22:56:53 VERBOSE: Local change detected in folder “utym6-2eckq”: deleted file fn1\_hmd\_20240403225301.data

The audit log says:

> audit-20240403-183625.log:{“id”:7204,“globalID”:7204,“time”:“2024-04-03T22:53:16.714886061+02:00”,“type”:“ItemStarted”,“data”:{“action”:“update”,“folder”:“utym6-2eckq”,“item”:“fn1\_hmd\_20240403225301.data”,“type”:“file”}} audit-20240403-183625.log:{“id”:7206,“globalID”:7206,“time”:“2024-04-03T22:53:21.714575666+02:00”,“type”:“DownloadProgress”,“data”:{“utym6-2eckq”:{“fn1\_hmd\_20240403225301.data”:{“total”:314,“reused”:0,“copiedFromOrigin”:0,“copiedFromOriginShifted”:0,“copiedFromElsewhere”:0,“pulled”:1,“pulling”:123,“bytesDone”:130870,“bytesTotal”:41093096},“fn1\_hmd\_20240403225302.data”:{“total”:286,“reused”:0,“copiedFromOrigin”:0,“copiedFromOriginShifted”:0,“copiedFromElsewhere”:0,“pulled”:6,“pulling”:136,“bytesDone”:784738,“bytesTotal”:37405800}}}} audit-20240403-183625.log:{“id”:7209,“globalID”:7209,“time”:“2024-04-03T22:53:26.715074855+02:00”,“type”:“DownloadProgress”,“data”:{“utym6-2eckq”:{“fn1\_hmd\_20240403225301.data”:{“total”:314,“reused”:0,“copiedFromOrigin”:0,“copiedFromOriginShifted”:0,“copiedFromElsewhere”:0,“pulled”:4,“pulling”:125,“bytesDone”:523479,“bytesTotal”:41093096},“fn1\_hmd\_20240403225302.data”:{“total”:286,“reused”:0,“copiedFromOrigin”:0,“copiedFromOriginShifted”:0,“copiedFromElsewhere”:0,“pulled”:12,“pulling”:134,“bytesDone”:1569475,“bytesTotal”:37405800}}}} audit-20240403-183625.log:{“id”:7212,“globalID”:7212,“time”:“2024-04-03T22:53:31.716091223+02:00”,“type”:“DownloadProgress”,“data”:{“utym6-2eckq”:{“fn1\_hmd\_20240403225301.data”:{“total”:314,“reused”:0,“copiedFromOrigin”:0,“copiedFromOriginShifted”:0,“copiedFromElsewhere”:0,“pulled”:7,“pulling”:130,“bytesDone”:916089,“bytesTotal”:41093096},“fn1\_hmd\_20240403225302.data”:{“total”:286,“reused”:0,“copiedFromOrigin”:0,“copiedFromOriginShifted”:0,“copiedFromElsewhere”:0,“pulled”:24,“pulling”:129,“bytesDone”:3138949,“bytesTotal”:37405800}}}} audit-20240403-183625.log:{“id”:7226,“globalID”:7226,“time”:“2024-04-03T22:53:41.717661779+02:00”,“type”:“DownloadProgress”,“data”:{“utym6-2eckq”:{“fn1\_hmd\_20240403225301.data”:{“total”:314,“reused”:0,“copiedFromOrigin”:0,“copiedFromOriginShifted”:0,“copiedFromElsewhere”:0,“pulled”:36,“pulling”:129,“bytesDone”:4711311,“bytesTotal”:41093096},“fn1\_hmd\_20240403225302.data”:{“total”:286,“reused”:0,“copiedFromOrigin”:0,“copiedFromOriginShifted”:0,“copiedFromElsewhere”:0,“pulled”:48,“pulling”:130,“bytesDone”:6277897,“bytesTotal”:37405800}}}} audit-20240403-183625.log:{“id”:7229,“globalID”:7229,“time”:“2024-04-03T22:53:46.717860338+02:00”,“type”:“DownloadProgress”,“data”:{“utym6-2eckq”:{“fn1\_hmd\_20240403225301.data”:{“total”:314,“reused”:0,“copiedFromOrigin”:0,“copiedFromOriginShifted”:0,“copiedFromElsewhere”:0,“pulled”:54,“pulling”:126,“bytesDone”:7066966,“bytesTotal”:41093096},“fn1\_hmd\_20240403225302.data”:{“total”:286,“reused”:0,“copiedFromOrigin”:0,“copiedFromOriginShifted”:0,“copiedFromElsewhere”:0,“pulled”:61,“pulling”:133,“bytesDone”:7978161,“bytesTotal”:37405800}}}} audit-20240403-183625.log:{“id”:7234,“globalID”:7234,“time”:“2024-04-03T22:53:51.718637369+02:00”,“type”:“DownloadProgress”,“data”:{“utym6-2eckq”:{“fn1\_hmd\_20240403225301.data”:{“total”:314,“reused”:0,“copiedFromOrigin”:0,“copiedFromOriginShifted”:0,“copiedFromElsewhere”:0,“pulled”:68,“pulling”:125,“bytesDone”:8899142,“bytesTotal”:41093096},“fn1\_hmd\_20240403225302.data”:{“total”:286,“reused”:0,“copiedFromOrigin”:0,“copiedFromOriginShifted”:0,“copiedFromElsewhere”:0,“pulled”:73,“pulling”:134,“bytesDone”:9547635,“bytesTotal”:37405800}}}} audit-20240403-183625.log:{“id”:7237,“globalID”:7237,“time”:“2024-04-03T22:53:56.72185827+02:00”,“type”:“DownloadProgress”,“data”:{“utym6-2eckq”:{“fn1\_hmd\_20240403225301.data”:{“total”:314,“reused”:0,“copiedFromOrigin”:0,“copiedFromOriginShifted”:0,“copiedFromElsewhere”:0,“pulled”:78,“pulling”:126,“bytesDone”:10207840,“bytesTotal”:41093096},“fn1\_hmd\_20240403225302.data”:{“total”:286,“reused”:0,“copiedFromOrigin”:0,“copiedFromOriginShifted”:0,“copiedFromElsewhere”:0,“pulled”:86,“pulling”:133,“bytesDone”:11247898,“bytesTotal”:37405800}}}} audit-20240403-183625.log:{“id”:7240,“globalID”:7240,“time”:“2024-04-03T22:54:01.722073015+02:00”,“type”:“DownloadProgress”,“data”:{“utym6-2eckq”:{“fn1\_hmd\_20240403225301.data”:{“total”:314,“reused”:0,“copiedFromOrigin”:0,“copiedFromOriginShifted”:0,“copiedFromElsewhere”:0,“pulled”:89,“pulling”:130,“bytesDone”:11647407,“bytesTotal”:41093096},“fn1\_hmd\_20240403225302.data”:{“total”:286,“reused”:0,“copiedFromOrigin”:0,“copiedFromOriginShifted”:0,“copiedFromElsewhere”:0,“pulled”:103,“pulling”:129,“bytesDone”:13471320,“bytesTotal”:37405800}}}} audit-20240403-183625.log:{“id”:7243,“globalID”:7243,“time”:“2024-04-03T22:54:06.722428279+02:00”,“type”:“DownloadProgress”,“data”:{“utym6-2eckq”:{“fn1\_hmd\_20240403225301.data”:{“total”:314,“reused”:0,“copiedFromOrigin”:0,“copiedFromOriginShifted”:0,“copiedFromElsewhere”:0,“pulled”:97,“pulling”:130,“bytesDone”:12694365,“bytesTotal”:41093096},“fn1\_hmd\_20240403225302.data”:{“total”:286,“reused”:0,“copiedFromOrigin”:0,“copiedFromOriginShifted”:0,“copiedFromElsewhere”:0,“pulled”:112,“pulling”:129,“bytesDone”:14648426,“bytesTotal”:37405800}}}} audit-20240403-183625.log:{“id”:7246,“globalID”:7246,“time”:“2024-04-03T22:54:11.723127876+02:00”,“type”:“DownloadProgress”,“data”:{“utym6-2eckq”:{“fn1\_hmd\_20240403225301.data”:{“total”:314,“reused”:0,“copiedFromOrigin”:0,“copiedFromOriginShifted”:0,“copiedFromElsewhere”:0,“pulled”:98,“pulling”:131,“bytesDone”:12825234,“bytesTotal”:41093096},“fn1\_hmd\_20240403225302.data”:{“total”:286,“reused”:0,“copiedFromOrigin”:0,“copiedFromOriginShifted”:0,“copiedFromElsewhere”:0,“pulled”:114,“pulling”:128,“bytesDone”:14910005,“bytesTotal”:37405800}}}} audit-20240403-183625.log:{“id”:7249,“globalID”:7249,“time”:“2024-04-03T22:54:16.723350306+02:00”,“type”:“DownloadProgress”,“data”:{“utym6-2eckq”:{“fn1\_hmd\_20240403225301.data”:{“total”:314,“reused”:0,“copiedFromOrigin”:0,“copiedFromOriginShifted”:0,“copiedFromElsewhere”:0,“pulled”:117,“pulling”:136,“bytesDone”:15311759,“bytesTotal”:41093096},“fn1\_hmd\_20240403225302.data”:{“total”:286,“reused”:0,“copiedFromOrigin”:0,“copiedFromOriginShifted”:0,“copiedFromElsewhere”:0,“pulled”:135,“pulling”:123,“bytesDone”:17656584,“bytesTotal”:37405800}}}} audit-20240403-183625.log:{“id”:7262,“globalID”:7262,“time”:“2024-04-03T22:54:26.723801696+02:00”,“type”:“DownloadProgress”,“data”:{“utym6-2eckq”:{“fn1\_hmd\_20240403225301.data”:{“total”:314,“reused”:0,“copiedFromOrigin”:0,“copiedFromOriginShifted”:0,“copiedFromElsewhere”:0,“pulled”:141,“pulling”:134,“bytesDone”:18452633,“bytesTotal”:41093096},“fn1\_hmd\_20240403225302.data”:{“total”:286,“reused”:0,“copiedFromOrigin”:0,“copiedFromOriginShifted”:0,“copiedFromElsewhere”:0,“pulled”:156,“pulling”:125,“bytesDone”:20403164,“bytesTotal”:37405800}}}} audit-20240403-183625.log:{“id”:7267,“globalID”:7267,“time”:“2024-04-03T22:54:31.724550224+02:00”,“type”:“DownloadProgress”,“data”:{“utym6-2eckq”:{“fn1\_hmd\_20240403225301.data”:{“total”:314,“reused”:0,“copiedFromOrigin”:0,“copiedFromOriginShifted”:0,“copiedFromElsewhere”:0,“pulled”:149,“pulling”:135,“bytesDone”:19499591,“bytesTotal”:41093096},“fn1\_hmd\_20240403225302.data”:{“total”:286,“reused”:0,“copiedFromOrigin”:0,“copiedFromOriginShifted”:0,“copiedFromElsewhere”:0,“pulled”:163,“pulling”:123,“bytesDone”:21318691,“bytesTotal”:37405800}}}} audit-20240403-183625.log:{“id”:7280,“globalID”:7280,“time”:“2024-04-03T22:54:36.725334503+02:00”,“type”:“DownloadProgress”,“data”:{“utym6-2eckq”:{“fn1\_hmd\_20240403225301.data”:{“total”:314,“reused”:0,“copiedFromOrigin”:0,“copiedFromOriginShifted”:0,“copiedFromElsewhere”:0,“pulled”:164,“pulling”:149,“bytesDone”:21462637,“bytesTotal”:41093096},“fn1\_hmd\_20240403225302.data”:{“total”:286,“reused”:0,“copiedFromOrigin”:0,“copiedFromOriginShifted”:0,“copiedFromElsewhere”:0,“pulled”:177,“pulling”:109,“bytesDone”:23149744,“bytesTotal”:37405800}}}} audit-20240403-183625.log:{“id”:7283,“globalID”:7283,“time”:“2024-04-03T22:54:41.726431435+02:00”,“type”:“DownloadProgress”,“data”:{“utym6-2eckq”:{“fn1\_hmd\_20240403225301.data”:{“total”:314,“reused”:0,“copiedFromOrigin”:0,“copiedFromOriginShifted”:0,“copiedFromElsewhere”:0,“pulled”:178,“pulling”:136,“bytesDone”:23294813,“bytesTotal”:41093096},“fn1\_hmd\_20240403225302.data”:{“total”:286,“reused”:0,“copiedFromOrigin”:0,“copiedFromOriginShifted”:0,“copiedFromElsewhere”:0,“pulled”:193,“pulling”:93,“bytesDone”:25242376,“bytesTotal”:37405800}}}} audit-20240403-183625.log:{“id”:7286,“globalID”:7286,“time”:“2024-04-03T22:54:46.726644436+02:00”,“type”:“DownloadProgress”,“data”:{“utym6-2eckq”:{“fn1\_hmd\_20240403225301.data”:{“total”:314,“reused”:0,“copiedFromOrigin”:0,“copiedFromOriginShifted”:0,“copiedFromElsewhere”:0,“pulled”:193,“pulling”:121,“bytesDone”:25257859,“bytesTotal”:41093096},“fn1\_hmd\_20240403225302.data”:{“total”:286,“reused”:0,“copiedFromOrigin”:0,“copiedFromOriginShifted”:0,“copiedFromElsewhere”:0,“pulled”:208,“pulling”:78,“bytesDone”:27204219,“bytesTotal”:37405800}}}} audit-20240403-183625.log:{“id”:7289,“globalID”:7289,“time”:“2024-04-03T22:54:51.728088034+02:00”,“type”:“DownloadProgress”,“data”:{“utym6-2eckq”:{“fn1\_hmd\_20240403225301.data”:{“total”:314,“reused”:0,“copiedFromOrigin”:0,“copiedFromOriginShifted”:0,“copiedFromElsewhere”:0,“pulled”:218,“pulling”:96,“bytesDone”:28529602,“bytesTotal”:41093096},“fn1\_hmd\_20240403225302.data”:{“total”:286,“reused”:0,“copiedFromOrigin”:0,“copiedFromOriginShifted”:0,“copiedFromElsewhere”:0,“pulled”:231,“pulling”:55,“bytesDone”:30212377,“bytesTotal”:37405800}}}} audit-20240403-183625.log:{“id”:7295,“globalID”:7295,“time”:“2024-04-03T22:54:56.729047872+02:00”,“type”:“DownloadProgress”,“data”:{“utym6-2eckq”:{“fn1\_hmd\_20240403225301.data”:{“total”:314,“reused”:0,“copiedFromOrigin”:0,“copiedFromOriginShifted”:0,“copiedFromElsewhere”:0,“pulled”:248,“pulling”:66,“bytesDone”:32455694,“bytesTotal”:41093096},“fn1\_hmd\_20240403225302.data”:{“total”:286,“reused”:0,“copiedFromOrigin”:0,“copiedFromOriginShifted”:0,“copiedFromElsewhere”:0,“pulled”:254,“pulling”:32,“bytesDone”:33220536,“bytesTotal”:37405800}}}} audit-20240403-183625.log:{“id”:7301,“globalID”:7301,“time”:“2024-04-03T22:55:01.260517205+02:00”,“type”:“ItemFinished”,“data”:{“action”:“update”,“error”:null,“folder”:“utym6-2eckq”,“item”:“fn1\_hmd\_20240403225301.data”,“type”:“file”}} audit-20240403-183625.log:{“id”:7302,“globalID”:7302,“time”:“2024-04-03T22:55:01.267887766+02:00”,“type”:“LocalIndexUpdated”,“data”:{“filenames”:[“fn1\_hmd\_20240403225301.data”],“folder”:“utym6-2eckq”,“items”:1,“sequence”:2332,“version”:2332}} audit-20240403-183625.log:{“id”:7303,“globalID”:7303,“time”:“2024-04-03T22:55:01.267929542+02:00”,“type”:“RemoteChangeDetected”,“data”:{“action”:“modified”,“folder”:“utym6-2eckq”,“folderID”:“utym6-2eckq”,“label”:“offload”,“modifiedBy”:“FLM3W3O”,“path”:“fn1\_hmd\_20240403225301.data”,“type”:“file”}} audit-20240403-183625.log:{“id”:7407,“globalID”:7407,“time”:“2024-04-03T22:56:53.290183259+02:00”,“type”:“LocalIndexUpdated”,“data”:{“filenames”:[“fn1\_hmd\_20240403225301.data”,“fn1\_hmd\_20240403225302.data”],“folder”:“utym6-2eckq”,“items”:2,“sequence”:2336,“version”:2336}} audit-20240403-183625.log:{“id”:7408,“globalID”:7408,“time”:“2024-04-03T22:56:53.290217626+02:00”,“type”:“LocalChangeDetected”,“data”:{“action”:“deleted”,“folder”:“utym6-2eckq”,“folderID”:“utym6-2eckq”,“label”:“offload”,“modifiedBy”:“MKOIBGQ”,“path”:“fn1\_hmd\_20240403225301.data”,“type”:“file”}}

So basically files has been transfered correctly, then other automation processed said file and deleted it, but on sender side file exists and deletion of file has not been synchronized with “source” Freenet-Debian host.

Clicking on Rescan button or restarting both nodes does not help, so i suspect that’s not only GUI glitch.

---

<div class="post-metadata">

### Author: ![chri-bra](https://forum.syncthing.net/user_avatar/forum.syncthing.net/chri-bra/32/16338_2.png) [@chri-bra](https://forum.syncthing.net/u/chri-bra)
#### Post date: [April 8, 2024, 8:30pm UTC](https://forum.syncthing.net/t/some-deletions-and-modifications-getting-stuck-in-sync-since-v1-27-5/21893/18 "2024-04-08T20:30:30Z")

</div>

I also wanted to give some feedback on v1.27.6-rc.1.

My syncthing installation was also affected by the bug this week that the systems went out of sync. Unfortunately, before I found the relevant threads in the forum, I had rebuilt everything from scratch. And ran into the same errors/problems.

Now that I have installed v1.27.6-rc.1 everywhere, Syncthing is working fine again.

Thanks for the awesome tool. And the bugfix! 🙏 😃

---

<div class="post-metadata">

### Author: ![lightrush](https://forum.syncthing.net/user_avatar/forum.syncthing.net/lightrush/32/12484_2.png) [@lightrush](https://forum.syncthing.net/u/lightrush)
#### Post date: [April 16, 2024, 5:37am UTC](https://forum.syncthing.net/t/some-deletions-and-modifications-getting-stuck-in-sync-since-v1-27-5/21893/19 "2024-04-16T05:37:35Z")

</div>

I was trying to sync a large dataset on a new machine and I upgraded to 1.27.5 right before that. I was constantly getting strange out of sync issues. I thought I was losing my mind. Syncthing has been so solid for me over the years that I never considered it could be a bug. 😁 Time to donate!

Are existing databases alright having run on 1.27.5? Is there any action required after upgrading to 1.27.6? Trigger a manual rescan? Something else?

---

<div class="post-metadata">

### Author: ![calmh](https://forum.syncthing.net/user_avatar/forum.syncthing.net/calmh/32/15311_2.png) [@calmh](https://forum.syncthing.net/u/calmh)
#### Post date: [April 16, 2024, 6:20am UTC](https://forum.syncthing.net/t/some-deletions-and-modifications-getting-stuck-in-sync-since-v1-27-5/21893/20 "2024-04-16T06:20:57Z")

</div>

Should resolve automatically on upgrade.

[Next page](https://forum.syncthing.net/t/some-deletions-and-modifications-getting-stuck-in-sync-since-v1-27-5/21893.md?page=2)
