mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 13:26:00 +03:00
[GH-ISSUE #366] random crashes in s3fs #188
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#188
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 @romange on GitHub (Feb 23, 2016).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/366
Hi,
We get random crashes with this driver. When it happens we see lines like the one below in the syslog.
We use version 1.79.
Thanks
08:55:43 ip-10-0-4-29 kernel: [3686951.802241] traps: s3fs[2952] general protection ip:441e7a sp:7f69627fb580 error:0 in s3fs[400000+63000]@ggtakec commented on GitHub (Mar 6, 2016):
Hi, romange
Did you use latest codes in master branch?
(Some bugs was fixed by it.)
And could you run s3fs with dbglevel option for logging detail?
Regards,
@romange commented on GitHub (Mar 6, 2016):
We used 1.79 which is the latest release that available. eventually we decided to give up on s3fs and use a cron script that manually uploads data to s3.
@ggtakec commented on GitHub (Mar 6, 2016):
Hi, romange
If you can reproduce, please tell me your environment such as OS and object size etc.
If I can reproduce the defect, I will be able to know the reason of a bug and to fix it.
Even if I might not make it, it is happy that you will try to test new s3fs after we will release new version.
Regards,
@romange commented on GitHub (Mar 7, 2016):
It's Ubuntu 14.04, each file is around 50-100Kb. Usually it's one file per hour. in addition there are sporadic reads of dozens of files. It was glued together with sftp service - we built sftp-to-s3 port for our clients to upload data to s3. They uploaded directly to mounted s3fs directory.
Crashes were sporadic - could be weeks or days until the next one. We replaced it with cron script that just reads the data, uploads it to s3 and them removes it from the local disk of the instance.
@jdcallet commented on GitHub (Feb 19, 2018):
Hi @romange @ggtakec
Any additional information about this?
I'm stuck getting always this same error.
@romange commented on GitHub (Feb 19, 2018):
@jdcallet No, we moved on to other solutions.
@anovikov1984 commented on GitHub (Mar 12, 2018):
@romange which other solutions? :) i am facing same problem
@romange commented on GitHub (Mar 12, 2018):
Well, we used goofys for some time but for heavy-load use-cases we stopped
accessing files via fuse. We just copy them to local disk and then process
them.
On Mon, Mar 12, 2018 at 9:20 PM, anovikov1984 notifications@github.com
wrote:
--
Best regards,
Roman
@mnd999 commented on GitHub (Apr 25, 2018):
Getting this too
s3fs[23121] general protection ip:7fb03c656df9 sp:7fb00effbbe0 error:0 in libcrypto.so.1.0.0@gaul commented on GitHub (Feb 2, 2019):
Could you try running s3fs under Valgrind which may reveal the source of these symptoms?
@gaul commented on GitHub (Mar 17, 2019):
I suspect that
f53503438cresolves this issue. Could you test with 1.85 and report your results?@gaul commented on GitHub (Apr 9, 2019):
Closing due to inactivity. Please reopen if symptoms persist.