starred/s3fs-fuse

Fork 0

mirror of https://github.com/s3fs-fuse/s3fs-fuse.git synced 2026-04-25 13:26:00 +03:00

[GH-ISSUE #2186] v1.92 mount issue , folder path appending with additional / #1113

New issue

Closed

opened 2026-03-04 01:51:29 +03:00 by kerem · 3 comments

kerem commented

2026-03-04 01:51:29 +03:00

Owner

Originally created by @sathishstorm on GitHub (Jun 7, 2023).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/2186

Additional Information

Version of s3fs being used (`s3fs --version`)

1.92

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

Version : 2.9.2

Kernel information (`uname -r`)

5.4.241-150.347.amzn2.x86_64

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

NAME="CentOS Linux"
VERSION="7 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="7"
PRETTY_NAME="CentOS Linux 7 (Core)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:7"
HOME_URL="https://www.centos.org/"
BUG_REPORT_URL="https://bugs.centos.org/"

CENTOS_MANTISBT_PROJECT="CentOS-7"
CENTOS_MANTISBT_PROJECT_VERSION="7"
REDHAT_SUPPORT_PRODUCT="centos"
REDHAT_SUPPORT_PRODUCT_VERSION="7"

How to run s3fs, if applicable

[] command line
[] /etc/fstab

s3fs bucketname:/folderpath /mountpath -o allow_other,use_cache=/tmp,connect_timeout=10,nonempty,umask=0022

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

2023-06-07T15:35:54.258Z [ERR] curl.cpp:CheckBucket(3741): Check bucket failed, S3 response:
NoSuchKeyThe specified key does not exist.folderpath/******************************
2023-06-07T15:35:54.258Z [CRT] s3fs.cpp:s3fs_check_service(4443): Failed to check bucket and directory for mount point : Bucket or directory(/folderpath) not found(host=https://s3.amazonaws.com) - You may need to specify the compat_dir option.
2023-06-07T15:35:54.258Z [ERR] s3fs.cpp:s3fs_exit_fuseloop(4200): Exiting FUSE event loop due to errors

Details about issue

additional / is added to the folder path so mount failing with error key not found.
after upgrading to v1.92 this error comes. when i downgraded to v1.91 it is working fine.

Originally created by @sathishstorm on GitHub (Jun 7, 2023). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/2186  ### Additional Information #### Version of s3fs being used (`s3fs --version`)  1.92 #### Version of fuse being used (`pkg-config --modversion fuse`, `rpm -qi fuse` or `dpkg -s fuse`)  Version : 2.9.2 #### Kernel information (`uname -r`)  5.4.241-150.347.amzn2.x86_64 #### GNU/Linux Distribution, if applicable (`cat /etc/os-release`)  NAME="CentOS Linux" VERSION="7 (Core)" ID="centos" ID_LIKE="rhel fedora" VERSION_ID="7" PRETTY_NAME="CentOS Linux 7 (Core)" ANSI_COLOR="0;31" CPE_NAME="cpe:/o:centos:centos:7" HOME_URL="https://www.centos.org/" BUG_REPORT_URL="https://bugs.centos.org/" CENTOS_MANTISBT_PROJECT="CentOS-7" CENTOS_MANTISBT_PROJECT_VERSION="7" REDHAT_SUPPORT_PRODUCT="centos" REDHAT_SUPPORT_PRODUCT_VERSION="7" #### How to run s3fs, if applicable  [] command line [] /etc/fstab  s3fs bucketname:/folderpath /mountpath -o allow_other,use_cache=/tmp,connect_timeout=10,nonempty,umask=0022 #### s3fs syslog messages (`grep s3fs /var/log/syslog`, `journalctl | grep s3fs`, or `s3fs outputs`)  ``` ``` 2023-06-07T15:35:54.258Z [ERR] curl.cpp:CheckBucket(3741): Check bucket failed, S3 response: <?xml version="1.0" encoding="UTF-8"?> <Error><Code>NoSuchKey</Code><Message>The specified key does not exist.</Message><Key>folderpath/</Key><RequestId>********</RequestId><HostId>**************************************</HostId></Error> 2023-06-07T15:35:54.258Z [CRT] s3fs.cpp:s3fs_check_service(4443): Failed to check bucket and directory for mount point : Bucket or directory(/folderpath) not found(host=https://s3.amazonaws.com) - You may need to specify the compat_dir option. 2023-06-07T15:35:54.258Z [ERR] s3fs.cpp:s3fs_exit_fuseloop(4200): Exiting FUSE event loop due to errors ### Details about issue  additional / is added to the folder path so mount failing with error key not found. after upgrading to v1.92 this error comes. when i downgraded to v1.91 it is working fine.

kerem closed this issue

2026-03-04 01:51:30 +03:00

kerem commented

2026-03-04 01:51:30 +03:00

Author

Owner

@sathishstorm commented on GitHub (Jun 9, 2023):

after checking the difference between the versions 1.91 and 1.92 looks like we need to use compat_dir parameter to resolve this issue which is added newly in 1.92

s3fs bucketname:/folderpath /mountpath -o allow_other,use_cache=/tmp,connect_timeout=10,nonempty,umask=0022,compat_dir

@sathishstorm commented on GitHub (Jun 9, 2023): after checking the difference between the versions 1.91 and 1.92 looks like we need to use **compat_dir** parameter to resolve this issue which is added newly in 1.92 s3fs bucketname:/folderpath /mountpath -o allow_other,use_cache=/tmp,connect_timeout=10,nonempty,umask=0022,**compat_dir**

kerem commented

2026-03-04 01:51:30 +03:00

Author

Owner

@gaul commented on GitHub (Jun 10, 2023):

Could you be more specific about what the directory layout looks like, e.g., AWS CLI --recursive output? You should not need this flag for most buckets.

@gaul commented on GitHub (Jun 10, 2023): Could you be more specific about what the directory layout looks like, e.g., AWS CLI --recursive output? You should not need this flag for most buckets.

kerem commented

2026-03-04 01:51:30 +03:00

Author

Owner

@ggtakec commented on GitHub (Jun 10, 2023):

@sathishstorm Sorry to make you spend time to confirm.
As you've noticed, from v1.92 there are times when you should give compat_dir in bucket/folder checks.
It is required for folders created by clients other than s3fs.

For reference, when this error occurs, v1.92 will output the following to the log:

Failed to check bucket and directory for mount point : Bucket or directory(/xxxxxxx) not found(host=https://xxxx.amazonaws.com) - You may need to specify the compat_dir option.

Thanks for your kindness.

@ggtakec commented on GitHub (Jun 10, 2023): @sathishstorm Sorry to make you spend time to confirm. As you've noticed, from v1.92 there are times when you should give `compat_dir` in `bucket/folder` checks. It is required for folders created by clients other than s3fs. For reference, when this error occurs, v1.92 will output the following to the log: ``` Failed to check bucket and directory for mount point : Bucket or directory(/xxxxxxx) not found(host=https://xxxx.amazonaws.com) - You may need to specify the compat_dir option. ``` Thanks for your kindness.

kerem referenced this issue

2026-03-04 02:02:20 +03:00

[PR #1113] [MERGED] Remove unused field #1824