Syncthing DB Migration Errors?

Support
21

The selection of container source is entirely due to integration, as far as I’m concerned.

With Unraid if I do a search on Syncthing in the Apps menu, I get two repositories, Binhex and linuxserver. If I pick one of those, I know it’s going to work without too much effort, and I also know that the Unraid system will properly check for updates and let me know when I should update.

If I grab a container from any other source, it is likely going to be more work to get it working on Unraid, and I may or may not get the same level of integration with updates, the UI and so on.

I would suggest that in the build documentation that you guys strongly recommend native-C as most of the folks doing bundling of containers do actually read the build documentation.

I appreciate your looking into the memory issue. I suspect my somewhat large file set (half a million files, 25,000 directories, 11.4 TB being mirrored) and the lack of memory + swap on the Unraid server is causing the problem.

I’ve sourced some additional RAM to use temporarily on the server and will likely try the 2.0.2 to latest migration at some point, but will wait for 2.0.6 before doing that.

Thank you for looking into this and following through.

1 Like
22

It’s already listed in https://docs.syncthing.net/dev/building.html#prerequisites, but maybe adding a note about potential performance differences could be useful.

1 Like
23

The language on that page isn’t very strong.

“Usually, a C compiler. Syncthing uses SQLite for storing data and the most common implementation is written in C.”

I would very much encourage clearly stating here that SQLite should be compiled with native C for best performance… and if you like, mentioning that modernc is a poor choice.

The current wording makes it sound like any C compiler is fine.

2 Likes
24

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.