[Bugs] [Bug 1365900] New: Volume gets mounted with ganesha v4 mount even when it is unexported.

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1365900

            Bug ID: 1365900
           Summary: Volume gets mounted with ganesha v4 mount even when it
                    is unexported.
           Product: GlusterFS
           Version: 3.8.1
         Component: ganesha-nfs
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: sraj at redhat.com
                CC: bugs at gluster.org, jthottan at redhat.com,
                    kkeithle at redhat.com, ndevos at redhat.com,
                    skoduri at redhat.com, storage-qa-internal at redhat.com



Description of problem:

Volume gets mounted with v4 even when it is unexported.

Version-Release number of selected component (if applicable):

[root at dhcp43-133 ~]# rpm -qa|grep glusterfs
glusterfs-libs-3.8.1-0.4.git56fcf39.el7rhgs.x86_64
glusterfs-fuse-3.8.1-0.4.git56fcf39.el7rhgs.x86_64
glusterfs-3.8.1-0.4.git56fcf39.el7rhgs.x86_64
glusterfs-api-3.8.1-0.4.git56fcf39.el7rhgs.x86_64
glusterfs-cli-3.8.1-0.4.git56fcf39.el7rhgs.x86_64
glusterfs-ganesha-3.8.1-0.4.git56fcf39.el7rhgs.x86_64
glusterfs-client-xlators-3.8.1-0.4.git56fcf39.el7rhgs.x86_64
glusterfs-server-3.8.1-0.4.git56fcf39.el7rhgs.x86_64
glusterfs-geo-replication-3.8.1-0.4.git56fcf39.el7rhgs.x86_64

[root at dhcp43-133 ~]# rpm -qa|grep ganesha
nfs-ganesha-gluster-2.4-0.dev.26.el7rhgs.x86_64
nfs-ganesha-2.4-0.dev.26.el7rhgs.x86_64
glusterfs-ganesha-3.8.1-0.4.git56fcf39.el7rhgs.x86_64


How reproducible:

Always

Steps to Reproduce:
1.Create a ganesha cluster and create a volume.
2.Enable ganesha on the volume and mount it on a client.

[root at dhcp43-133 ~]# gluster vol set testvolume ganesha.enable on
volume set: success

10.70.40.192:/testvolume on /mnt/nfs1 type nfs4
(rw,relatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=10.70.46.206,local_lock=none,addr=10.70.40.192)

3.Mount is successful as expected.
4.Unmount the volume and unexport it.

[root at dhcp43-133 ~]# gluster vol set testvolume ganesha.enable off
volume set: success

[root at dhcp43-133 ~]# showmount -e localhost
Export list for localhost:

5.Try mounting the volume back with v4 and observe that it gets mounted and
doesn't give any error

[root at dhcp46-206 ~]# mount -t nfs -o vers=4 10.70.40.192:/testvolume /mnt/nfs1
[root at dhcp46-206 ~]# 

10.70.40.192://testvolume on /mnt/nfs1 type nfs4
(rw,relatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=10.70.46.206,local_lock=none,addr=10.70.40.192)

>> Trying the same with v3 mount gives access denied error as below:

[root at dhcp46-206 ~]# mount -t nfs -o vers=3 10.70.40.192:/testvolume /mnt/nfs2
mount.nfs: access denied by server while mounting 10.70.40.192:/testvolume

6. Creating dir or files inside the mount point gives "read-only filesystem"

[root at dhcp46-206 ~]# cd /mnt/nfs1
[root at dhcp46-206 nfs1]# mkdir dir
mkdir: cannot create directory ‘dir’: Read-only file system
[root at dhcp46-206 nfs1]# touch file
touch: cannot touch ‘file’: Read-only file system


Actual results:

Volume gets mounted with ganesha v4 mount even when it is unexported.

Expected results:

Mounting an unexported volume with v4 ganesha mount should give proper error
message and should not get mounted.

Additional info:

Will attach the packet trace

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.