[GH-ISSUE #2809] Mounting Bucket Subdirectory Fails in v1.97 #1305

New issue

Open

opened 2026-03-04 01:52:58 +03:00 by kerem · 0 comments

kerem commented

2026-03-04 01:52:58 +03:00

Owner

Originally created by @Benedikt0x4C on GitHub (Feb 25, 2026).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/2809

We use s3fs-fuse to mount subdirectories in S3 buckets. These subdirectories were properly created through the file system before (not using the AWS console).

We've been using s3fs-fuse v1.95 for quite some time without any issues; it mounts subdirectories fine. As an example:

s3fs my-s3-bucket:/assets /var/www/assets -o iam_role

That said, after the update to v1.97, it fails to mount with the exact same commands, if it contains an S3 bucket subdirectory. It does not show any error message or logs any error that we could find. It doesn't matter if you use the command line or /etc/fstab to mount a subdirectory of an S3 bucket, it will refuse to mount in both cases. What still worked in v1.97 is if you simply mount the root directory of an S3 bucket, e.g., s3fs my-s3-bucket /var/www/assets -o iam_role.

After downgrading s3fs-fuse to v1.95 again, mounting a subdirectory of an S3 bucket worked flawlessly again.

We're using official packages that are distributed with Rocky Linux 9.

Additional Information

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

Amazon Simple Storage Service File System V1.97 with OpenSSL

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

Name : fuse
Version : 2.9.9
Release : 16.el9
Architecture: x86_64

Provider (`AWS`, `OVH`, `Hetzner`, `iDrive E2`, ...)

AWS

Kernel information (`uname -r`)

5.14.0-611.30.1.el9_7.x86_64

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

NAME="Rocky Linux"
VERSION="9.5 (Blue Onyx)"

How to run s3fs, if applicable

[x] command line
[x] /etc/fstab

Command line:

s3fs my-s3-bucket:/assets /var/www/assets -o iam_role

/etc/fstab:

my-s3-bucket:/assets /var/www/assets fuse.s3fs _netdev,allow_other,iam_role,umask=002,uid=1000,gid=48 0 0

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

(No relevant logs in journalctl.)

Originally created by @Benedikt0x4C on GitHub (Feb 25, 2026). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/2809 We use `s3fs-fuse` to mount subdirectories in S3 buckets. These subdirectories were properly created through the file system before (**not** using the AWS console). We've been using `s3fs-fuse` v1.95 for quite some time without any issues; it mounts subdirectories fine. As an example: ``` s3fs my-s3-bucket:/assets /var/www/assets -o iam_role ``` That said, after the update to v1.97, it fails to mount with the exact same commands, if it contains an S3 bucket subdirectory. It does not show any error message or logs any error that we could find. It doesn't matter if you use the command line or `/etc/fstab` to mount a subdirectory of an S3 bucket, it will refuse to mount in both cases. What still worked in v1.97 is if you simply mount the root directory of an S3 bucket, e.g., `s3fs my-s3-bucket /var/www/assets -o iam_role`. After downgrading `s3fs-fuse` to v1.95 again, mounting a subdirectory of an S3 bucket worked flawlessly again. We're using official packages that are distributed with Rocky Linux 9. ### Additional Information #### Version of s3fs being used (`s3fs --version`) Amazon Simple Storage Service File System V1.97 with OpenSSL #### Version of fuse being used (`pkg-config --modversion fuse`, `rpm -qi fuse` or `dpkg -s fuse`) Name : fuse Version : 2.9.9 Release : 16.el9 Architecture: x86_64 #### Provider (`AWS`, `OVH`, `Hetzner`, `iDrive E2`, ...) AWS #### Kernel information (`uname -r`) 5.14.0-611.30.1.el9_7.x86_64 #### GNU/Linux Distribution, if applicable (`cat /etc/os-release`) NAME="Rocky Linux" VERSION="9.5 (Blue Onyx)" #### How to run s3fs, if applicable [x] command line [x] /etc/fstab Command line: ``` s3fs my-s3-bucket:/assets /var/www/assets -o iam_role ``` /etc/fstab: ``` my-s3-bucket:/assets /var/www/assets fuse.s3fs _netdev,allow_other,iam_role,umask=002,uid=1000,gid=48 0 0 ``` #### s3fs syslog messages (`grep s3fs /var/log/syslog`, `journalctl | grep s3fs`, or `s3fs outputs`) (No relevant logs in `journalctl`.)