Bug 1114574
| Summary: | nfs-ganesha: rpcinfo -p displays running nfs info, even though nfs-ganesha process is stopped | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Saurabh <saujain> |
| Component: | nfs-ganesha | Assignee: | Satish Mohan <smohan> |
| Status: | CLOSED DUPLICATE | QA Contact: | storage-qa-internal <storage-qa-internal> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rhgs-3.0 | CC: | asriram, jthottan, mzywusko, nlevinki, nsathyan, skoduri, vagarwal |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Known Issue | |
| Doc Text: |
Executing "rpcinfo -p" command after stopping nfs-ganesha displays nfs related programs.
Workaround (if any): Use "rpcinfo -d" on each of the nfs related services listed in "rpcifnfo -p" and start the Red Hat Storage volume forcefully using the following command "gluster vol start <volume> force "
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-01-27 07:15:40 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: | 1087818 | ||
This issue is not always seen in our setup. The workaround is to use "rpcinfo -d" to cleanup the ports and is also part of RHS3.0 Documentation for NFS-Ganesha. We will check with the QA setup. Since there is a workaround, we will fix this issue in the next release. Please review and sign-off edited doc text. Meghana reviewed the text during online review meeting. Hence removing need_info. *** This bug has been marked as a duplicate of bug 1227169 *** |
Description of problem: for stopping nfs-ganesha, we use the command gluster volume set <dist-rep> nfs-ganesha.enable off This stops the nfs-ganesha process, still the rpcinfo -p displays the information about nfs. Hence, even if nfs-ganehsa is stopped from glusterfs point of view, the glusterfs-nfs could not be started. Version-Release number of selected component (if applicable): glusterfs-3.6.0.22-1.el6rhs.x86_64 nfs-ganesha-2.1.0.2-4.el6rhs.x86_64 How reproducible: always Actual results: [root@nfs1 ~]# rpcinfo -p program vers proto port service 100000 4 tcp 111 portmapper 100000 3 tcp 111 portmapper 100000 2 tcp 111 portmapper 100000 4 udp 111 portmapper 100000 3 udp 111 portmapper 100000 2 udp 111 portmapper 100024 1 udp 42790 status 100024 1 tcp 59211 status 100003 3 udp 2049 nfs 100003 3 tcp 2049 nfs 100003 4 udp 2049 nfs 100003 4 tcp 2049 nfs 100005 1 udp 49710 mountd 100005 1 tcp 33435 mountd 100005 3 udp 49710 mountd 100005 3 tcp 33435 mountd 100021 4 udp 35307 nlockmgr 100021 4 tcp 34680 nlockmgr 100011 1 udp 875 rquotad 100011 1 tcp 875 rquotad 100011 2 udp 875 rquotad 100011 2 tcp 875 rquotad [root@nfs1 ~]# ps -eaf | grep ganesha root 11829 1906 0 06:12 pts/0 00:00:00 grep ganesha Expected results: rpcinfo should be clear of the nfs information once nfs-ganesha is stopped. Additional info: