-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Repository is showing as unknown and panic: deadlock detected #393
Labels
frozen-due-to-age
Issues closed and untouched for a long time, together with being locked for discussion
Comments
Same problem here (even the name "~/Projects" is the same) on Linux. Link to output. In my case the folder contains ~120k entries (98k files and some folders). |
calmh
added a commit
that referenced
this issue
Jun 26, 2014
Yeah, sorry about that, the timeout was bad. Increased to 20 minutes, which should be enough, and I'm interested in the backtrace if it isn't. If I'm still wrong, it can be disabled with something like |
calmh
added a commit
that referenced
this issue
Jun 29, 2014
* v0.8: Increase deadlock timeout, make configurable (fixes #389, fixes #393) Remove spurious debug output in .stignore handling Connection notices are informational No need to hold a write lock in Override Don't whine about unexpected EOFs Ensure correct version string format Conflicts: model/model.go
calmh
added a commit
that referenced
this issue
Jun 30, 2014
* master: Improve XDR performance XDR incorrect encoding of uint16; tests and benchmarks Fix linux/freebsd/windows compilation Refactor node ID handling, use check digits (fixes #269) discosrv: Tunable limiter settings Increase deadlock timeout, make configurable (fixes #389, fixes #393) Logger should use stdout instead of stderr Remove spurious debug output in .stignore handling Connection notices are informational No need to hold a write lock in Override Don't whine about unexpected EOFs Ensure correct version string format Include MaxVersion in Cluster Config message Test script for REST interface Don't deadlock on connect close while sending Index (fixes #386) Detect deadlock in model and panic Asset update for previous commit Conflicts: model/model.go
st-review
added
the
frozen-due-to-age
Issues closed and untouched for a long time, together with being locked for discussion
label
Jun 17, 2017
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
frozen-due-to-age
Issues closed and untouched for a long time, together with being locked for discussion
After running
syncthing
on Mac OS OX, and setting it to point at a folder with a lot of files,syncthing
now seems to be stuck with all repositories showing as unknown.Attached is a screen shot of the GUI whilst it's starting up, and pasted below is the log showing the deadlock detected after a few minutes:
The text was updated successfully, but these errors were encountered: