starred/s3fs-fuse

Fork 0

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

[GH-ISSUE #2032] umask and mp_umask are mutually exclusive in that using umask causes mp_umask to be overridden #1022

New issue

Closed

opened 2026-03-04 01:50:44 +03:00 by kerem · 3 comments

kerem commented

2026-03-04 01:50:44 +03:00

Owner

Originally created by @michaelsmoody on GitHub (Sep 16, 2022).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/2032

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)

s3fs 1.91

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

FUSE 2.9.2

Kernel information (uname -r)

5.10.135-122.509.amzn2.x86_64

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

Amazon Linux 2

s3fs command line used, if applicable

s3fs -o url=https://s3-us-gov-west-1.amazonaws.com -o endpoint=us-gov-west-1 -o allow_other -o umask=007 -o mp_umask=022 -o dev -o suid -o use_xattr cust-s3-transfer-storage:/FOLDER /mnt/folder

/etc/fstab entry, if applicable

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

if you execute s3fs with dbglevel, curldbg option, you can get detail debug messages

2022-09-16T18:46:15.410Z [INF]     s3fs.cpp:set_mountpoint_attribute(3628): PROC(uid=0, gid=0) - MountPoint(uid=0, gid=0, mode=40755)

Details about issue

Despite this line in the logs, despite this setting, it appears that umask and mp_umask are mutually exclusive, and that when both are set, my mountpoint gets set to the setting of umask NO MATTER WHAT, which prevents what I need to work from actually working.

drwxrwx---. 1 root root 0 Jan 1 1970 /mnt/folder

This is an unfortunate consequence (combined of course with the sticky bit problem, and several other blocking issues as well) that prevents production usage of S3FS at this time.

I've attempted a combination of removing and adding options for this and other reasons, such as the reason this is being worked on in the first place, CHROOT (suid, dev, uid/gid, etc), and while uid/gid are properly obeyed, they do have another unfortunate consequence that I'll bring up elsewhere.

Any help of course that you can provide would be greatly appreciated!

Originally created by @michaelsmoody on GitHub (Sep 16, 2022). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/2032 ### 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) s3fs 1.91 #### Version of fuse being used (pkg-config --modversion fuse, rpm -qi fuse, dpkg -s fuse) FUSE 2.9.2 #### Kernel information (uname -r) 5.10.135-122.509.amzn2.x86_64 #### GNU/Linux Distribution, if applicable (cat /etc/os-release) Amazon Linux 2 #### s3fs command line used, if applicable ``` s3fs -o url=https://s3-us-gov-west-1.amazonaws.com -o endpoint=us-gov-west-1 -o allow_other -o umask=007 -o mp_umask=022 -o dev -o suid -o use_xattr cust-s3-transfer-storage:/FOLDER /mnt/folder ``` #### /etc/fstab entry, if applicable ``` ``` #### s3fs syslog messages (grep s3fs /var/log/syslog, journalctl | grep s3fs, or s3fs outputs) _if you execute s3fs with dbglevel, curldbg option, you can get detail debug messages_ ``` 2022-09-16T18:46:15.410Z [INF] s3fs.cpp:set_mountpoint_attribute(3628): PROC(uid=0, gid=0) - MountPoint(uid=0, gid=0, mode=40755) ``` ### Details about issue Despite this line in the logs, despite this setting, it appears that `umask` and `mp_umask` are mutually exclusive, and that when both are set, my mountpoint gets set to the setting of `umask` **NO MATTER WHAT**, which prevents what I need to work from actually working. `drwxrwx---. 1 root root 0 Jan 1 1970 /mnt/folder` This is an unfortunate consequence (combined of course with the sticky bit problem, and several other blocking issues as well) that prevents production usage of S3FS at this time. I've attempted a combination of removing and adding options for this and other reasons, such as the reason this is being worked on in the first place, CHROOT (`suid`, `dev`, `uid`/`gid`, etc), and while `uid`/`gid` are properly obeyed, they do have another unfortunate consequence that I'll bring up elsewhere. Any help of course that you can provide would be greatly appreciated!

kerem closed this issue

2026-03-04 01:50:44 +03:00

kerem commented

2026-03-04 01:50:45 +03:00

Author

Owner

@ggtakec commented on GitHub (Sep 24, 2022):

I believe this issue will be resolved once #1964 is merged.
With the above PR, you will be able to set permissions for mount points.
I believe that mp_umask will be deprecated accordingly.
Please wait until it is merged.

@ggtakec commented on GitHub (Sep 24, 2022): I believe this issue will be resolved once #1964 is merged. With the above PR, you will be able to set permissions for mount points. I believe that mp_umask will be deprecated accordingly. Please wait until it is merged.

kerem commented

2026-03-04 01:50:45 +03:00

Author

Owner

@michaelsmoody commented on GitHub (Oct 23, 2022):

@ggtakec I've seen #1964 merged, however would you mind confirming that mp_umask is indeed being deprecated and that I should now chaos/chown the mountpount directly? Do you happen do know when a release might be made with this commit/merge? (No push, just curious what the release cycle looks like)

@michaelsmoody commented on GitHub (Oct 23, 2022): @ggtakec I've seen #1964 merged, however would you mind confirming that mp_umask is indeed being deprecated and that I should now chaos/chown the mountpount directly? Do you happen do know when a release might be made with this commit/merge? (No push, just curious what the release cycle looks like)

kerem commented

2026-03-04 01:50:45 +03:00

Author

Owner

@ggtakec commented on GitHub (Feb 12, 2023):

We'd like to release it sooner, but we don't have a firm date yet. (#2102)
This issue will be closed, but please reopen it if you still have problems.

@ggtakec commented on GitHub (Feb 12, 2023): We'd like to release it sooner, but we don't have a firm date yet. (#2102) This issue will be closed, but please reopen it if you still have problems.

kerem referenced this issue

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

[PR #1024] [CLOSED] Fix issues #1022 File been incorrect truncated when writing via nfs which mounted on s3fs-fuse #1767

kerem referenced this issue

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

[PR #1023] [CLOSED] fix bug #1022 #1768