mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 05:16:00 +03:00
[PR #2539] [MERGED] Fixed fake_diskfree option #2605
Labels
No labels
bug
bug
dataloss
duplicate
enhancement
feature request
help wanted
invalid
need info
performance
pull-request
question
question
testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/s3fs-fuse#2605
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/s3fs-fuse/s3fs-fuse/pull/2539
Author: @ggtakec
Created: 10/6/2024
Status: ✅ Merged
Merged: 10/6/2024
Merged by: @gaul
Base:
master← Head:fix/fake_diskfree📝 Commits (1)
2fc88ddFixed fake_diskfree option📊 Changes
3 files changed (+58 additions, -50 deletions)
View changed files
📝
src/fdcache.cpp(+18 -19)📝
src/fdcache.h(+8 -4)📝
src/s3fs.cpp(+32 -27)📄 Description
Relevant Issue (if applicable)
( #2538 is weakly related issues )
Details
The value of the
fake_diskfreeoption was affected by the values of thefree_space_ratioandensure_diskfreeoptions, and in some cases it could not be set.Originally,
fake_diskfreewas an option for debugging s3fs, setting a pseudo amount of free disk space, so it should not have been affected by the results of the check of the amount of free space required when s3fs was started.If the amount of free space was below the minimum required for multipart uploads, etc., it was unable to be set, but we have changed it so that it can be set without being affected by this condition.
When making this correction, we also found an error in the mutual exclusion control (mutex), so we have corrected that at the same time.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.