Bug 763473 (GLUSTER-1741)
Summary: | gluster volume stop after one process crashed. | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Lakshmipathi G <lakshmipathi> |
Component: | cli | Assignee: | Pranith Kumar K <pkarampu> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 3.1-alpha | CC: | gluster-bugs, pkarampu, vijay |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | Type: | --- | |
Regression: | RTP | Mount Type: | All |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Lakshmipathi G
2010-09-29 09:39:27 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? If 'gluster volume stop <VOLNAME> force' works, I will be closing this bug. PATCH: http://patches.gluster.com/patch/5149 in master (mgmt/glusterd: handle glusterfs crashes for start/stop of bricks) If some of the gluterfs processes crash then we can use "gluster volume start/stop force" to take the appropriate action. |