mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 13:26:00 +03:00
[GH-ISSUE #382] Usage of stat_cache_expire=<expiration seconds> turns off stat cache for all values of <expiration seconds> #201
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#201
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 @adupon on GitHub (Mar 29, 2016).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/382
When I include stat_cache_expire option, s3fs does not use the stat cache at all...
/usr/bin/s3fs mybucket /mnt/mybucket -ostat_cache_expire=10000,passwd_file=/etc/passwd-s3fs
I tested this using
ls /mnt/mybucket ; ls /mnt/mybucket
When stat_cache_expire is included as an option... both ls commands take about 10 seconds each.. When I remove the stat_cache_expire option... the first command takes 10 seconds, the second command is instant...
s3fs --version
Amazon Simple Storage Service File System V1.79(commit:cf56b35) with OpenSSL
@grutherford commented on GitHub (Apr 4, 2016):
I get the same issue also using v1.79 I enabled stat_cache_expire as the server memory was all getting used, since implementing this nothing is cached, do we need to set another option at the same time?
@ggtakec commented on GitHub (May 14, 2016):
@adupon and @grutherford, I'm very sorry for my late reply.
I can reproduce your report issue content, and it is a fatal bug.
So I fixed it by #415
Please use latest master branch code.
Regards,