+++ This bug was initially created as a clone of Bug #1401806 +++ Description of problem: After doing start and stop on volume having ganesha enable,volume is failed to export again Version-Release number of selected component (if applicable): # rpm -qa | grep ganesha nfs-ganesha-2.4.1-2.el7rhgs.x86_64 glusterfs-ganesha-3.8.4-7.el7rhgs.x86_64 nfs-ganesha-gluster-2.4.1-2.el7rhgs.x86_64 How reproducible: Steps to Reproduce: 1.Create 4 node ganesha cluster on 8 node gluster and enable ganesha on it 2.Create a volume and enable ganesha 3.Check showmount -e.Volume is exported 4.Stop the volume 5.Again start the same volunme Actual results: on restart of the volume,volume failed to get exported again. Observed the following messages in ganesha.log 06/12/2016 12:07:24 : epoch 08220000 : dhcp47-3.lab.eng.blr.redhat.com : ganesha.nfsd-10937[dbus_heartbeat] glusterfs_create_export :FSAL :EVENT :Volume ganeshaVol1 exported at : '/' 06/12/2016 12:09:12 : epoch 08220000 : dhcp47-3.lab.eng.blr.redhat.com : ganesha.nfsd-10937[dbus_heartbeat] gsh_export_addexport :EXPORT :CRIT :Error finding exports: EXPORT(Export_Id=) because No such file or directory 06/12/2016 12:09:12 : epoch 08220000 : dhcp47-3.lab.eng.blr.redhat.com : ganesha.nfsd-10937[dbus_heartbeat] dbus_message_entrypoint :DBUS :MAJ :Method (AddExport) on (org.ganesha.nfsd.exportmgr) failed: name = (org.freedesktop.DBus.Error.InvalidArgs), message = (Error finding exports: EXPORT(Export_Id=) because No such file or directory) Expected results: Volume should be exported successfully on restart of the volume Additional info:
REVIEW: http://review.gluster.org/16037 (ganesha/scripts : find export id for already exported volume in S31ganesha-start.sh) posted (#1) for review on master by jiffin tony Thottan (jthottan)
COMMIT: http://review.gluster.org/16037 committed in master by Kaleb KEITHLEY (kkeithle) ------ commit 58a58e706da73ee751b7cd98c23e6675667fefdb Author: Jiffin Tony Thottan <jthottan> Date: Tue Dec 6 13:38:21 2016 +0530 ganesha/scripts : find export id for already exported volume in S31ganesha-start.sh Change-Id: Iada90ed215966d3f526fa20aa5359b67f25a6944 BUG: 1401822 Signed-off-by: Jiffin Tony Thottan <jthottan> Reviewed-on: http://review.gluster.org/16037 Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: soumya k <skoduri> Reviewed-by: Kaleb KEITHLEY <kkeithle>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.10.0, please open a new bug report. glusterfs-3.10.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://lists.gluster.org/pipermail/gluster-users/2017-February/030119.html [2] https://www.gluster.org/pipermail/gluster-users/