mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 05:16:00 +03:00
[GH-ISSUE #6] s3fs have crashed with a segfault #3
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#3
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 @timurb on GitHub (Jan 13, 2014).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/6
I've seen the s3fs segfault today in the morning with the following message:
There are no accompanying messages in logs but I know there was some minor writing to S3 ~5min in advance to that.
The s3fs daemon was running since 9 Jan with more than 1.5Tb written since that time. Before that I've tried running s3fs of the same version on the same host with no errors (but with lesser overall throughput I think) for 2 weeks (before that I've used the older 1.61 version).
I'm running Debian Wheezy 7.3 with s3fs 1.74 (I think I've used r499 for compilation):
@timurb commented on GitHub (Jan 13, 2014):
Probably this also relates to overfilled cache disk as I've seen it to be full.
If that is the reason for that it would be nice if s3fs have produced out-of-space error instead of crashing.
@ggtakec commented on GitHub (Jan 15, 2014):
Thanks for a bug reporting.
I'll try to test about disk space without crashing. Please wait for a while.
@abertranb commented on GitHub (Oct 2, 2014):
Hello this is solved? Because I had an error whit version 1.78 getting this error
[646652.031561] s3fs[17520]: segfault at 0 ip 000000000042b4e3 sp 00007fc6d3ffe530 error 4 in s3fs[400000+52000]
I had cache enabled but the disk is not full (35% of use)
Would you recommend to disable cache?
I read some places to use an small number of multireq_max
https://code.google.com/p/s3fs/issues/detail?id=426
This is ok?
Thanks
@abertranb commented on GitHub (Oct 6, 2014):
Hello any news about it??
@ggtakec commented on GitHub (Oct 13, 2014):
Hi, abertranb
I'm sorry for late reply.
I want to know about your case of s3fs crashed, please let me know what option does you specify for s3fs, what do you do when s3fs crashed, etc.
Thanks in advance for your help.
@ggtakec commented on GitHub (Jan 17, 2016):
I'm sorry about this Issue had been left at a long period of time.
Latest codes(master branch) is fixed some bugs which included like this issue.
And I think that it is difficult to reproduce this problem now because there are many fixes from posting this issue.
If you is in still the same defect has failed on latest codes, please post new issue.
And If you post new problem, please post with detail logs(ex. syslog/messages) which are made by running s3fs with "dbglevel" or "curldbg".
Thanks in advance for your help.