Bug 763473 (GLUSTER-1741) - gluster volume stop after one process crashed.
Summary: gluster volume stop after one process crashed.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-1741
Product: GlusterFS
Classification: Community
Component: cli
Version: 3.1-alpha
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Pranith Kumar K
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-29 09:39 UTC by Lakshmipathi G
Modified: 2015-12-01 16:45 UTC (History)
3 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:
Embargoed:

Attachments (Terms of Use)

Description Lakshmipathi G 2010-09-29 09:39:27 UTC 
if one glusterfs process already crashed-gluster volume stop won't stop the remaining glfs processes

#gluster volume stop testqa35
Stopping volume will make its data inaccessible. Do you want to Continue? (y/n) y
Stopping volume testqa35 has been unsuccessful
Comment 1 Vijay Bellur 2010-09-30 01:24:57 UTC 
(In reply to comment #0)
> if one glusterfs process already crashed-gluster volume stop won't stop the
> remaining glfs processes
> 
> #gluster volume stop testqa35
> Stopping volume will make its data inaccessible. Do you want to Continue? (y/n)
> y
> Stopping volume testqa35 has been unsuccessful

Can you please try with gluster volume stop force?
Comment 2 Amar Tumballi 2010-09-30 06:09:56 UTC 
If 'gluster volume stop <VOLNAME> force' works, I will be closing this bug.
Comment 3 Vijay Bellur 2010-10-01 13:33:49 UTC 
PATCH: http://patches.gluster.com/patch/5149 in master (mgmt/glusterd: handle glusterfs crashes for start/stop of bricks)
Comment 4 Pranith Kumar K 2010-10-01 23:44:32 UTC 
If some of the gluterfs processes crash then we can use "gluster volume start/stop force" to take the appropriate action.
Note You need to log in before you can comment on or make changes to this bug.