mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 13:26:00 +03:00
[GH-ISSUE #1563] Default stat_cache_expire not taking effect #820
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#820
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 @lincheney on GitHub (Feb 10, 2021).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1563
Additional Information
The following information is very important in order to help us to help you. Omission of the following details may delay your support request or receive no attention at all.
Keep in mind that the commands we provide to retrieve information are oriented to GNU/Linux Distributions, so you could need to use others if you use s3fs on macOS or BSD
Version of s3fs being used (s3fs --version)
example: 1.00
V1.86 (commit:e2fbcb4)
Version of fuse being used (pkg-config --modversion fuse, rpm -qi fuse, dpkg -s fuse)
example: 2.9.4
2.9.2
Kernel information (uname -r)
command result: uname -r
3.10.0-1127.10.1.el7.x86_64
GNU/Linux Distribution, if applicable (cat /etc/os-release)
command result: cat /etc/os-release
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
Details about issue
The man page specifies that the
-o stat_cache_expire (default is 900), but this does not appear to be the case, stat cache seems to last forever.If the
stat_cache_expireoption is explicitly set to a value, then the caching expiry works.I believe this may be due to
IsExpireTimestill being set to false by default:https://github.com/s3fs-fuse/s3fs-fuse/blob/master/src/cache.cpp#L153
@gaul commented on GitHub (Feb 10, 2021):
This makes sense. Could you test this locally and submit a pull request to correct this value?