[GH-ISSUE #463] OSXFUSE: force ejecting (no response from user space 5) #253

New issue

Closed

opened 2026-03-04 01:43:42 +03:00 by kerem · 2 comments

kerem commented

2026-03-04 01:43:42 +03:00

Owner

Originally created by @dcow on GitHub (Aug 30, 2016).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/463

I'm using s3fs to try and list a rather large directory (many entries). The bucket mounts successfully but, when trying to list, ls hangs for a bit then reports that the volume is no longer mounted. That's the only error message I receive.

Originally created by @dcow on GitHub (Aug 30, 2016). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/463 I'm using `s3fs` to try and list a rather large directory (many entries). The bucket mounts successfully but, when trying to list, `ls` hangs for a bit then reports that the volume is no longer mounted. That's the only error message I receive.

kerem closed this issue

2026-03-04 01:43:42 +03:00

kerem commented

2026-03-04 01:43:43 +03:00

Author

Owner

@ggtakec commented on GitHub (Sep 19, 2016):

@dcow
How many files in directory do you have?
Does s3fs keep to try to list files after you seems like s3fs hangup?

s3fs sends many requests to S3 for reading each file's attribute, probably it includes this problem.
If you can, please try to run s3fs with dbglevel option.
It reports many information about this issue.

Thanks in advance for your help.

@ggtakec commented on GitHub (Sep 19, 2016): @dcow How many files in directory do you have? Does s3fs keep to try to list files after you seems like s3fs hangup? s3fs sends many requests to S3 for reading each file's attribute, probably it includes this problem. If you can, please try to run s3fs with dbglevel option. It reports many information about this issue. Thanks in advance for your help.

kerem commented

2026-03-04 01:43:43 +03:00

Author

Owner

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

We kept this issue open for a long time.
We launch new version 1.86, which fixed some problem(bugs).
Please use the latest version.
I will close this, but if the problem persists, please reopen or post a new issue.

@ggtakec commented on GitHub (Mar 30, 2019): We kept this issue open for a long time. We launch new version 1.86, which fixed some problem(bugs). Please use the latest version. I will close this, but if the problem persists, please reopen or post a new issue.

kerem referenced this issue

2026-03-04 01:53:54 +03:00

[PR #253] [MERGED] Added chacking cache dir perms at starting. #1426