Bug 763623 (GLUSTER-1891) - wrong message during volume stop with removed-detached brick
Summary: wrong message during volume stop with removed-detached brick
Keywords:
Status: CLOSED DUPLICATE of bug 763517
Alias: GLUSTER-1891
Product: GlusterFS
Classification: Community
Component: cli
Version: 3.1-alpha
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Pranith Kumar K
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-11 06:33 UTC by Lakshmipathi G
Modified: 2015-12-01 16:45 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: RTP
Mount Type: All
Documentation: ---
CRM:
Verified Versions:

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

Description Lakshmipathi G 2010-10-11 06:33:18 UTC 
remove a brick from 3-dht cluster and did a peer detach on removed-brick.

On the removed-brick volume stop says "successful" - though it didn't stop the volume. 

removed-birck# gluster volume stop dht44
Stopping volume will make its data inaccessible. Do you want to Continue? (y/n) y
Stopping volume dht44 has been successful
Comment 1 Pranith Kumar K 2010-10-11 10:38:18 UTC 
This bug should not be observed once the bug 763517 is fixed. So making this a dup.

*** This bug has been marked as a duplicate of bug 1785 ***
Note You need to log in before you can comment on or make changes to this bug.