Bug 1467057 - NFS-Ganesha doesn't work on Gluster bricks with name that ends with "w0"
Summary: NFS-Ganesha doesn't work on Gluster bricks with name that ends with "w0"
Keywords:
Status: CLOSED EOL
Alias: None
Product: GlusterFS
Classification: Community
Component: ganesha-nfs
Version: 3.10
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-02 10:24 UTC by Jan
Modified: 2018-06-20 18:29 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-06-20 18:29:49 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Jan 2017-07-02 10:24:44 UTC
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):
CentOS
uname -r
3.10.0-514.21.2.el7.x86_64
and also tested with:
3.10.0-514.26.1.el7.x86_64

yum list installed | egrep 'gluster|ganesha'
centos-release-gluster310.noarch     1.0-1.el7.centos         @extras

glusterfs.x86_64                     3.10.2-1.el7
@centos-gluster310
glusterfs-api.x86_64                 3.10.2-1.el7
@centos-gluster310
glusterfs-cli.x86_64                 3.10.2-1.el7
@centos-gluster310
glusterfs-client-xlators.x86_64      3.10.2-1.el7
@centos-gluster310
glusterfs-fuse.x86_64                3.10.2-1.el7
@centos-gluster310
glusterfs-ganesha.x86_64             3.10.2-1.el7
@centos-gluster310
glusterfs-libs.x86_64                3.10.2-1.el7
@centos-gluster310
glusterfs-server.x86_64              3.10.2-1.el7
@centos-gluster310
libntirpc.x86_64                     1.4.3-1.el7
 @centos-gluster310
nfs-ganesha.x86_64                   2.4.5-1.el7
 @centos-gluster310
nfs-ganesha-gluster.x86_64           2.4.5-1.el7
 @centos-gluster310
userspace-rcu.x86_64                 0.7.16-3.el7
@centos-gluster310

How reproducible:
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

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.

Comment 1 Jan 2017-07-03 09:12:21 UTC
Tested with Gluster version 3.10.3. Issue remains.

Comment 2 Kaleb KEITHLEY 2017-07-03 11:37:11 UTC
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

Comment 3 Jan 2017-07-03 19:01:30 UTC
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

Comment 4 Shyamsundar 2018-06-20 18:29:49 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.