Bug 807650

Summary:	[bfb6366bd2a6de4cb5322dda72fbc1e6ad1edc41]: replace-brick abort does not cleanup rb_mount stale mount
Product:	[Community] GlusterFS	Reporter:	Rahul C S <rahulcs>
Component:	glusterd	Assignee:	krishnan parthasarathi <kparthas>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	pre-release	CC:	amarts, gluster-bugs, nsathyan, vbellur, vinaraya
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-07-11 07:13:49 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Rahul C S 2012-03-28 12:08:57 UTC

Description of problem:
After  a replace-brick abort is issued after a replace-brick start, df -h output shows the presence of a stale mount whose transport endpoint is not connected.

df output
dagobah:vol            84G  1.3G   83G   2% /data/mounts/mount
df: `/etc/glusterd/vols/vol/rb_mount': Transport endpoint is not connected

Comment 2 Amar Tumballi 2012-04-27 09:10:24 UTC

patch sent @ http://review.gluster.com/3143

Comment 3 Vijay Bellur 2012-05-18 13:06:51 UTC

Pushing this to post 3.3.0

Comment 4 Amar Tumballi 2012-07-11 06:26:31 UTC

waiting on patch review/acceptance

Comment 5 krishnan parthasarathi 2012-07-11 07:13:49 UTC


*** This bug has been marked as a duplicate of bug 806890 ***