[GH-ISSUE #2264] Only when refreshing the directory, the meta information(timestamp) of files in that directory will be updated #1139

New issue

Closed

opened 2026-03-04 01:51:41 +03:00 by kerem · 2 comments

kerem commented

2026-03-04 01:51:41 +03:00

Owner

Originally created by @jestiny0 on GitHub (Aug 14, 2023).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/2264

Additional Information

Version of s3fs being used (`s3fs --version`)

V1.86

Version of fuse being used (`pkg-config --modversion fuse`, `rpm -qi fuse` or `dpkg -s fuse`)

2.9.9-3

Kernel information (`uname -r`)

5.15.0-1040-aws

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

NAME="Ubuntu"
VERSION="20.04.2 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.2 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal

How to run s3fs, if applicable

mkdir /models-s3 && echo xxx > /passwd-s3fs && chmod 600 /passwd-s3fs && s3fs model /models-s3 -o passwd_file=/passwd-s3fs

Details about issue

I have a Java program that checks the timestamp and size of a certain file to determine whether to reload the file. The core code is as follows:

File f = new File("vocab");
        long lastModify = f.lastModified();
        long size = f.length();
        System.out.println(lastModify);
        System.out.println(size);

Problem Reproduction:

Run the Java program and find that the file's timestamp is 1.
Use the "ls" command on the file in the directory and find that the timestamp is 1 (it should actually be 2).
Use the "ls" command on the directory and find that the timestamp becomes 2.
Use the "ls" command on the file and find that the timestamp also becomes 2.
Run the Java program again, and the timestamp is successfully changed to 2

Originally created by @jestiny0 on GitHub (Aug 14, 2023). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/2264  ### Additional Information #### Version of s3fs being used (`s3fs --version`)  V1.86 #### Version of fuse being used (`pkg-config --modversion fuse`, `rpm -qi fuse` or `dpkg -s fuse`)  2.9.9-3 #### Kernel information (`uname -r`)  5.15.0-1040-aws #### GNU/Linux Distribution, if applicable (`cat /etc/os-release`)  NAME="Ubuntu" VERSION="20.04.2 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.2 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/" SUPPORT_URL="https://help.ubuntu.com/" BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/" PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy" VERSION_CODENAME=focal UBUNTU_CODENAME=focal #### How to run s3fs, if applicable `mkdir /models-s3 && echo xxx > /passwd-s3fs && chmod 600 /passwd-s3fs && s3fs model /models-s3 -o passwd_file=/passwd-s3fs` ### Details about issue  <img width="1110" alt="image" src="https://github.com/s3fs-fuse/s3fs-fuse/assets/105039245/130ed2bd-3248-4bfe-9ba6-6eba3893c192"> I have a Java program that checks the timestamp and size of a certain file to determine whether to reload the file. The core code is as follows: ``` File f = new File("vocab"); long lastModify = f.lastModified(); long size = f.length(); System.out.println(lastModify); System.out.println(size); ``` Problem Reproduction: 1. Run the Java program and find that the file's timestamp is 1. 2. Use the "ls" command on the file in the directory and find that the timestamp is 1 (it should actually be 2). 3. Use the "ls" command on the directory and find that the timestamp becomes 2. 4. Use the "ls" command on the file and find that the timestamp also becomes 2. 5. Run the Java program again, and the timestamp is successfully changed to 2

kerem closed this issue

2026-03-04 01:51:42 +03:00

kerem commented

2026-03-04 01:51:42 +03:00

Author

Owner

@gaul commented on GitHub (Aug 14, 2023):

1.86 has no default time limit for caching metadata. If you set -o stat_cache_expire=900 then it will only be cached for 15 minutes. 1.89 and later set this value by default.

@gaul commented on GitHub (Aug 14, 2023): 1.86 has no default time limit for caching metadata. If you set `-o stat_cache_expire=900` then it will only be cached for 15 minutes. 1.89 and later set this value by default.

kerem commented

2026-03-04 01:51:42 +03:00

Author

Owner

@jestiny0 commented on GitHub (Aug 15, 2023):

Fixed! Thanks for your reply

@jestiny0 commented on GitHub (Aug 15, 2023): Fixed! Thanks for your reply