starred/s3fs-fuse
1
0
Fork 0
mirror of https://github.com/s3fs-fuse/s3fs-fuse.git synced 2026-04-25 05:16:00 +03:00
Code Issues 305 Projects Releases 5 Packages Wiki Activity

[GH-ISSUE #18] s3fs crashes with segfault #13

New issue
Closed
opened 2026-03-04 01:41:10 +03:00 by kerem · 6 comments
kerem commented 2026-03-04 01:41:10 +03:00
Owner
Copy link

Originally created by @AGirin on GitHub (Feb 25, 2014).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/18

Version: 1.76

We have a script that parses some files and writes output to s3. s3fs-fuse constantly crash and we get Transport is not connected error.

The only log message in the messages log is:
kernel: s3fs[28576]: segfault at 0 ip 0000000000423679 sp 00007f3d87569870 error 4 in s3fs[400000+51000]

We tried running with s3fs -f and... it does not crash at all. So we cannot get the real output beside that message in the messages log file.

Not sure how to go about it. I think we can get dump file if this will help.

Thanks!

Andrew

Originally created by @AGirin on GitHub (Feb 25, 2014). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/18 Version: 1.76 We have a script that parses some files and writes output to s3. s3fs-fuse constantly crash and we get Transport is not connected error. The only log message in the messages log is: kernel: s3fs[28576]: segfault at 0 ip 0000000000423679 sp 00007f3d87569870 error 4 in s3fs[400000+51000] We tried running with s3fs -f and... it does not crash at all. So we cannot get the real output beside that message in the messages log file. Not sure how to go about it. I think we can get dump file if this will help. Thanks! Andrew
kerem closed this issue 2026-03-04 01:41:11 +03:00
kerem commented 2026-03-04 01:41:11 +03:00
Author
Owner
Copy link

@AGirin commented on GitHub (Feb 25, 2014):

Small update. It finally crashed under -f option. We got this:

ParallelGetObjectRetryCallback(987): Over retry count(3) limit(/directory/subdirectory/file_name).

I wonder what causes it? Can we change retry to higher number?

<!-- gh-comment-id:36060151 --> @AGirin commented on GitHub (Feb 25, 2014): Small update. It finally crashed under -f option. We got this: ParallelGetObjectRetryCallback(987): Over retry count(3) limit(/directory/subdirectory/file_name). I wonder what causes it? Can we change retry to higher number?
kerem commented 2026-03-04 01:41:12 +03:00
Author
Owner
Copy link

@AGirin commented on GitHub (Feb 25, 2014):

We'll try "retries" option to see if this solves the issue.

<!-- gh-comment-id:36064192 --> @AGirin commented on GitHub (Feb 25, 2014): We'll try "retries" option to see if this solves the issue.
kerem commented 2026-03-04 01:41:12 +03:00
Author
Owner
Copy link

@ggtakec commented on GitHub (Mar 17, 2014):

Hi, AGirin

Thank you for your reports, and sorry for replying too late.
I found a bug and fixed it, I pushed new branch as "bugfix#18" for this fix.

If you can, please use and check it.

Thanks in advance for your help.

<!-- gh-comment-id:37832867 --> @ggtakec commented on GitHub (Mar 17, 2014): Hi, AGirin Thank you for your reports, and sorry for replying too late. I found a bug and fixed it, I pushed new branch as "bugfix#18" for this fix. If you can, please use and check it. Thanks in advance for your help.
kerem commented 2026-03-04 01:41:12 +03:00
Author
Owner
Copy link

@ggtakec commented on GitHub (Mar 29, 2014):

I'm sorry for my mistake that I checked in new branch.
I re-check in it as soon as possible, pls wait for it.

<!-- gh-comment-id:39004805 --> @ggtakec commented on GitHub (Mar 29, 2014): I'm sorry for my mistake that I checked in new branch. I re-check in it as soon as possible, pls wait for it.
kerem commented 2026-03-04 01:41:12 +03:00
Author
Owner
Copy link

@ggtakec commented on GitHub (Mar 30, 2014):

Sorry for mis-check'd-in, and I re-chcked-in, merged master branch.
Please try to use master branch.

<!-- gh-comment-id:39019086 --> @ggtakec commented on GitHub (Mar 30, 2014): Sorry for mis-check'd-in, and I re-chcked-in, merged master branch. Please try to use master branch.
kerem commented 2026-03-04 01:41:12 +03:00
Author
Owner
Copy link

@jiazhiguang commented on GitHub (Feb 1, 2015):

I occurred this problem too, and I used the master version.

<!-- gh-comment-id:72350069 --> @jiazhiguang commented on GitHub (Feb 1, 2015): I occurred this problem too, and I used the master version.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
v1.97
v1.96
v1.95
v1.94
v1.93
v1.92
v1.91
v1.90
v1.89
v1.88
v1.87
v1.86
v1.85
v1.84
v1.83
v1.82
v1.81
v1.80
v1.79
v1.78
Pre-v1.78
v1.77
v1.76
v1.75
v1.74
Labels
Clear labels   
bug

   
bug

   
dataloss

   
duplicate

   
enhancement

   
feature request

   
help wanted

   
invalid

   
need info

   
performance

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
question

   
testing
No labels
bug
bug
dataloss
duplicate
enhancement
feature request
help wanted
invalid
need info
performance
pull-request
question
question
testing
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/s3fs-fuse#13
No description provided.