Bug 807650 - [bfb6366bd2a6de4cb5322dda72fbc1e6ad1edc41]: replace-brick abort does not cleanup rb_mount stale mount
Summary: [bfb6366bd2a6de4cb5322dda72fbc1e6ad1edc41]: replace-brick abort does not clea...
Keywords:
Status: CLOSED DUPLICATE of bug 806890
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterd
Version: pre-release
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: krishnan parthasarathi
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-28 12:08 UTC by Rahul C S
Modified: 2015-11-03 23:04 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-07-11 07:13:49 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

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 ***


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