Bug 1467057
| Summary: | NFS-Ganesha doesn't work on Gluster bricks with name that ends with "w0" | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Jan <jan.h.zak> |
| Component: | ganesha-nfs | Assignee: | bugs <bugs> |
| Status: | CLOSED EOL | QA Contact: | |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.10 | CC: | bugs, jan.h.zak, kkeithle |
| Target Milestone: | --- | Keywords: | Triaged |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-06-20 18:29:49 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
Jan
2017-07-02 10:24:44 UTC
Tested with Gluster version 3.10.3. Issue remains. please attach the /etc/ganesha/ganesha.conf file.
You have to configure an EXPORT block in the ganesha.conf file. Ganesha doesn't do anything with gluster bricks. The EXPORT block tells the FSAL_GLUSTER which gluster volume to export.
E.g.:
gluster volume create mynfsvol $host:/$path-to-brick
gluster volume start mynfsvol
then /etc/ganesha/ganesha.conf has an export block for the gluster volume:
...
FSAL {
Name = GLUSTER;
Hostname = localhost;
Volume = mynfsvol;
}
...
Then start nfs-ganesha
ganesha.conf contains following lines %include "/var/run/gluster/shared_storage/nfs-ganesha/exports/export.bri3.conf" this is content is autogenerated when I enable Ganesha on a specified brick using command: sudo gluster vol set "bri3" ganesha.enable on This bug reported is against a version of Gluster that is no longer maintained (or has been EOL'd). See https://www.gluster.org/release-schedule/ for the versions currently maintained. As a result this bug is being closed. If the bug persists on a maintained version of gluster or against the mainline gluster repository, request that it be reopened and the Version field be marked appropriately. |