mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 05:16:00 +03:00
[GH-ISSUE #117] S3fs occasionally fails to open files #72
Labels
No labels
bug
bug
dataloss
duplicate
enhancement
feature request
help wanted
invalid
need info
performance
pull-request
question
question
testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/s3fs-fuse#72
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @boazrf on GitHub (Feb 4, 2015).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/117
While running process that does intensive read/write s3fs occasionally fails to open files.
Problem may be related to #94
Environment:
s3fs version: 1.78
OS: Amazon linux
Linux version 3.10.40-50.136.amzn1.x86_64 (mockbuild@gobi-build-60001) (gcc version 4.8.2 20131212 (Red Hat 4.8.2-7) (GCC) ) #1 SMP Tue May 13 21:35:08 UTC 2014
Scenario
Issue 1
Even when all works well I keep seeing the message Hostname was NOT found in DNS cache repeats constantly throughout the log. This might be curl issue but I'm not sure how to resolve it. I've encountered suggestion to downgrade curl to 7.31 (http://stackoverflow.com/questions/27093467/curl-hostname-was-not-found-in-dns-cache-error) but I haven't figured out yet how to do it (yum downgrade doesn't work).
Issue 2
After running for a while I'm getting Could not resolve host: and CURLE_COULDNT_RESOLVE_HOST messages followed by a failure to open the file after several retries (I increased retries to 100 but it didn't help).
@ggtakec commented on GitHub (Mar 8, 2015):
I'm sorry for replying late.
I tried to find the reason searched about "CURLE_COULDNT_RESOLVE_HOST" error, but I did not get clear answer.
I have not been get the reason and not been able to reproduce yet.
s3fs uses DNS cache and session id cache by libcurl CURLSHOPT_SHARE as default.
So if you can, please try to run s3fs with nodnscache and nosscache option.
These option means that s3fs does not use DNS/Session cache.
And if you can, I want to know the result about that you run s3fs with HTTP.(not HTTPS)
I'm sorry for that I do not know the cause of this Issue yet.
(We should know why libcurl could not know resolv host.)
Thanks in advance for your assistance.
@boazrf commented on GitHub (Mar 8, 2015):
Takeshi, thanks for reviewing the problem.
I was able to overcome the problem by downgrading libcurl to version 7.31. It seems that there is a known bug in new version of curl that causes a failure with it's DNS cache in some cases. The bug doesn't exists in version 7.31 (http://stackoverflow.com/questions/27093467/curl-hostname-was-not-found-in-dns-cache-error).
Because yum downgrade didn't work I did the following:
Following that the message Hostname was NOT found in DNS cache disappeared and so did CURLE_COULDNT_RESOLVE_HOST, and most important: files opening stopped failing.
So - I consider this issue closed. I belive this workaround will also resolved issue #94. It might be a good idea to update install doc and add check for valid libcurl version.
@ggtakec commented on GitHub (Mar 8, 2015):
@boazrf Thanks a lot.
@ggtakec commented on GitHub (Jan 17, 2016):
I'm closing this issue, if you have a problem yet, please post new issue or reopen this issue.
Thanks in advance for your help.