on 1.29.2, I just upgrade our storage, and moved the root of the data.
previously the user running the service had home at /A for example, now it is /B.
I did all the work with syncthing service down, and rebooted. Everything in the right place. UI shows “Unexpected Items” everywhere.
a diff -r /A /B shows nothing is different. Even checked the dates in case that is taken into account.
After clicking the red button to drop the unexpected files, almost everything (encrypted folders only on this host) change name. (now diff -rq /A /B | wc -l shows some 2k files changed)
ls -1R | wc -l (counting number of dirs/files) return the same, before and after. (some 6k files)
Q: Should I be worried, or the path root is part of the hash? And if so, how it was able to “fix” it?
edit: it probably doesn’t matter, but before it was md-raid1+ext4, now it is btrfs-raid1. File contents were the same (cp -a /A /B). service was properly systemctl stoped before anything.
edit2: synthing logs doesn’t show anything about this. Until I clicked the red button, then it shows 'Reverting unexpected items…"
What kind of Folder? Send & Receive or something else?
It seems like some of the Devices are untrusted – which Device is showing the “Unexpected Items” error? Did the password get changed as part of the previous changes?
What changes to Syncthing’s configuration did you make before restarting Syncthing?
Linux 6.12.9. - Other devices are mixed. Linux and Android, all 1.29.0 or 1.29.2.
But I think the error showed up as soon as syncthing started… not sure it saw other device online to start the error.
This host have a couple folders, type “receives encrypted”.
Simple file versioning. with empty (default) backup dir name.
not watching for changes.
pull random.
ignore permissions.
nothing for ownership and xattr options.
Nope. Again, just stop. move storage. start.
absolutely none. The user have everything setup from its home, the data move involved changing the user home to the new storage. The only change was in /etc/passwd. (reason why i rebooted instead of just restarting the service to be honest. always a mess to know what systemd will not update from those files)
the configs are ok. everything ok after “Reverting unexpected items” actions.
this was also all recently created on this very latest version i believe. will check the update logs but i think it was already started last week on 1.29.2
checked update logs for that host. No syncthing package ever upgraded, so it was installed as 1.29.2 from the start.
edit: seems I missed one question before:
It seems like some of the Devices are untrusted – which Device is showing the “Unexpected Items” error?
All folders are shared with central “untrusted” servers. So everything have password. The difference is the servers receive Encrypted. and the desktop/laptops/phones share among themselves and with unstrusted servers, with the same pass phrase on all devices.
Only this server showed the issue. Everything else chugged along as if nothing had happened during this.
Make sure you don’t set a password between devices which are both unencrypted. That used to work, but was never intended and causes problems since a few versions.
I did had to clean some .syncthing-encryption mixed with the clear text files after upgrading a laptop.
Yay for easy restore from version history too.
Edit: but relevant to this issue. the folder showing this was “receive encrypted”, so it only had the .syncthing-encrypt (i am sure i’m remebering the filename pattern wrong) and hashes for dir/filenames.
You can try looking at the file debug info from the command line for any file that is identified as a local addition:
syncthing cli debug file FILDER-ID RELATIVE-PATH
Not quite sure, but I think a dialog in the GUI should list the supposedly locally changed files, so you can pick a path from that. In the command output (JSON format), look for differences between the global and local file info sections.