Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1169701

Summary:	cann't start nfs process when " /usr/sbin/glusterfs -s localhost --volfile-id gluster/nfs.." is running
Product:	[Community] GlusterFS	Reporter:	lily <junli.li>
Component:	nfs	Assignee:	Niels de Vos <ndevos>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	3.4.2	CC:	bugs, gluster-bugs, ndevos
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-12-02 12:32:56 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:

Description lily 2014-12-02 09:02:08 UTC

Description of problem:
On Red Hat Enterprise Linux Server release 6.5 (Santiago), I can not start nfs process when /usr/sbin/glusterfs is running.

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

How reproducible:


Steps to Reproduce:
1./etc/init.d/nfs start
2.lsof -i:2049
3.kill the process who is using port of 2049
4.start nfs process

Actual results:
1.Starting NFS daemon: rpc.nfsd: unable to bind inet TCP socket: errno 98 (Address already in use)
2.# lsof -i:2049
COMMAND     PID USER   FD   TYPE   DEVICE SIZE/OFF NODE NAME
glusterfs 26965 root   12u  IPv4 50016099      0t0  TCP *:nfs (LISTEN)
3.kill sucessfully
4.start sucessfully
Starting NFS daemon:                                       [  OK  ]

Expected results:
1.start sucessfully
3.kill sucessfully
4.start sucessfully
Starting NFS daemon:                                       [  OK  ]



Additional info:

Comment 1 Niels de Vos 2014-12-02 12:32:56 UTC

This is expected behaviour. If you want to use the kernel NFS server or client on a Gluster storage server, make sure to disable the Gluster NFS server:

    # gluster volume set VOLUME nfs.disable true

You should repeat that for all volumes. New volumes can have this option set before they get started.