Subfolders are owned and readable only by root

[GoogleCodeExporter]

When mounting a bucket, I have access to files within the root of the bucket, 
but anything in folders created from AWS's S3 manager are not accessible as 
they are "root" owned.

A "ls -l" will show this within the bucket root folder:
d--------- 1 root root 0 May 31 23:34 craft
d--------- 1 root root 0 Aug  8 21:31 world
d--------- 1 root root 0 Aug 15 20:04 tiles

Creating new folders will assign the proper ownership and behavior works as 
expected.

s3fs --version
Amazon Simple Storage Service File System 1.73

pkg-config --modversion fuse
2.9.0
System information (uname -a):

cat /etc/issue
Linux Mint 15 Olivia

Original issue reported on code.google.com by clkr...@gmail.com on 5 Sep 2013 at 1:26

[GoogleCodeExporter]

Forgot this:

uname -a
Linux zo-m1 3.8.0-29-generic #42-Ubuntu SMP Tue Aug 13 19:40:39 UTC 2013 x86_64
x86_64 x86_64 GNU/Linux

Original comment by clkr...@gmail.com on 5 Sep 2013 at 1:27

[GoogleCodeExporter]

Hi,

s3fs can list the object(directory and file) which are uploaded and made by 
other clients(ex, s3 console).
But these object does not have "x-ams-meta-***" attribute headers which are 
used s3fs for object stat(owner/group/mtime/permission).
Then you can see "d---------" directory which is made by other clients, and 
that does not have attar headers.

Leatest version(revision) s3fs supports "umask" option, you can set umask 
option.
Thus if you specifiy the value(0022) to umask option, the object which did not 
have read-write permission("d---------") can be saw "drwxr-xr-x".

Please try to set umask(and uid/gid) option.
I closed this issue, if you have more problem please let me know.

Thanks in advance for your help.

Original comment by ggta...@gmail.com on 17 Sep 2013 at 6:50

• Changed state: Done

[GoogleCodeExporter]

Please use umask=0022 option it works

Original comment by paraspri...@gmail.com on 31 Jan 2014 at 8:41