[GH-ISSUE #735] Get the issue with mounting from my amazon instance server with S3 buckets #420

New issue

Closed

opened 2026-03-04 01:45:24 +03:00 by kerem · 2 comments

kerem commented

2026-03-04 01:45:24 +03:00

Owner

Originally created by @isea44 on GitHub (Mar 23, 2018).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/735

Additional Information

I have the server running on amazon which using s3fs mounting with s3 buckets.
since the beginning of this year after Amazon did the maintenance reboot. I have been facing the issue with s3 mounting.

The issue is all users cannot R/W the file in the folder which mounted with s3 bucket over s3fs
got the message after trying to R/W the file in folder: operation not permitted
Re-mounting does not help.
To fix this we need to restart the server and do 'modprobe fuse' and mount s3 buckets

but after running for a few days or weeks, we always got the same issue again...
the folders still mounted but cannot R/W inside those folders

Version of s3fs being used (s3fs --version)

Amazon Simple Storage Service File System 1.71

Version of fuse being used (pkg-config --modversion fuse)

[root@vmeo-delivery /]# modinfo fuse
filename: /lib/modules/2.6.18-274.17.1.el5xen/kernel/fs/fuse/fuse.ko
vermagic: 2.6.18-274.17.1.el5xen SMP mod_unload gcc-4.1

System information (uname -r)

2.6.18-274.17.1.el5xen

Distro (cat /etc/issue)

CentOS release 5.8 (Final)

/etc/fstab entry (if applicable):

s3fs#vmeo /mnt/mounts3 fuse use_cache=/mnt/tmp,use_rrs=1,allow_other,nonempty 0 0
s3fs#vmeohttp /mnt/s3vmeohttp fuse use_cache=/tmp,use_rrs=1,nonempty,allow_other 0 0

s3fs syslog messages (grep s3fs /var/log/syslog, or s3fs outputs)

Mar 22 16:02:15 vmeo-delivery s3fs: ### CURLE_COULDNT_CONNECT
Mar 22 16:02:19 vmeo-delivery s3fs: ###retrying...
Mar 22 17:02:12 vmeo-delivery s3fs: ### CURLE_COULDNT_CONNECT
Mar 22 17:02:16 vmeo-delivery s3fs: ###retrying...
Mar 22 18:02:05 vmeo-delivery s3fs: ### CURLE_COULDNT_CONNECT

Originally created by @isea44 on GitHub (Mar 23, 2018). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/735 ### Additional Information I have the server running on amazon which using s3fs mounting with s3 buckets. since the beginning of this year after Amazon did the maintenance reboot. I have been facing the issue with s3 mounting. The issue is all users cannot R/W the file in the folder which mounted with s3 bucket over s3fs got the message after trying to R/W the file in folder: operation not permitted Re-mounting does not help. To fix this we need to restart the server and do 'modprobe fuse' and mount s3 buckets but after running for a few days or weeks, we always got the same issue again... the folders still mounted but cannot R/W inside those folders #### Version of s3fs being used (s3fs --version) Amazon Simple Storage Service File System 1.71 #### Version of fuse being used (pkg-config --modversion fuse) [root@vmeo-delivery /]# modinfo fuse filename: /lib/modules/2.6.18-274.17.1.el5xen/kernel/fs/fuse/fuse.ko vermagic: 2.6.18-274.17.1.el5xen SMP mod_unload gcc-4.1 #### System information (uname -r) 2.6.18-274.17.1.el5xen #### Distro (cat /etc/issue) CentOS release 5.8 (Final) #### /etc/fstab entry (if applicable): s3fs#vmeo /mnt/mounts3 fuse use_cache=/mnt/tmp,use_rrs=1,allow_other,nonempty 0 0 s3fs#vmeohttp /mnt/s3vmeohttp fuse use_cache=/tmp,use_rrs=1,nonempty,allow_other 0 0 #### s3fs syslog messages (grep s3fs /var/log/syslog, or s3fs outputs) Mar 22 16:02:15 vmeo-delivery s3fs: ### CURLE_COULDNT_CONNECT Mar 22 16:02:19 vmeo-delivery s3fs: ###retrying... Mar 22 17:02:12 vmeo-delivery s3fs: ### CURLE_COULDNT_CONNECT Mar 22 17:02:16 vmeo-delivery s3fs: ###retrying... Mar 22 18:02:05 vmeo-delivery s3fs: ### CURLE_COULDNT_CONNECT

kerem closed this issue

2026-03-04 01:45:24 +03:00

kerem commented

2026-03-04 01:45:25 +03:00

Author

Owner

@gaul commented on GitHub (Jul 11, 2019):

Can you make sure that s3fs is still running? These symptoms are consistent with some kind of crash or permanent network error. Also please test with the latest version 1.85 since 1.71 is 7 years old!

@gaul commented on GitHub (Jul 11, 2019): Can you make sure that s3fs is still running? These symptoms are consistent with some kind of crash or permanent network error. Also please test with the latest version 1.85 since 1.71 is 7 years old!

kerem commented

2026-03-04 01:45:25 +03:00

Author

Owner

@gaul commented on GitHub (Feb 3, 2020):

Closing due to inactivity. Please reopen if symptoms persist.

@gaul commented on GitHub (Feb 3, 2020): Closing due to inactivity. Please reopen if symptoms persist.

kerem referenced this issue

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

[PR #420] [MERGED] Skip early credential checks when iam_role=auto #1500