Bug 1170786
Summary: | man mount.glusterfs | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Khoi Mai <khoi.mai2008> |
Component: | fuse | Assignee: | bugs <bugs> |
Status: | CLOSED EOL | QA Contact: | |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.5.3 | CC: | bugs, ndevos |
Target Milestone: | --- | Keywords: | Documentation, Regression, Triaged |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-06-17 15:56:26 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: |
Description
Khoi Mai
2014-12-04 20:42:08 UTC
looking over /sbin/mount.glusterfs I found: ## Place-holder backward compatibility "backupvolfile-server") backupvolfile_server=$value ;; "fetch-attempts") volfile_max_fetch_attempts=$value ;; ## End backward compatibility So i guess in this version of glusterfs-3.5.3-1 its not ready for it yet. Need to check why --volfile-max-fetch-attempts has been marked obsolete, and update the documentation to mention its replacement option. This bug is getting closed because the 3.5 is marked End-Of-Life. There will be no further updates to this version. Please open a new bug against a version that still receives bugfixes if you are still facing this issue in a more current release. |