[GH-ISSUE #189] allow_other Not Working #107

New issue

Closed

opened 2026-03-04 01:42:11 +03:00 by kerem · 3 comments

kerem commented

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

Owner

Originally created by @bubba-h57 on GitHub (May 13, 2015).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/189

I began attempting to use s3fs yesterday, and have since then spent the majority of my time attempting to sort out permissions.

I followed the instructions at Installation Notes for building from the github repository (I checked out the v1.77 tag) on Ubuntu 14.04.

However, regardless of how I mount my bucket, I can not get access for anyone other than root, or a user specified via uid=. When specifying gid= along with the ever preset allow_other I can see the group is properly set, however, members of the group can not access anything, only the uid.

There appears to be very minimal documentation on the allow_other option and googling brings me a handful of stackoverflow questions that marginally speak to the issue. I can only assume that this typically just works, but I'm hopeful that someone might point me towards a solution.

I've ensured /etc/fuse.conf is properly configured, I prefer mounting as root from /etc/fstab, and I feel like I've exhausted every mount option available in my pursuit of configuring the mounted bucket for read access from others.

Thanks in advance!

Originally created by @bubba-h57 on GitHub (May 13, 2015). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/189 I began attempting to use `s3fs` yesterday, and have since then spent the majority of my time attempting to sort out permissions. I followed the instructions at [Installation Notes](https://github.com/s3fs-fuse/s3fs-fuse/wiki/Installation-Notes#tested-on-ubuntu-1404-lts) for building from the github repository _(I checked out the v1.77 tag)_ on Ubuntu 14.04. However, regardless of how I mount my bucket, I can not get access for anyone other than root, or a user specified via `uid=`. When specifying `gid=` along with the ever preset `allow_other` I can see the group is properly set, however, members of the group can not access anything, only the `uid`. There appears to be very minimal documentation on the `allow_other` option and googling brings me a handful of stackoverflow questions that marginally speak to the issue. I can only assume that this typically **just works**, but I'm hopeful that someone might point me towards a solution. I've ensured `/etc/fuse.conf` is properly configured, I prefer mounting as `root` from `/etc/fstab`, and I feel like I've exhausted every mount option available in my pursuit of configuring the mounted bucket for read access from others. Thanks in advance!

kerem closed this issue

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

kerem commented

2026-03-04 01:42:12 +03:00

Author

Owner

@bubba-h57 commented on GitHub (May 13, 2015):

It is perhaps noteworthy that I'm using s3fs to mount a bucket that has a few thousand objects already present, and that new object in this bucket will be inserted via another process. The s3fs is effectively a read-only mount for this use case.

This perhaps means that some headers are missing from my objects? If so, which ones, and how can I set them programatically when I create the new objects (which, as noted earlier, will be a different process)?

@bubba-h57 commented on GitHub (May 13, 2015): It is perhaps noteworthy that I'm using `s3fs` to mount a bucket that has a few thousand objects already present, and that new object in this bucket will be inserted via another process. The `s3fs` is effectively a read-only mount for this use case. This perhaps means that some headers are missing from my objects? If so, which ones, and how can I set them programatically when I create the new objects (which, as noted earlier, will be a different process)?

kerem commented

2026-03-04 01:42:12 +03:00

Author

Owner

@bubba-h57 commented on GitHub (May 13, 2015):

I've since discovered that adding umask=0002 to the mount options solves my access issues. I'll close this now. However, I suggest that it is worth adding something to documentation with regards to how one handles permissions on buckets that have been pre-populated. Thanks again.

@bubba-h57 commented on GitHub (May 13, 2015): I've since discovered that adding `umask=0002` to the mount options solves my access issues. I'll close this now. However, I suggest that it is worth adding something to documentation with regards to how one handles permissions on buckets that have been pre-populated. Thanks again.

kerem commented

2026-03-04 01:42:12 +03:00

Author

Owner

@thomasintveld commented on GitHub (Jun 15, 2015):

Thank you, had the same problem as bubba-h57 and adding -o umask=0002 fixed the problem. After adding your user to the fuse group and allowing fuse to user_allow_other in /etc/fuse.conf the s3fs string then becomes:
s3fs -o allow_other -o umask=0002 [bucket-name] [mount-folder]

Problem solved!

@thomasintveld commented on GitHub (Jun 15, 2015): Thank you, had the same problem as bubba-h57 and adding `-o umask=0002` fixed the problem. After adding your user to the `fuse` group and allowing fuse to `user_allow_other` in `/etc/fuse.conf` the s3fs string then becomes: `s3fs -o allow_other -o umask=0002 [bucket-name] [mount-folder]` Problem solved!

kerem referenced this issue

2026-03-04 01:53:31 +03:00

[PR #119] [MERGED] Added new mp_umask option about issue#107, pr#110 #1351