[GH-ISSUE #1955] parameter to increase timeout for CheckBucket #987

New issue

Open

opened 2026-03-04 01:50:27 +03:00 by kerem · 1 comment

kerem commented

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

Owner

Originally created by @prembhaskal on GitHub (Jun 8, 2022).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1955

Additional Information

The following information is very important in order to help us to help you. Omission of the following details may delay your support request or receive no attention at all.
Keep in mind that the commands we provide to retrieve information are oriented to GNU/Linux Distributions, so you could need to use others if you use s3fs on macOS or BSD

Version of s3fs being used (s3fs --version)

s3fs --version
Amazon Simple Storage Service File System V1.91 (commit:unknown) with OpenSSL
Copyright (C) 2010 Randy Rizun rrizun@gmail.com
License GPL2: GNU GPL version 2 https://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Version of fuse being used (pkg-config --modversion fuse, rpm -qi fuse, dpkg -s fuse)

rpm -qi fuse
Name : fuse
Version : 2.9.7
Release : 15.el8
Architecture: x86_64
Install Date: Fri May 13 20:33:15 2022
Group : Unspecified
Size : 208300
License : GPL+
Signature : RSA/SHA256, Fri Feb 25 18:38:22 2022, Key ID 199e2f91fd431d51
Source RPM : fuse-2.9.7-15.el8.src.rpm
Build Date : Thu Feb 24 17:57:08 2022
Build Host : x86-vm-55.build.eng.bos.redhat.com
Relocations : (not relocatable)
Packager : Red Hat, Inc. http://bugzilla.redhat.com/bugzilla
Vendor : Red Hat, Inc.
URL : http://fuse.sf.net
Summary : File System in Userspace (FUSE) v2 utilities
Description :
With FUSE it is possible to implement a fully functional filesystem in a
userspace program. This package contains the FUSE v2 userspace tools to
mount a FUSE filesystem.

Kernel information (uname -r)

4.18.0-193.19.1.2009211817.el7_8.emrs.altmvl.x86_64

GNU/Linux Distribution, if applicable (cat /etc/os-release)

NAME="Red Hat Enterprise Linux"
VERSION="8.6 (Ootpa)"
ID="rhel"
ID_LIKE="fedora"
VERSION_ID="8.6"
PLATFORM_ID="platform:el8"
PRETTY_NAME="Red Hat Enterprise Linux 8.6 (Ootpa)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:redhat:enterprise_linux:8::baseos"
HOME_URL="https://www.redhat.com/"
DOCUMENTATION_URL="https://access.redhat.com/documentation/red_hat_enterprise_linux/8/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"

REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 8"
REDHAT_BUGZILLA_PRODUCT_VERSION=8.6
REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux"
REDHAT_SUPPORT_PRODUCT_VERSION="8.6"

s3fs command line used, if applicable

/etc/fstab entry, if applicable

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

if you execute s3fs with dbglevel, curldbg option, you can get detail debug messages

Details about issue

The s3fs mount process is exiting frequent, in the logs we are seeing below errors.

2022-06-07T03:05:37.138Z [INF] curl.cpp:InitMimeType(424): Loaded mime information from /etc/mime.types
2022-06-07T03:05:37.142Z [INF] s3fs.cpp:s3fs_init(3393): init v1.91(commit:unknown) with OpenSSL
2022-06-07T03:05:57.225Z [ERR] curl.cpp:RequestPerform(2419): ### CURLE_COULDNT_RESOLVE_HOST==> /tmp/tmp.lqyvHIn4W3-pm-file-transfer <==
2022-06-07T03:07:57.512Z [INF] curl.cpp:InitMimeType(424): Loaded mime information from /etc/mime.types
2022-06-07T03:07:57.515Z [INF] s3fs.cpp:s3fs_init(3393): init v1.91(commit:unknown) with OpenSSL
2022-06-07T03:09:23.570Z [ERR] curl.cpp:RequestPerform(2541): ### giving up
2022-06-07T03:09:23.570Z [ERR] curl.cpp:CheckBucket(3515): Check bucket failed, S3 response:
2022-06-07T03:09:23.570Z [CRT] s3fs.cpp:s3fs_check_service(3594): unable to connect(host=http://s3.openshift-storage:80) - result of checking service.
2022-06-07T03:09:23.570Z [ERR] s3fs.cpp:s3fs_exit_fuseloop(3383): Exiting FUSE event loop due to errors

It seems it is unable to connect to underlying s3 storage and has timed out
I wanted to know which parameter will help to increase the timeout for this check.

Originally created by @prembhaskal on GitHub (Jun 8, 2022). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1955 ### Additional Information _The following information is very important in order to help us to help you. Omission of the following details may delay your support request or receive no attention at all._ _Keep in mind that the commands we provide to retrieve information are oriented to GNU/Linux Distributions, so you could need to use others if you use s3fs on macOS or BSD_ #### Version of s3fs being used (s3fs --version) s3fs --version Amazon Simple Storage Service File System V1.91 (commit:unknown) with OpenSSL Copyright (C) 2010 Randy Rizun <rrizun@gmail.com> License GPL2: GNU GPL version 2 <https://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. #### Version of fuse being used (pkg-config --modversion fuse, rpm -qi fuse, dpkg -s fuse) rpm -qi fuse Name : fuse Version : 2.9.7 Release : 15.el8 Architecture: x86_64 Install Date: Fri May 13 20:33:15 2022 Group : Unspecified Size : 208300 License : GPL+ Signature : RSA/SHA256, Fri Feb 25 18:38:22 2022, Key ID 199e2f91fd431d51 Source RPM : fuse-2.9.7-15.el8.src.rpm Build Date : Thu Feb 24 17:57:08 2022 Build Host : x86-vm-55.build.eng.bos.redhat.com Relocations : (not relocatable) Packager : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla> Vendor : Red Hat, Inc. URL : http://fuse.sf.net Summary : File System in Userspace (FUSE) v2 utilities Description : With FUSE it is possible to implement a fully functional filesystem in a userspace program. This package contains the FUSE v2 userspace tools to mount a FUSE filesystem. #### Kernel information (uname -r) 4.18.0-193.19.1.2009211817.el7_8.emrs.altmvl.x86_64 #### GNU/Linux Distribution, if applicable (cat /etc/os-release) NAME="Red Hat Enterprise Linux" VERSION="8.6 (Ootpa)" ID="rhel" ID_LIKE="fedora" VERSION_ID="8.6" PLATFORM_ID="platform:el8" PRETTY_NAME="Red Hat Enterprise Linux 8.6 (Ootpa)" ANSI_COLOR="0;31" CPE_NAME="cpe:/o:redhat:enterprise_linux:8::baseos" HOME_URL="https://www.redhat.com/" DOCUMENTATION_URL="https://access.redhat.com/documentation/red_hat_enterprise_linux/8/" BUG_REPORT_URL="https://bugzilla.redhat.com/" REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 8" REDHAT_BUGZILLA_PRODUCT_VERSION=8.6 REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux" REDHAT_SUPPORT_PRODUCT_VERSION="8.6" #### s3fs command line used, if applicable ``` ``` #### /etc/fstab entry, if applicable ``` ``` #### s3fs syslog messages (grep s3fs /var/log/syslog, journalctl | grep s3fs, or s3fs outputs) _if you execute s3fs with dbglevel, curldbg option, you can get detail debug messages_ ``` ``` ### Details about issue The s3fs mount process is exiting frequent, in the logs we are seeing below errors. ``` 2022-06-07T03:05:37.138Z [INF] curl.cpp:InitMimeType(424): Loaded mime information from /etc/mime.types 2022-06-07T03:05:37.142Z [INF] s3fs.cpp:s3fs_init(3393): init v1.91(commit:unknown) with OpenSSL 2022-06-07T03:05:57.225Z [ERR] curl.cpp:RequestPerform(2419): ### CURLE_COULDNT_RESOLVE_HOST==> /tmp/tmp.lqyvHIn4W3-pm-file-transfer <== 2022-06-07T03:07:57.512Z [INF] curl.cpp:InitMimeType(424): Loaded mime information from /etc/mime.types 2022-06-07T03:07:57.515Z [INF] s3fs.cpp:s3fs_init(3393): init v1.91(commit:unknown) with OpenSSL 2022-06-07T03:09:23.570Z [ERR] curl.cpp:RequestPerform(2541): ### giving up 2022-06-07T03:09:23.570Z [ERR] curl.cpp:CheckBucket(3515): Check bucket failed, S3 response: 2022-06-07T03:09:23.570Z [CRT] s3fs.cpp:s3fs_check_service(3594): unable to connect(host=http://s3.openshift-storage:80) - result of checking service. 2022-06-07T03:09:23.570Z [ERR] s3fs.cpp:s3fs_exit_fuseloop(3383): Exiting FUSE event loop due to errors ``` It seems it is unable to connect to underlying s3 storage and has timed out I wanted to know which **parameter will help to increase the timeout** for this check.

kerem commented

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

Author

Owner

@prembhaskal commented on GitHub (Jun 9, 2022):

Also i wanted to know if timeout works as described below and few questions in them.
suppose

at time 't' seconds, the s3fs mount process started
at time 't+1000' seconds, the S3 endpoint becomes unresponsive, meaning if you do curl with very less connect timeout, you will get connection refused error.
at time 't+1030' seconds, the s3fs fuse gives the checkbucket error, if someone does a read/write operation on the mounted file system. the filesystem operation fails or remains hung?? for how long?
at time 't+1060' second, the S3 endpoint becomes responsive back,
at time 't+1061', will filesystem operation resume now?

Suppose the S3 endpoint never recovers after 1st breakdown, at what of time will the filesystem operation fail. after 5 mins (the connect timeout) or 2 mins (the read timeout)?

@prembhaskal commented on GitHub (Jun 9, 2022): Also i wanted to know if timeout works as described below and few questions in them. suppose - at time 't' seconds, the s3fs mount process started - at time 't+1000' seconds, the S3 endpoint becomes unresponsive, meaning if you do curl with very less connect timeout, you will get connection refused error. - at time 't+1030' seconds, the s3fs fuse gives the checkbucket error, if someone does a read/write operation on the mounted file system. the filesystem operation fails or remains hung?? for how long? - at time 't+1060' second, the S3 endpoint becomes responsive back, - at time 't+1061', will filesystem operation resume now? Suppose the S3 endpoint never recovers after 1st breakdown, at what of time will the filesystem operation fail. after 5 mins (the connect timeout) or 2 mins (the read timeout)?