Bug 987240
| Summary: | NUFA options 'lookup-unhashed' and 'local-volume-name' are not visible through cli | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Harshavardhana <fharshav> |
| Component: | cli | Assignee: | Kaushal <kaushal> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.4.0 | CC: | cww, gluster-bugs, ndevos |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | upstream | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-07-11 18:15:35 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
Harshavardhana
2013-07-23 04:10:20 UTC
In addition to this
Cannot set lookup-unhashed for NUFA
$ gluster volume set gfs cluster.lookup-unhashed on
volume set: success
But volume file doesn't have this option listed, instead this gets appended
to distribute xlator when its re-enabled.
[root@sysrq ~]# grep 'lookup-unhashed' /var/lib/glusterd/vols/gfs/gfs-fuse.vol
[root@sysrq ~]# grep 'lookup-unhashed' /var/lib/glusterd/vols/gfs/gfs-fuse.vol
[root@sysrq ~]# gluster volume info | grep lookup-unhashed
cluster.lookup-unhashed: on
[root@sysrq ~]# grep 'nufa' /var/lib/glusterd/vols/gfs/gfs-fuse.vol
type cluster/nufa
[root@sysrq ~]#
commit 71d69e4331d7abff910e1f013bb7b2cb9d7f630c
Author: Harshavardhana <harsha>
Date: Wed Jul 24 14:49:58 2013 -0700
Add switch and nufa options to 'gluster cli'
Change-Id: Ic3c43291e0e1ead0d89c0436e8d70aa5dee2f543
BUG: 924488
Signed-off-by: Harshavardhana <harsha>
Reviewed-on: http://review.gluster.org/5391
Tested-by: Gluster Build System <jenkins.com>
Reviewed-by: Anand Avati <avati>
*** This bug has been marked as a duplicate of bug 924488 *** |