Bug 1158130
| Summary: | Not possible to disable fopen-keeo-cache when mounting | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Philip Spencer <pspencer> | ||||
| Component: | fuse | Assignee: | Amar Tumballi <atumball> | ||||
| Status: | CLOSED NEXTRELEASE | QA Contact: | |||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | mainline | CC: | atumball, bugs, kaushal, nbalacha, vbellur | ||||
| Target Milestone: | --- | Keywords: | Patch, Triaged | ||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2019-08-16 05:35:37 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
GlusterFS-3.6 is nearing its End-Of-Life, only important security bugs still make a chance on getting fixed. Moving this to the mainline 'version'. If this needs to get fixed in 3.7 or 3.8 this bug should get cloned. REVIEW: https://review.gluster.org/22678 (mount.glusterfs: make fcache-keep-open option take a value) posted (#1) for review on master by Amar Tumballi REVIEW: https://review.gluster.org/22678 (mount.glusterfs: make fcache-keep-open option take a value) merged (#4) on master by Amar Tumballi |
Created attachment 951449 [details] Patch to allow mounting with -o fopen-keep-cache=off It is not possible, when using the regular mount command, to stop glusterfs from using fopen-keep-cache, which is the default when fuse supports automatic cache revalidation. The glusterfs executable accepts "--fopen-keep-cache=off", but mount.glusterfs does not; it only accepts "--fopen-keep-cache" with no arguments. The attached patch fixes that and also corrects the documentation which incorrectly states that the default value of fopen-keep-cache is false whereas in fact the default value is true if fuse supports automatic cache revalidation.