[GH-ISSUE #384] All files mounted from S3 are corrupted #202

Closed
opened 2026-03-04 01:43:13 +03:00 by kerem · 3 comments
Owner

Originally created by @gl-lamhnguyen on GitHub (Apr 2, 2016).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/384

It worked before, I don't know what update from s3fs broke it. Now all files are corrupted from local machine (but not files from S3 bucket)

Originally created by @gl-lamhnguyen on GitHub (Apr 2, 2016). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/384 It worked before, I don't know what update from s3fs broke it. Now all files are corrupted from local machine (but not files from S3 bucket)
kerem closed this issue 2026-03-04 01:43:13 +03:00
Author
Owner

@Morc001 commented on GitHub (Apr 2, 2016):

Is it not #15 by any chance? I found that turning ensure_diskfree off with caching enabled "fixes" the problem. So at the moment master branch produces all-zero content files with caching and ensure_diskfree enabled.

Morc

<!-- gh-comment-id:204768834 --> @Morc001 commented on GitHub (Apr 2, 2016): Is it not #15 by any chance? I found that turning ensure_diskfree off with caching enabled "fixes" the problem. So at the moment master branch produces all-zero content files with caching and ensure_diskfree enabled. Morc
Author
Owner

@ggtakec commented on GitHub (Apr 17, 2016):

@gl-lamhnguyen I'm sorry for late reply.
This problem might be a bug has been modified by the #395.
Currently, the bug has been fixed.
Please try to use latest codes on master branch.

Thanks in advance for your help.

<!-- gh-comment-id:210974204 --> @ggtakec commented on GitHub (Apr 17, 2016): @gl-lamhnguyen I'm sorry for late reply. This problem might be a bug has been modified by the #395. Currently, the bug has been fixed. Please try to use latest codes on master branch. Thanks in advance for your help.
Author
Owner

@ggtakec commented on GitHub (Mar 30, 2019):

We kept this issue open for a long time.
We launch new version 1.86, which fixed some problem(bugs).
Please use the latest version.
I will close this, but if the problem persists, please reopen or post a new issue.

<!-- gh-comment-id:478216372 --> @ggtakec commented on GitHub (Mar 30, 2019): We kept this issue open for a long time. We launch new version 1.86, which fixed some problem(bugs). Please use the latest version. I will close this, but if the problem persists, please reopen or post a new issue.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/s3fs-fuse#202
No description provided.