[GH-ISSUE #2525] Prefix options don't seem to work unless prefix is "/" #1234

New issue

Open

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

kerem commented

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

Owner

Originally created by @nhartwic on GitHub (Sep 26, 2024).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/2525

s3fs seems to work fine for me when I want to mount a whole bucket, but all of my attempts to mount a specific path seem to have failed. Brief command line snippet as an example:

$ s3fs $MYBUCKET:/root/ data/
$ ls data/
$ s3fs $MYBUCKET:/root data/
$ ls data/
$ s3fs $MYBUCKET:/ data/
$ ls data/
baobab  index.html  jbrowsers  misc  resources  root  ucscGenomeBrowserHubs

Note that "$MYBUCKET:/root/" clearly exists since I can mount the bucket with a "/" prefix and see that "root" exists, but whenever I try to more directly mount "root", it just doesn't work. And this seems to be true for any prefix I've tested other than "/"

Other requested information:

$ s3fs --version
Amazon Simple Storage Service File System V1.93 (commit:unknown) with GnuTLS(gcrypt)
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.

$ pkg-config --modversion fuse
Package fuse was not found in the pkg-config search path.
Perhaps you should add the directory containing `fuse.pc'
to the PKG_CONFIG_PATH environment variable
Package 'fuse', required by 'virtual:world', not found

$ uname -r
6.8.0-45-generic

$ cat /etc/os-release
PRETTY_NAME="Ubuntu 24.04.1 LTS"
NAME="Ubuntu"
VERSION_ID="24.04"
VERSION="24.04.1 LTS (Noble Numbat)"
VERSION_CODENAME=noble
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=noble
LOGO=ubuntu-logo

At the moment, my workaround is to just mount the bucket and then softlink to the prefix, but this is messier than I'd like.

Originally created by @nhartwic on GitHub (Sep 26, 2024). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/2525 s3fs seems to work fine for me when I want to mount a whole bucket, but all of my attempts to mount a specific path seem to have failed. Brief command line snippet as an example: ``` $ s3fs $MYBUCKET:/root/ data/ $ ls data/ $ s3fs $MYBUCKET:/root data/ $ ls data/ $ s3fs $MYBUCKET:/ data/ $ ls data/ baobab index.html jbrowsers misc resources root ucscGenomeBrowserHubs ``` Note that "$MYBUCKET:/root/" clearly exists since I can mount the bucket with a "/" prefix and see that "root" exists, but whenever I try to more directly mount "root", it just doesn't work. And this seems to be true for any prefix I've tested other than "/" Other requested information: ``` $ s3fs --version Amazon Simple Storage Service File System V1.93 (commit:unknown) with GnuTLS(gcrypt) 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. $ pkg-config --modversion fuse Package fuse was not found in the pkg-config search path. Perhaps you should add the directory containing `fuse.pc' to the PKG_CONFIG_PATH environment variable Package 'fuse', required by 'virtual:world', not found $ uname -r 6.8.0-45-generic $ cat /etc/os-release PRETTY_NAME="Ubuntu 24.04.1 LTS" NAME="Ubuntu" VERSION_ID="24.04" VERSION="24.04.1 LTS (Noble Numbat)" VERSION_CODENAME=noble ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/" SUPPORT_URL="https://help.ubuntu.com/" BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/" PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy" UBUNTU_CODENAME=noble LOGO=ubuntu-logo ``` At the moment, my workaround is to just mount the bucket and then softlink to the prefix, but this is messier than I'd like.

kerem commented

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

Author

Owner

@KirigiriSuzumiya commented on GitHub (Dec 20, 2024):

Same issue appeared when using self-hosted minio as s3 backend. Any progress? @nhartwic

@KirigiriSuzumiya commented on GitHub (Dec 20, 2024): Same issue appeared when using self-hosted minio as s3 backend. Any progress? @nhartwic

kerem commented

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

Author

Owner

@ggtakec commented on GitHub (Jan 19, 2025):

Try starting s3fs with dbglevel=info (or dbglevel=dbg) and curldbg options and get the execution log.
The log may provide some clues to solving this problem.

@ggtakec commented on GitHub (Jan 19, 2025): Try starting s3fs with `dbglevel=info` (or `dbglevel=dbg`) and `curldbg` options and get the execution log. The log may provide some clues to solving this problem.