[GH-ISSUE #429] Mount hangs following upgrade to 1.80 #229

New issue

Closed

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

kerem commented

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

Owner

Originally created by @makered on GitHub (Jun 6, 2016).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/429

I recently upgraded from v1.79 to v1.80. At first everything seemed to go well and I was able to access S3 via the mount.

After some time, however, any attempt to access the S3 mount or running disk-related commands (e.g. df -h) would cause the request to hang until the system was rebooted. The log does not seem to reveal anything suspicious.

The mount definition in /etc/fstab is:

s3fs#mybucketname /s3 fuse use_cache=/cache,url=http://s3.amazonaws.com,enable_noobj_cache,enable_content_md5,stat_cache_expire=30,nonempty,allow_other,_netdev,default_permissions,iam_role=MYROLE,parallel_count=10,uid=1004,gid=1001,umask=0002,nodev,noauto 0 0

Is there anything more specific I can do to troubleshoot?

Thank you

Originally created by @makered on GitHub (Jun 6, 2016). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/429 I recently upgraded from v1.79 to v1.80. At first everything seemed to go well and I was able to access S3 via the mount. After some time, however, any attempt to access the S3 mount or running disk-related commands (e.g. `df -h`) would cause the request to hang until the system was rebooted. The log does not seem to reveal anything suspicious. The mount definition in /etc/fstab is: `s3fs#mybucketname /s3 fuse use_cache=/cache,url=http://s3.amazonaws.com,enable_noobj_cache,enable_content_md5,stat_cache_expire=30,nonempty,allow_other,_netdev,default_permissions,iam_role=MYROLE,parallel_count=10,uid=1004,gid=1001,umask=0002,nodev,noauto 0 0` Is there anything more specific I can do to troubleshoot? Thank you

kerem closed this issue

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

kerem commented

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

Author

Owner

@ggtakec commented on GitHub (Jun 12, 2016):

Hi, @makered
If you can reproduce, please try to run with the dbglevel options(and curldbg).
I think that it is possible to obtain a detailed debugging information.
However, because the log file will be very large size by these options, please use with caution.

Thanks in advance for your help.

@ggtakec commented on GitHub (Jun 12, 2016): Hi, @makered If you can reproduce, please try to run with the dbglevel options(and curldbg). I think that it is possible to obtain a detailed debugging information. However, because the log file will be very large size by these options, please use with caution. Thanks in advance for your help.

kerem commented

2026-03-04 01:43:28 +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:47 +03:00

[PR #229] [MERGED] Convert rename_before_close to a shell script #1408