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

syncthing v0.14.37-rc.2: folder error: failed to check available storage space #4321

Closed
ckeen opened this issue Aug 22, 2017 · 2 comments
Closed
Labels
frozen-due-to-age Issues closed and untouched for a long time, together with being locked for discussion

Comments

@ckeen
Copy link

ckeen commented Aug 22, 2017

  • what happened,

Upon startup syncthing pauses shares with the above error message which can also be found in the logs (one is attached). Resuming is not possible as they will get stopped again with the same error message. Storage space is plenty on this device and on the other nodes which are running the same version albeit on other Oses.

  • what you expected to happen instead, and

Normal starup.

  • any steps to reproduce the problem.

I am not sure whether this is easily reproducable or whether it is the specific version or OS combination. I am willing to debug this further with directions.

The log file has been edited so that keys and share names have been renamed/removed. Otherwise it is provided as is.

Version Information

Syncthing Version: v0.14.37-rc.2
OS Version: OpenBSD 6.1-current
Browser Version: N/A

Logfile

[NPNSQ] 18:51:53 INFO: syncthing v0.14.37-rc.2 "Dysprosium Dragonfly" (go1.9rc2 openbsd-amd64) teamcity@build.syncthing.net 2017-08-22 06:48:25 UTC
[NPNSQ] 18:51:53 INFO: My ID: xxxxxxxx
[NPNSQ] 18:51:54 INFO: Single thread SHA256 performance is 47 MB/s using minio/sha256-simd (41 MB/s using crypto/sha256).
[NPNSQ] 18:51:55 INFO: Hashing performance with weak hash is 40.15 MB/s
[NPNSQ] 18:51:55 INFO: Hashing performance without weak hash is 45.48 MB/s
[NPNSQ] 18:51:55 INFO: Weak hash enabled, as it has an acceptable performance impact.
[NPNSQ] 18:51:55 VERBOSE: Starting up (/home/ckeen/.config/syncthing)
[NPNSQ] 18:51:56 INFO: Starting deadlock detector with 20m0s timeout
[NPNSQ] 18:51:56 INFO: Ready to synchronize "foo" (readwrite)
[NPNSQ] 18:51:56 INFO: Ready to synchronize default (readwrite)
[NPNSQ] 18:51:56 INFO: Ready to synchronize bar (readwrite)
[NPNSQ] 18:51:56 WARNING: Stopping folder "foo" - failed to check available storage space
[NPNSQ] 18:51:56 INFO: Stopping folder "foo" due to error: failed to check available storage space
[NPNSQ] 18:51:56 INFO: Failed initial scan (rw) of "foo"
[NPNSQ] 18:51:56 VERBOSE: Folder "foo" is now error
[NPNSQ] 18:51:56 WARNING: Stopping folder default - failed to check available storage space
[NPNSQ] 18:51:56 INFO: Stopping folder default due to error: failed to check available storage space
[NPNSQ] 18:51:56 INFO: Failed initial scan (rw) of default
[NPNSQ] 18:51:56 VERBOSE: Folder "default" is now error
[NPNSQ] 18:51:56 WARNING: Stopping folder bar - failed to check available storage space
[NPNSQ] 18:51:56 INFO: Stopping folder bar due to error: failed to check available storage space
[NPNSQ] 18:51:56 INFO: Failed initial scan (rw) of bar
[NPNSQ] 18:51:56 VERBOSE: Folder "bar" is now error
[NPNSQ] 18:51:56 INFO: Send rate is unlimited, receive rate is unlimited
[NPNSQ] 18:51:56 INFO: Rate limits do not apply to LAN connections
[NPNSQ] 18:51:56 INFO: Using discovery server https://discovery-v4-2.syncthing.net/v2/?id=xxx
[NPNSQ] 18:51:56 INFO: Using discovery server https://discovery-v4-3.syncthing.net/v2/?id=xxx
[NPNSQ] 18:51:56 INFO: Using discovery server https://discovery-v4-4.syncthing.net/v2/?id=xxx
[NPNSQ] 18:51:56 INFO: Using discovery server https://discovery-v6-2.syncthing.net/v2/?id=xxx
[NPNSQ] 18:51:56 INFO: Using discovery server https://discovery-v6-3.syncthing.net/v2/?id=xxx
[NPNSQ] 18:51:56 INFO: Using discovery server https://discovery-v6-4.syncthing.net/v2/?id=xxx
[NPNSQ] 18:51:56 INFO: TCP listener (0.0.0.0:22000) starting
[NPNSQ] 18:51:56 VERBOSE: Discovered device XXX at [tcp://192.168.178.20:22000]
[NPNSQ] 18:51:56 INFO: GUI and API listening on 127.0.0.1:8384
[NPNSQ] 18:51:56 INFO: Access the GUI via the following URL: http://127.0.0.1:8384/
[NPNSQ] 18:51:56 INFO: Device XXX is "baz" at [dynamic]
[NPNSQ] 18:51:56 INFO: Device XXX is "quux" at [dynamic]
[NPNSQ] 18:51:56 INFO: Device XXX is "localhost" at [dynamic]
[NPNSQ] 18:51:56 INFO: Device XXX is "bar" at [dynamic]
[NPNSQ] 18:51:56 INFO: Device XXX is "me" at [dynamic]
[NPNSQ] 18:51:56 INFO: Anonymous usage reporting is always enabled for candidate releases.
[NPNSQ] 18:51:56 INFO: Automatic upgrade is always enabled for candidate releases.
[NPNSQ] 18:51:56 VERBOSE: Startup complete
[NPNSQ] 18:51:56 INFO: Starting usage reporting
[NPNSQ] 18:51:57 INFO: Skipping pull of "foo" due to folder error: failed to check available storage space
[NPNSQ] 18:51:57 INFO: Skipping pull of bar due to folder error: failed to check available storage space
[NPNSQ] 18:51:57 INFO: Skipping pull of default due to folder error: failed to check available storage space
[NPNSQ] 18:52:07 INFO: Skipping pull of "foo" due to folder error: failed to check available storage space
[NPNSQ] 18:52:07 INFO: Joined relay relay://51.15.52.244:22067
[NPNSQ] 18:52:07 INFO: Skipping pull of default due to folder error: failed to check available storage space
[NPNSQ] 18:52:07 INFO: Skipping pull of bar due to folder error: failed to check available storage space
[NPNSQ] 18:52:07 INFO: Detected 0 NAT devices
[NPNSQ] 18:52:10 INFO: set tcp 192.168.178.24:46700->192.168.178.20:22000: protocol not available
[NPNSQ] 18:52:11 INFO: Established secure connection to XXX at 192.168.178.24:46700-192.168.178.20:22000 (tcp-client) (TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305)
[NPNSQ] 18:52:11 INFO: Device XXX client is "syncthing v0.14.37-rc.2" named "quux"
[NPNSQ] 18:52:11 INFO: Skipping pull of bar due to folder error: failed to check available storage space
[NPNSQ] 18:52:11 INFO: Skipping pull of default due to folder error: failed to check available storage space
[NPNSQ] 18:52:11 INFO: Skipping pull of "foo" due to folder error: failed to check available storage space
[NPNSQ] 18:52:13 VERBOSE: Summary for folder "default" is map[globalFiles:3604 needDirectories:1136 inSyncFiles:0 needFiles:3604 sequence:10598 needSymlinks:1 localDirectories:0 localSymlinks:0 globalBytes:2002212482 localBytes:0 state:error globalDirectories:1136 inSyncBytes:0 version:10598 localFiles:0 needBytes:2002212482 localDeleted:0 error:failed to check available storage space globalSymlinks:1 needDeletes:0 globalDeleted:1552]
[NPNSQ] 18:52:13 VERBOSE: Completion for folder "default" on device XXX is 100%
[NPNSQ] 18:52:13 VERBOSE: Summary for folder "bar" is map[localSymlinks:0 localBytes:0 globalFiles:56 globalSymlinks:0 globalBytes:357916046 needBytes:357916046 state:error globalDirectories:4 needDirectories:4 sequence:104 needFiles:56 error:failed to check available storage space localDeleted:0 globalDeleted:16 needDeletes:0 localFiles:0 localDirectories:0 needSymlinks:0 inSyncBytes:0 inSyncFiles:0 version:104]
[NPNSQ] 18:52:13 VERBOSE: Completion for folder "bar" on device XXX is 100%
[NPNSQ] 18:52:13 VERBOSE: Summary for folder "m59k9-mvdrj" is map[globalBytes:14863233 globalDirectories:0 localDeleted:0 inSyncBytes:0 localBytes:0 localFiles:0 globalSymlinks:0 localSymlinks:0 version:47 needDeletes:0 globalDeleted:11 needSymlinks:0 globalFiles:1 needBytes:14863233 inSyncFiles:0 error:failed to check available storage space localDirectories:0 needDirectories:0 sequence:47 needFiles:1 state:error]
[NPNSQ] 18:52:13 VERBOSE: Completion for folder "m59k9-mvdrj" on device XXX is 100%
[NPNSQ] 18:52:16 VERBOSE: Listen address dynamic+https://relays.syncthing.net/endpoint resolution has changed: lan addresses: [relay://51.15.52.244:22067/?id=XXX&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=0&statusAddr=:22070&providedBy=] wan addresses: [relay://51.15.52.244:22067/?id=XXX&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=0&statusAddr=:22070&providedBy=]
[NPNSQ] 18:52:21 INFO: Skipping pull of "foo" due to folder error: failed to check available storage space
[NPNSQ] 18:52:21 INFO: Skipping pull of default due to folder error: failed to check available storage space
[NPNSQ] 18:52:21 INFO: Skipping pull of bar due to folder error: failed to check available storage space
[NPNSQ] 18:52:31 INFO: Skipping pull of "foo" due to folder error: failed to check available storage space
[NPNSQ] 18:52:31 INFO: Skipping pull of bar due to folder error: failed to check available storage space
[NPNSQ] 18:52:31 INFO: Skipping pull of default due to folder error: failed to check available storage space
[NPNSQ] 18:52:41 INFO: Skipping pull of default due to folder error: failed to check available storage space
[NPNSQ] 18:52:41 INFO: Skipping pull of "foo" due to folder error: failed to check available storage space
[NPNSQ] 18:52:41 INFO: Skipping pull of bar due to folder error: failed to check available storage space

@AudriusButkevicius
Copy link
Member

Thanks, I'll check this and come back with other questions.

@imsodin
Copy link
Member

imsodin commented Aug 22, 2017

The problem is that openbsd is not supported by calmh/du and now this makes checkFreeSpace fail, when before it did not:
https://github.com/syncthing/syncthing/blob/master/lib/model/model.go#L2305

Edit:
And the error message there should include the error from fs.Usage:
https://github.com/syncthing/syncthing/blob/master/lib/model/model.go#L2306

AudriusButkevicius added a commit to AudriusButkevicius/syncthing that referenced this issue Aug 22, 2017
viable-hartman pushed a commit to viable-hartman/syncthing that referenced this issue Aug 25, 2017
@st-review st-review added the frozen-due-to-age Issues closed and untouched for a long time, together with being locked for discussion label Sep 10, 2018
@syncthing syncthing locked and limited conversation to collaborators Sep 10, 2018
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
Projects
None yet
Development

No branches or pull requests

4 participants