Bug 763248 – Remove brick successful but nfs still running on removed brick

This service will be undergoing maintenance at 00:00 UTC, 2016-09-28. It is expected to last about 1 hours

Bug 763248 - (GLUSTER-1516) Remove brick successful but nfs still running on removed brick

Summary:	Remove brick successful but nfs still running on removed brick

Status:	CLOSED NOTABUG

Aliases:	GLUSTER-1516

Product:	GlusterFS
Classification:	Community
Component:	nfs (Show other bugs)
Sub Component:
Version:	3.1-alpha
Hardware:	All Linux

Priority	low Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Shehjar Tikoo
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2010-09-03 05:36 EDT by Lakshmipathi G
Modified:	2015-12-01 11:45 EST (History)
CC List:	2 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:
Type:	---
Regression:	RTP
Mount Type:	nfs
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Pranith Kumar K 2010-09-03 02:41:21 EDT

Only when all the volumes are stopped. The nfs process will be stopped.

Comment 1 Lakshmipathi G 2010-09-03 05:36:36 EDT

testing with 3.1.0qa14 + 4 dht setup,removing a brick using
"gluster volume remove-brick" removes the brick(brick4)  as expected.
but nfs is still running there.

server4#ps ax|grep glust
27072 ?        Ssl    0:00 glusterd
27628 ?        Ssl    0:00 /usr/local/sbin/glusterfs -f /etc/glusterd/nfs/nfs-server.vol -p /etc/glusterd/nfs/run/nfs.pid
27634 pts/0    R+     0:00 grep glust

server4#showmount -e  
Export list for domU-12-31-39-10-6D-E2:
/dht4 *


server1#gluster volume info

Volume Name: dht4
Type: None
Status: Started
Number of Bricks: 3
Bricks:
Brick1: 10.192.134.144:/mnt/d1
Brick2: 10.214.231.112:/mnt/d1
Brick3: 10.192.141.187:/mnt/d1

Note You need to log in before you can comment on or make changes to this bug.