[Bugs] [Bug 1624444] Fail volume stop operation in case brick detach request fails

bugzilla at redhat.com bugzilla at redhat.com
Sun Oct 14 10:15:00 UTC 2018


https://bugzilla.redhat.com/show_bug.cgi?id=1624444

Rajesh Madaka <rmadaka at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ON_QA                       |VERIFIED
         QA Contact|bmekala at redhat.com          |rmadaka at redhat.com



--- Comment #11 from Rajesh Madaka <rmadaka at redhat.com> ---
Followed below steps to verify this bug

1. Having 3 node(n1, n2, n3) cluster
2. Brick multiplex enabled
3. Created 5 replica (1x3) volumes
4. kill the brick using kill -9 <brick PID> from first node n1
4. Then take the glusterd process to gdb using "gdb -p <glusterd PID> from node
n1
5. Put a break point on function glusterd_volume_stop_glusterfs using "b
glusterd_volume_stop_glusterfs"
6. Then open one more terminal for same node n1 and then try to stop the volume
7. Then set brickinfo->status = GF_BRICK_STARTED using "p brickinfo->status =
GF_BRICK_STARTED"
8.Volume stop is failing with below error.
9. volume stop: rep_test5: failed: Commit failed on localhost. Please check the
log file for more details.


build Version:
glusterfs-3.12.2-22

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=3mRR9k8iLk&a=cc_unsubscribe


More information about the Bugs mailing list