mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 13:26:00 +03:00
[GH-ISSUE #1057] [RFE] Cache Limit #581
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#581
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?
Originally created by @bstromski on GitHub (Jun 27, 2019).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1057
Additional Information
S3fs has a ensure_diskfree option, but if filesystems vary by size, ensure_diskfree would have to be dynamic to each system running s3fs.
Wouldn't it be easier to have a cache_limit option that prevents the default (tmp) or cachedir from exceeding that value? This would allow users to set X value for cache size to any cachedir they chose without the need for calculating how much free space should reside in tmp or cachedir per system.
Version of s3fs being used (s3fs --version)
s3fs-fuse-1.85-1.el7.x86_64
Version of fuse being used (pkg-config --modversion fuse, rpm -qi fuse, dpkg -s fuse)
fuse-2.9.2-10.el7.x86_64
fuse-libs-2.9.2-10.el7.x86_64
s3fs-fuse-1.85-1.el7.x86_64
Kernel information (uname -r)
3.10.0
GNU/Linux Distribution, if applicable (cat /etc/os-release)
RHEL 7.5
s3fs command line used, if applicable
/etc/fstab entry, if applicable
s3fs syslog messages (grep s3fs /var/log/syslog, journalctl | grep s3fs, or s3fs outputs)
if you execute s3fs with dbglevel, curldbg option, you can get detail debug messages