[GH-ISSUE #868] bucket mounted by user01 successfully but all subfolders are owned by root so no access by user01 #502

New issue

Closed

opened 2026-03-04 01:46:10 +03:00 by kerem · 2 comments

kerem commented

2026-03-04 01:46:10 +03:00

Owner

Originally created by @s4mx on GitHub (Dec 5, 2018).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/868

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)

V1.84(commit:d9e89de) with OpenSSL

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

libfuse2 (= 2.9.2-4ubuntu4.14.04.1)

Kernel information (uname -r)

4.2.0-27-generic

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

NAME="Ubuntu"
VERSION="14.04.5 LTS, Trusty Tahr"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 14.04.5 LTS"
VERSION_ID="14.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"

s3fs command line used, if applicable

s3fs -o allow_other s3-bucket /s3mount/s3-bucket -o passwd_file=~/.passwd-s3fs

### Details about issue
user01@pbcg01:s3mount$ ll
drwxrwxrwx  1 user01 pbix    0 Dec 31  1969 s3-bucket

user01@pbcg01:s3mount$  ll s3-bucket/
total 5
drwxrwxrwx 1 xuem01 pbix    0 Dec 31  1969 ./
drwxrwsr-x 4 root   pbix 4096 Dec  4 17:47 ../
d--------- 1 root   root    0 Dec 31  1969 data/

Originally created by @s4mx on GitHub (Dec 5, 2018). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/868 ### 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) V1.84(commit:d9e89de) with OpenSSL #### Version of fuse being used (pkg-config --modversion fuse, rpm -qi fuse, dpkg -s fuse) libfuse2 (= 2.9.2-4ubuntu4.14.04.1) #### Kernel information (uname -r) 4.2.0-27-generic #### GNU/Linux Distribution, if applicable (cat /etc/os-release) NAME="Ubuntu" VERSION="14.04.5 LTS, Trusty Tahr" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 14.04.5 LTS" VERSION_ID="14.04" HOME_URL="http://www.ubuntu.com/" SUPPORT_URL="http://help.ubuntu.com/" BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/" #### s3fs command line used, if applicable s3fs -o allow_other s3-bucket /s3mount/s3-bucket -o passwd_file=~/.passwd-s3fs ``` ### Details about issue user01@pbcg01:s3mount$ ll drwxrwxrwx 1 user01 pbix 0 Dec 31 1969 s3-bucket user01@pbcg01:s3mount$ ll s3-bucket/ total 5 drwxrwxrwx 1 xuem01 pbix 0 Dec 31 1969 ./ drwxrwsr-x 4 root pbix 4096 Dec 4 17:47 ../ d--------- 1 root root 0 Dec 31 1969 data/

kerem closed this issue

2026-03-04 01:46:10 +03:00

kerem commented

2026-03-04 01:46:11 +03:00

Author

Owner

@gaul commented on GitHub (Feb 2, 2019):

When an object lacks permission s3fs assumes it has the most restrictive permissions, 000. Could you try mounting with -o umask=027 provides a default permission? Or try compiling from master which should also work around this symptom.

@gaul commented on GitHub (Feb 2, 2019): When an object lacks permission s3fs assumes it has the most restrictive permissions, `000`. Could you try mounting with `-o umask=027` provides a default permission? Or try compiling from master which should also work around this symptom.

kerem commented

2026-03-04 01:46:11 +03:00

Author

Owner

@gaul commented on GitHub (Apr 9, 2019):

Can you retest with 1.85 and reopen this issue if symptoms persist?

@gaul commented on GitHub (Apr 9, 2019): Can you retest with 1.85 and reopen this issue if symptoms persist?

kerem referenced this issue

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

[PR #502] [MERGED] Fixed issue#435 branch codes for remaining bugs(2) #1526

kerem referenced this issue

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