Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failure to fsync() files should not be fatal #5704

calmh opened this issue May 9, 2019 · 0 comments


None yet
1 participant
Copy link

commented May 9, 2019

Sometimes it doesn't work over network filesystems. While we want to do it to ensure data on stable storage, failing the entire sync over it just guarantees that the data is not on storage...

[HRXF4] 08:17:52 INFO: Puller (folder “Projects” (n--------n),
  file “EDITS/.../1019_24m.mat”):
 sync /volumes/.../mat/.syncthing.1019_24m.mat.tmp: operation not supported

@calmh calmh added the bug label May 9, 2019

calmh added a commit to calmh/syncthing that referenced this issue May 9, 2019

@calmh calmh added this to the v1.1.4 milestone May 10, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.