[Bugs] [Bug 1377198] New: Volume restart couldn' t re-export the volume exported via ganesha.
bugzilla at redhat.com
bugzilla at redhat.com
Mon Sep 19 07:35:40 UTC 2016
https://bugzilla.redhat.com/show_bug.cgi?id=1377198
Bug ID: 1377198
Summary: Volume restart couldn't re-export the volume exported
via ganesha.
Product: GlusterFS
Version: 3.8
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 restart couldn't export the volume exported via ganesha.
Version-Release number of selected component (if applicable):
[root at dhcp43-116 ganesha]# rpm -qa|grep ganesha
glusterfs-ganesha-3.8.3-0.6.git7956718.el7.centos.x86_64
nfs-ganesha-gluster-2.4-0.rc4.el7.centos.x86_64
nfs-ganesha-debuginfo-2.4-0.rc4.el7.centos.x86_64
nfs-ganesha-2.4-0.rc4.el7.centos.x86_64
How reproducible:
Always
Steps to Reproduce:
1.Create and start a volume
[root at dhcp43-116 nfs-ganesha]# gluster volume create testvol replica 2
10.70.43.116:/bricks/brick0/b0 10.70.43.88:/bricks/brick0/b0
10.70.42.47:/bricks/brick0/b0 10.70.42.237:/bricks/brick0/b0
10.70.43.116:/bricks/brick1/b1 10.70.43.88:/bricks/brick1/b1
10.70.42.47:/bricks/brick1/b1 10.70.42.237:/bricks/brick1/b1
10.70.43.116:/bricks/brick2/b2 10.70.43.88:/bricks/brick2/b2
10.70.42.47:/bricks/brick2/b2 10.70.42.237:/bricks/brick2/b2
volume create: testvol: success: please start the volume to access data
[root at dhcp43-116 nfs-ganesha]# gluster vol start testvol
volume start: testvol: success
2. Export the volume
[root at dhcp43-116 ~]# gluster vol set testvol ganesha.enable on
volume set: success
3. Make sure showmount lists the exported volume
[root at dhcp43-116 ~]# cd /var/run/gluster/shared_storage/nfs-ganesha/exports/
[root at dhcp43-116 exports]# ls
export.testvol.conf
[root at dhcp43-116 exports]# showmount -e localhost
Export list for localhost:
/testvol (everyone)
4. stop the volume
[root at dhcp43-116 exports]# gluster vol stop testvol
Stopping volume will make its data inaccessible. Do you want to continue? (y/n)
y
volume stop: testvol: success
5. start the volume again
[root at dhcp43-116 exports]# gluster vol start testvol
volume start: testvol: success
6. Observe that showmount doesn't list the exported volume after start of the
volume
[root at dhcp43-116 exports]# showmount -e localhost
Export list for localhost:
[root at dhcp43-116 exports]# ls
export.testvol.conf
7. Observe that following error messages are seen in ganesha.log
19/09/2016 17:48:14 : epoch 57dbe5c8 : dhcp43-116.lab.eng.blr.redhat.com :
ganesha.nfsd-6039[dbus_heartbeat] gsh_export_addexport :EXPORT :CRIT :Error
while parsing /etc/ganesha/exports/export.testvol.conf
19/09/2016 17:48:14 : epoch 57dbe5c8 : dhcp43-116.lab.eng.blr.redhat.com :
ganesha.nfsd-6039[dbus_heartbeat] dbus_message_entrypoint :DBUS :MAJ :Method
(AddExport) on (org.ganesha.nfsd.exportmgr) failed: name =
(org.freedesktop.DBus.Error.InvalidFileContent), message = (Error while parsing
/etc/ganesha/exports/export.testvol.conf because of (token scan) errors.
Details:
Config File (<unknown file>:0): new file
(/etc/ganesha/exports/export.testvol.conf) open error (No such file or
directory), ignored
Actual results:
Volume restart couldn't export the volume exported via ganesha.
Expected results:
Volume should get exported properly after volume restart.
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list