Red Hat Bugzilla – Bug 1467057
NFS-Ganesha doesn't work on Gluster bricks with name that ends with "w0"
Last modified: 2017-07-03 15:01:30 EDT
Description of problem:
If you enable Ganesha on Gluster brick with name for example "w0" or "sw0" then it doesn't work. There is something wrong with string "w0" at the end of brick name.
Version-Release number of selected component (if applicable):
and also tested with:
yum list installed | egrep 'gluster|ganesha'
centos-release-gluster310.noarch 1.0-1.el7.centos @extras
Install and configure 3x node Gluster, with following bricks:
Name: w0, Path: /st/w0/0/ (w0 is mounted XFS filesystem)
Name: sw0, Path: /st/sw0/0/ (sw0 is mounted XFS filesystem)
and some other just for test
Create bricks: w0 and sw0
Check exports directory:
ls -l /var/run/gluster/shared_storage/nfs-ganesha/exports/
export.w0.conf - does NOT exist
export.sw0.conf - exists but it doesn't work after reboot
Start NFS-Ganesha service and check:
showmount -e localhost
If you have other bricks that they will show but "w0" and "sw0" will not show - it doesn't work.
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.
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:
Name = GLUSTER;
Hostname = localhost;
Volume = mynfsvol;
Then start nfs-ganesha
ganesha.conf contains following lines
this is content is autogenerated when I enable Ganesha on a specified brick using command:
sudo gluster vol set "bri3" ganesha.enable on