Open wobure123 opened 2 weeks ago
Frankly, with a filesystem implementation that stupid, I think you'll run into lots of issues and assumptions where Syncthing won't work well. It seems to me like it might be an inappropriate setup, where the correct solution would be to run Syncthing wherever the webdav server lives.
Personal special implementation 😁, works fine for months,gonna see how far it will go after unconment those code ~
Feature description
Hope to provide a configuration parameter that allows customization to cancel the search for and copying of required blocks from other directories on syncthing machine device
Problem or use case
I use Syncthing as the server in a WebDAV file system, and everything works fine. However, a bug occurs when syncing files with identical hash values. Syncthing prioritizes copying blocks from existing files in other folders, causing the original file to be cyclically downloaded via WebDAV: one download for each copied block. This essentially causes the synchronization process to hang. Currently, I've resolved the bug by commenting out the following code (
lib/model/folder_sendrecv.go
) and recompiling my own release. I hope a parameter can be provided for custom control , making it more elegant for adapting to WebDAV file systems.Alternatives or workarounds
none