[Bugs] [Bug 1227656] Glusted dies when adding new brick to a distributed volume and converting to replicated volume

[bugzilla at redhat.com]

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

Gaurav Kumar Garg <ggarg at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
              Flags|                            |needinfo?(redhat.bugs at point
                   |                            |b.co.uk)



--- Comment #9 from Gaurav Kumar Garg <ggarg at redhat.com> ---
Hi Richard,

Steps  that you have mentioned in attach file after executing that steps
glusterd is not crashing. Only mount failure is coming as you mentioned in the
list of steps. So why mount failure is coming because you have executed "
service glusterfsd stop " command on both node after executing that command you
have executed "service glusterd stop" on both node. then you have started
glusterd on one node. 

So this is expected behaviour (mount failure) because your brick process
(glusterfsd) didn't come back online. so while mounting the volume it check
whether brick is online or not if it is not then it will show mount failure.
you can also check in your volume status that brick is not online.

to solve mount failure problem you need to re-start volume again either by
stopping it and starting it or by executing "gluster volume start <VOLNAME>
force".


Then main things is about glusterd crash problem. so as far as my concern
glusterd should not crash by performing these steps. are your executing any
other command or previously have you executed any rebalance/remove-brick
command ????

Could you paste output of "gluster voluem status" here ???

-- 
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=wXOlJux50s&a=cc_unsubscribe