[GH-ISSUE #1248] File content not being updated but timestamps are! #667

New issue

Closed

opened 2026-03-04 01:47:43 +03:00 by kerem · 2 comments

kerem commented

2026-03-04 01:47:43 +03:00

Owner

Originally created by @sharmad on GitHub (Feb 26, 2020).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1248

Version of s3fs being used

1.79

Version of fuse being used

2.9.4

Kernel information (uname -r)

4.14.158-101.185.amzn1.x86_64

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

NAME="Amazon Linux AMI"
VERSION="2018.03"
ID="amzn"
ID_LIKE="rhel fedora"
VERSION_ID="2018.03"
PRETTY_NAME="Amazon Linux AMI 2018.03"
ANSI_COLOR="0;33"
CPE_NAME="cpe:/o:amazon:linux:2018.03:ga"
HOME_URL="http://aws.amazon.com/amazon-linux-ami/"

/etc/fstab entry

s3fs#shared-bucket /s3mnt fuse allow_other,use_rrs,uid=test,gid=test,use_cache=/storage/s3-cache-shared,iam_role=test-role,_netdev 0 0

Details about issue

We have several servers using s3fs-fuse to mount the same s3 bucket and accessing the target file object. However, we found that updating the file, updated it in some servers but not in others. Interestingly, the timestamp updated in all servers and their caches, but the content didn't for around half.

It should also be noted that we were just updating one character in this 20.9kb file. For example, going from "38" to "37" in a line somewhere in the file.

Temporarily, this was fixed by removing the file from the cache directory of the problematic servers. After this we got the updated content! And the cache gets updated too with the new file/content.

Originally created by @sharmad on GitHub (Feb 26, 2020). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1248 #### Version of s3fs being used 1.79 #### Version of fuse being used 2.9.4 #### Kernel information (uname -r) 4.14.158-101.185.amzn1.x86_64 #### GNU/Linux Distribution, if applicable (cat /etc/os-release) ``` NAME="Amazon Linux AMI" VERSION="2018.03" ID="amzn" ID_LIKE="rhel fedora" VERSION_ID="2018.03" PRETTY_NAME="Amazon Linux AMI 2018.03" ANSI_COLOR="0;33" CPE_NAME="cpe:/o:amazon:linux:2018.03:ga" HOME_URL="http://aws.amazon.com/amazon-linux-ami/" ``` #### /etc/fstab entry ``` s3fs#shared-bucket /s3mnt fuse allow_other,use_rrs,uid=test,gid=test,use_cache=/storage/s3-cache-shared,iam_role=test-role,_netdev 0 0 ``` ### Details about issue We have several servers using s3fs-fuse to mount the same s3 bucket and accessing the target file object. However, we found that updating the file, updated it in some servers but not in others. Interestingly, the timestamp updated in all servers and their caches, but the content didn't for around half. It should also be noted that we were just updating one character in this 20.9kb file. For example, going from "38" to "37" in a line somewhere in the file. Temporarily, this was fixed by removing the file from the cache directory of the problematic servers. After this we got the updated content! And the cache gets updated too with the new file/content.

kerem

2026-03-04 01:47:43 +03:00

closed this issue
added the
need info
label

kerem commented

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

Author

Owner

@gaul commented on GitHub (Apr 22, 2020):

By default s3fs does not have a stat cache age. If you set -o stat_cache_expire=60 does the time update on other servers?

@gaul commented on GitHub (Apr 22, 2020): By default s3fs does not have a stat cache age. If you set `-o stat_cache_expire=60` does the time update on other servers?

kerem commented

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

Author

Owner

@gaul commented on GitHub (Jul 26, 2020):

Closing due to inactivity. Please reopen if symptoms persist.

@gaul commented on GitHub (Jul 26, 2020): Closing due to inactivity. Please reopen if symptoms persist.

kerem referenced this issue

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

[PR #668] [MERGED] Changed .travis.yml for fixing not found gpg2 on osx #1592