[GH-ISSUE #2390] The file being updated doesn't exist for a few seconds #1172

New issue

Closed

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

kerem commented

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

Owner

Originally created by @ParadiseLost5 on GitHub (Dec 13, 2023).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/2390

Additional Information

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

V1.82

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

2.9.2

Kernel information (`uname -r`)

3.10.0-1160.el7.x86_64

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

CentOS Linux Version 7 (Core)

How to run s3fs

In fstab:
S3_bucket_name /home/S3-test fuse.s3fs _netdev, allow_other 0 0

Details about issue

I have two different networks, each with a Linux VM mounting S3 to a local folder via S3FS, and Samba turning this local folder into a shared network folder so Windows machines in the same network will be able to access it. The UNC path of the shared folder is identical in both of the networks (for example: "\SharedFilesServer\SharedFiles").
When I update a 1MB file in the shared folder in one env, the corresponding file in the shared folder on the other env doesn't exist for a few seconds (while it is being replaced by the updated file).
Is there a configuration I can use that will ensure the file will always remain available (until its update is done)?
Thanks

Originally created by @ParadiseLost5 on GitHub (Dec 13, 2023). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/2390 ### Additional Information #### Version of s3fs being used (`s3fs --version`) V1.82 #### Version of fuse being used (`pkg-config --modversion fuse`, `rpm -qi fuse` or `dpkg -s fuse`) 2.9.2 #### Kernel information (`uname -r`) 3.10.0-1160.el7.x86_64 #### GNU/Linux Distribution, if applicable (`cat /etc/os-release`) CentOS Linux Version 7 (Core) #### How to run s3fs In fstab: S3_bucket_name /home/S3-test fuse.s3fs _netdev, allow_other 0 0 ### Details about issue I have two different networks, each with a Linux VM mounting S3 to a local folder via S3FS, and Samba turning this local folder into a shared network folder so Windows machines in the same network will be able to access it. The UNC path of the shared folder is identical in both of the networks (for example: "\\SharedFilesServer\SharedFiles"). When I update a 1MB file in the shared folder in one env, the corresponding file in the shared folder on the other env doesn't exist for a few seconds (while it is being replaced by the updated file). Is there a configuration I can use that will ensure the file will always remain available (until its update is done)? Thanks

kerem closed this issue

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

kerem commented

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

Author

Owner

@ParadiseLost5 commented on GitHub (Jan 3, 2024):

An update: we've solved this issue by adding a retry mechanism on the server side. Plus, we configured S3FS to use local cache on both of the envs. This decreased the save time of files, and also solved an issue where files were corrupted on one env.
To do so, just add "use_cache=/tmp" to the fstab file. For example:
<mount_folder_path> fuse.s3fs _netdev,allow_other,use_cache=/tmp 0 0

@ParadiseLost5 commented on GitHub (Jan 3, 2024): An update: we've solved this issue by adding a retry mechanism on the server side. Plus, we configured S3FS to use local cache on both of the envs. This decreased the save time of files, and also solved an issue where files were corrupted on one env. To do so, just add "use_cache=/tmp" to the fstab file. For example: <mount_folder_path> fuse.s3fs _netdev,allow_other,use_cache=/tmp 0 0

kerem commented

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

Author

Owner

@ParadiseLost5 commented on GitHub (Jan 3, 2024):

I'm closing this issue since implementing a simple retry mechanism solved it.

@ParadiseLost5 commented on GitHub (Jan 3, 2024): I'm closing this issue since implementing a simple retry mechanism solved it.