[GH-ISSUE #2372] list_bucket request during new file creation process(macos fuse-t) #1166

New issue

Closed

opened 2026-03-04 01:51:52 +03:00 by kerem · 1 comment

kerem commented

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

Owner

Originally created by @ggtakec on GitHub (Nov 18, 2023).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/2372

Originally assigned to: @ggtakec on GitHub.

Relevant PR(Issue)

#2198

Details about issue

Due to support for macos fuse-t, Github Actions on macos12 may fail.
(We fixed some bugs in supporting macos fuse-t, but it seems that some bugs still remain.)

The problem is that s3fs no longer creates 0-byte files when first creating new files.
(This support is necessary to speed up s3fs, and the current status will continue to be maintained.)

When creating a new file, the file does not exist until s3fs uploads the file contents.
In macos-fuse-t, something like list_bucket may be called while this file is created but has not yet been uploaded(flushed).
If the list_bucket is called at this timing, the response to the HEAD request will not include the new created file, so the user will receive an error that the file does not exist.
utimens, chmod, etc. are fixed, but this list_bucket is not yet fixed.
(We have to include reading from the dummy stat cache, and we are currently considering modifying it.)

Originally created by @ggtakec on GitHub (Nov 18, 2023). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/2372 Originally assigned to: @ggtakec on GitHub. ### Relevant PR(Issue) #2198 ### Details about issue Due to support for `macos fuse-t`, Github Actions on macos12 may fail. (We fixed some bugs in supporting `macos fuse-t`, but it seems that some bugs still remain.) The problem is that s3fs no longer creates 0-byte files when first creating new files. (This support is necessary to speed up s3fs, and the current status will continue to be maintained.) When creating a new file, the file does not exist until s3fs uploads the file contents. In `macos-fuse-t`, something like `list_bucket` may be called while this file is created but has not yet been uploaded(flushed). If the `list_bucket` is called at this timing, the response to the `HEAD` request will not include the new created file, so the user will receive an error that the file does not exist. `utimens`, `chmod`, etc. are fixed, but this `list_bucket` is not yet fixed. (We have to include reading from the `dummy stat cache`, and we are currently considering modifying it.)

kerem

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

closed this issue
added the
bug
label

kerem commented

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

Author

Owner

@ggtakec commented on GitHub (Feb 23, 2024):

This problem has been resolved, but there may still be problems. It continues with #2418.

@ggtakec commented on GitHub (Feb 23, 2024): This problem has been resolved, but there may still be problems. It continues with #2418.