When mounted via fstab it always mounts read only.

[mobdevross]

I am sure this was working previously, but after a rebuild of the machine (using scripts) I can no longer get the bucket to mount as a read write volume when using fstab. Any help appreciated!

Mounting Using Ubuntu 18.0.4 running on Amazon EC2 with a machine role that has permissions to access the S3 bucket.

/etc/fstab
goofys#ross-incoming-binaries /mnt/s3 fuse _netdev,allow_other,--file-mode=0666,--dir-mode=0777,--debug_s3,--debug_fuse 0 0

running mount -l
ross-incoming-binaries on /mnt/s3 type fuse (ro,relatime,user_id=0,group_id=0,default_permissions,allow_other)

Output from system log:

Jan 02 20:15:06 ip-10-86-148-195 /usr/bin/goofys[1383]: s3.INFO Switching from region 'us-east-1' to 'eu-west-1'
Jan 02 20:15:06 ip-10-86-148-195 /usr/bin/goofys[1383]: [1.7K blob data]
Jan 02 20:15:06 ip-10-86-148-195 /usr/bin/goofys[1383]: [424B blob data]
Jan 02 20:15:06 ip-10-86-148-195 /usr/bin/goofys[1383]: s3.DEBUG DEBUG: Validate Response s3/HeadObject failed, not retrying, error NotFo
                                                                status code: 404, request id: 4228656EEEA3D67D, host id: aGQ+26NBRPHhhgXN
Jan 02 20:15:06 ip-10-86-148-195 /usr/bin/goofys[1383]: [1.7K blob data]
Jan 02 20:15:06 ip-10-86-148-195 /usr/bin/goofys[1383]: fuse.DEBUG Op 0x00000001        connection.go:395] <- init
Jan 02 20:15:06 ip-10-86-148-195 /usr/bin/goofys[1383]: fuse.DEBUG Op 0x00000001        connection.go:478] -> OK ()
Jan 02 20:15:06 ip-10-86-148-195 /usr/bin/goofys[1383]: main.INFO File system has been successfully mounted.
Jan 02 20:15:06 ip-10-86-148-195 /usr/bin/goofys[1383]: [425B blob data]
Jan 02 20:15:06 ip-10-86-148-195 /usr/bin/goofys[1383]: s3.DEBUG {
                                                          Bucket: "ross-incoming-binaries",
                                                          IsTruncated: false,
                                                          KeyMarker: "",
                                                          MaxUploads: 1000,
                                                          NextKeyMarker: "",
                                                          NextUploadIdMarker: "",
                                                          UploadIdMarker: ""
                                                        }

If I run goofys manually using the following it seems work correctly:
sudo goofys -f --debug_s3 --debug_fuse --file-mode=066dir-mode=0777 ross-incoming-binaries /mnt/s3

Output from mount -l
ross-incoming-binaries on /mnt/s3 type fuse (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions)

[mobdevross]

Further to this, we were building Goofys from the latest master and not using release 0.23.1.

The issue occurs in the latest master only - not on version 0.23.1 taken as a released binary. Looks like this could be a potential regression at the moment with the work being done.

[mbosner]

I have the same issue. Latest binary works, latest master does not work with fstab.

[kahing]

could you try to see if reverting dfb5c81 fixes the problem?

[arraen]

Also, have this issue. dfb5c81 revert doesn't help.
Bisect guide me to this commit: 1971d6d

[kahing]

I am able to reproduce this wtih 1971d6d the issue seems to come from the underlining fuse library. if I switch the submodule to cb66eea2377fb365bbeb3055585db6e9ea3e8226 the issue goes away

[arraen]

@kahing Yeah, sorry, I mean that 1971d6d added this issue