Bug 1054678
| Summary: | nfs-ganesha: script does not disable glusterfs-nfs in case gluterfs-nfs is already not running on the present node of the rhs cluster | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Saurabh <saujain> |
| Component: | nfs-ganesha | Assignee: | Anand Subramanian <ansubram> |
| Status: | CLOSED NOTABUG | QA Contact: | Saurabh <saujain> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 2.1 | CC: | ansubram, grajaiya, mmadhusu, mzywusko, nlevinki, sharne, skoduri, smohan, vagarwal |
| Target Milestone: | --- | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | nfs-ganesha-2.0.0.2-4.el6rhs | Doc Type: | Known Issue |
| Doc Text: |
Before starting nfs-ganesha, gluster-nfs should be disabled by setting nfs.disable option to ON. The rhs-nfs_ganesha.sh script checks only if gluster-nfs process is running on the host and if gluster-nfs is down for some reason , it does not set the nfs.disable option to ON. This might result in two issues:
1.nfs-ganesha starts on the host specified as input to the rhs-nfs_ganesha.sh script. But, gluster-nfs would still be active on the nodes other than the node running nfs-ganesha if the volume has bricks across multiple nodes.
Workaround:
Set nfs.disable option to ON by using the following command on any of the nodes containing the RHS volume in question,
gluster volume set [volume-name] nfs.disable ON
2.nfs-ganesha fails to start and the script displays the message, "NFS ports still appear to be in use, please try again."
Workaround:
Follow the listed steps to troubleshoot this issue,
a.Check the log file to see if the failure is due to ports still being in use.
b.Check rpcinfo -p to see if NFS ports are still in use.
c.Remove the independent entries for nfs,mountd,nlockmgr and nfs_acl using rpcinfo -d command.
d.Execute the following command,
gluster volume set [volume-name] nfs.disable ON
e.Start NFS-ganesha using the script.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-07-07 12:24:34 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1035040 | ||
|
Description
Saurabh
2014-01-17 09:23:40 UTC
The issue is fixed in the last rhs nfs-ganesha build (nfs-ganesha-2.0.0.2-4.el6rhs). Please try the above bld and verify the fix. (In reply to Meghana from comment #2) > The issue is fixed in the last rhs nfs-ganesha build > (nfs-ganesha-2.0.0.2-4.el6rhs). Please try the above bld and verify the fix. It would be awesome if you can point out the patch URL for this fix. - shanks well, seems the issue is still not fixed, the other nodes are still having glusterfs-nfs running. [root@rhsauto004 ~]# ps -eaf | grep nfs root 3574 1 6 14:44 ? 00:00:14 /usr/sbin/glusterfs -s localhost --volfile-id gluster/nfs -p /var/lib/glusterd/nfs/run/nfs.pid -l /var/log/glusterfs/nfs.log -S /var/run/c66ee1ad00917f211581417cb71f0e9b.socket root 3666 3122 0 14:48 pts/0 00:00:00 grep nfs [root@rhsauto004 ~]# kill -9 3574 [root@rhsauto004 ~]# [root@rhsauto004 ~]# [root@rhsauto004 ~]# time bash /usr/lib/glusterfs/.unsupported/rhs-nfs_ganesha.sh -l /root/ganeshalog/1.log -v dist-rep -i 10.70.36.234 -f /usr/lib/glusterfs/.unsupported/nfs-ganesha.conf -c start -n 3 NFS-ganesha server started. ============Volume exports============ Export list for 10.70.36.234: /dist-rep *,* ====================================== real 0m6.769s user 0m0.478s sys 0m0.305s [root@rhsauto004 ~]# gluster volume info Volume Name: dist-rep Type: Distributed-Replicate Volume ID: 414a3d23-9e22-436e-a527-984a003657a8 Status: Started Number of Bricks: 6 x 2 = 12 Transport-type: tcp Bricks: Brick1: rhsauto004.lab.eng.blr.redhat.com:/rhs/brick1/d1r1 Brick2: rhsauto012.lab.eng.blr.redhat.com:/rhs/brick1/d1r2 Brick3: rhsauto015.lab.eng.blr.redhat.com:/rhs/brick1/d2r1 Brick4: rhsauto016.lab.eng.blr.redhat.com:/rhs/brick1/d2r2 Brick5: rhsauto004.lab.eng.blr.redhat.com:/rhs/brick1/d3r1 Brick6: rhsauto012.lab.eng.blr.redhat.com:/rhs/brick1/d3r2 Brick7: rhsauto015.lab.eng.blr.redhat.com:/rhs/brick1/d4r1 Brick8: rhsauto016.lab.eng.blr.redhat.com:/rhs/brick1/d4r2 Brick9: rhsauto004.lab.eng.blr.redhat.com:/rhs/brick1/d5r1 Brick10: rhsauto012.lab.eng.blr.redhat.com:/rhs/brick1/d5r2 Brick11: rhsauto015.lab.eng.blr.redhat.com:/rhs/brick1/d6r1 Brick12: rhsauto016.lab.eng.blr.redhat.com:/rhs/brick1/d6r2 Options Reconfigured: nfs.disable: off Please add doc text for this known issue. Please review the edited doc text and sign off. This is no longer an issue and importantly not applicable to Denali RHS 3.0 Ganesha. The script rhs_nfs-ganehsa.sh is deprecated. |