permissions when using the same bucket mounted on multiple servers

[GoogleCodeExporter]

Detailed description of observed behavior:

We use Drupal on AWS Linux boxes with an s3fs mount for the folder which 
contains user uploaded and cache file. The mount point is used on 2 servers. 
When we change permissions on one folder within the s3fs mount it does not 
consistently reflect when viewed from the other server. i.e. we have a folder 
ctools/css which when changed to 777 shows up on the server where the change 
was made correctly, but shows up without the applied change on the other box it 
is mounted on.

What steps will reproduce the problem - please be very specific and
detailed. (if the developers cannot reproduce the issue, then it is
unlikely a fix will be found)?

===================================================================
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.
===================================================================
Version of s3fs being used (s3fs --version):

Version of fuse being used (pkg-config --modversion fuse):

System information (uname -a):

Distro (cat /etc/issue):

s3fs command line used (if applicable):

/etc/fstab entry (if applicable):

s3fs syslog messages (grep s3fs /var/log/syslog):

Original issue reported on code.google.com by james...@gmail.com on 2 Oct 2013 at 3:24

[GoogleCodeExporter]

Sorry the details are as follows:
s3fs version 1.73
Fuse version 2.9.2
Distro Amazon Linux AMI release 2013.03
s3fs command line: s3fs -o allow_other -o use_cache=/tmp/s3fs <bucketname> 
/var/www/s3files

Original comment by james...@gmail.com on 2 Oct 2013 at 3:28

[GoogleCodeExporter]

Hi, jamesg3d

s3fs caches file and directory stats as default.
This cache structure has ETag for the object, then if the ETag of object is 
changed, s3fs can know to need to update it's stats.
But a case of directory object S3 does not return the ETag, then s3fs's cache 
does not have stats information for it.
Then if directory stats is chafed, s3fs can not know it.

But you can take two ways for this problem.
One is that s3fs's stats cache is off by specifying "max_stat_cache_size=0" 
option.
The other is specifying the stats cache expire by "stat_cache_expire=xxx" 
option.

Please try to do these.

Regards,

Original comment by ggta...@gmail.com on 6 Oct 2013 at 3:06

[GoogleCodeExporter]

Hi,

This issue is left for a long term, and s3fs project moved on 
Github(https://github.com/s3fs-fuse/s3fs-fuse).
So I closed this issue.

If you have a problem yet, please post new issue.

Regards,

Original comment by ggta...@gmail.com on 23 Dec 2013 at 3:22

• Changed state: Done