fstab ignores allow_other about goofys HOT 17 CLOSED

Wasn't it working before? What's changed?

from goofys.

fstab mount was never working. Once you made the fix that got it working, this new issue arose.

If I mount from command line the -o allow_other does work and has been working.

from goofys.

What's the symptom? I am able to have allow_other in fstab and mount as root, and then access the files as a regular user.

from goofys.

I was not getting that behavior. I 'sudo mount /mnt/mountpoint' as normal user, do not receive any errors, but the mount was owned by root and I could not access.

I will try again now and reconfirm the behavior.

from goofys.

When I mount using fstab as stated above, the mount point is owned by root:root and although with 0777 normal user cannot create files.

from goofys.

Looks like allow_other is fine but user/umask are not plumbed through correctly

from goofys.

I see. Is that a me thing or you?

Danny Greer
CPi Syndication
Direct Tel/Fax: (212) 500-0913

On Nov 11, 2015, at 6:19 PM, Ka-Hing Cheung [email protected] wrote:

Looks like allow_other is fine but user/umask are not plumbed through correctly

—
Reply to this email directly or view it on GitHub.

from goofys.

Yes I can reproduce the problem

from goofys.

I deleted the source and binary, then did go get and go install again but have the same problem. I've checked that the latest source did download.

from goofys.

Did go install put goofys at the right place to be run by mount?

from goofys.

It doesn't but I have a symlink in /usr/bin

Danny Greer
CPi Syndication
Direct Tel/Fax: (212) 500-0913

On Nov 12, 2015, at 3:21 AM, Ka-Hing Cheung [email protected] wrote:

Did go install put goofys at the right place to be run by mount?

—
Reply to this email directly or view it on GitHub.

from goofys.

I am not able to reproduce this:

$ tail -1 /etc/fstab
goofys#goofys   /tmp/mnt        fuse    allow_other,--file-mode=0777,--uid=1001 0       0
$ touch /tmp/mnt/a
$ ls -l /tmp/mnt/
-rwxrwxrwx 1 khc root         0 Nov 12 12:47 a

In another issue you mentioned that there's a copy of goofys in /bin, can you try to strace thing again and see if it's executing the correct copy?

from goofys.

You have the same problem. a is owned by root. try with a --uid=[other than root].

The mount will still be owned by root. I get the correct drwxrwxrwx but owner of the mount is root even though I specified the www-data:www-data account.

I can create files because of the permissions being -rwxrwxrwx but they are owned by root and not the user specified but --uid or even the current user.

I have verified that I only have one goofys binary in the filesystem anywhere and one symlink pointing to it.

from goofys.

No, a is owned by khc and group is root. uid 1001 in fstab is khc.

from goofys.

just verified --gid works from mount too:

$ tail -1 /etc/fstab
goofys#goofys   /tmp/mnt        fuse    allow_other,--file-mode=0777,--uid=1001,--gid=1001      0       0
$ ls -l /tmp/mnt/a
-rwxrwxrwx 1 khc khc         0 Nov 12 12:47 a

from goofys.

Your fstab looks a little strange:

`goofys#cpirepsarchive   /mnt/cpirepsarchive.s3 fuse    allow_other,--file-mode=0777,--dir-mode=0777,--uid="33,--gid="33",--storage-class="REDUCED_REDUNDANCY"    0       0`

notice the extra " after --uid

from goofys.

Thank you! I was just examining that line in fstab looking for a typo, and could not see it staring me in the face.

It, of course works now. But I'm afraid I have found a new problem.... Try to 'touch test', then 'rm test' then if you 'touch test' again and 'ls' there is nothing. I'll create a separate issue.

from goofys.