[Gluster-devel] wrong volume status report

Atin Mukherjee amukherj at redhat.com
Mon Sep 7 17:37:06 UTC 2015

On 09/07/2015 05:11 PM, Emmanuel Dreyfus wrote:
> Atin Mukherjee <amukherj at redhat.com> wrote:
>> GlusterD doesn't report the status of bricks if find that another
>> transaction on the same volume is in progress on the cluster. 
> That the point: the bricks suddently disaprear from glusterfs volume
> status output. That does not obviously tell this is a transaction in
> progress problem.
This could only happen when glusterd instance of that brick is down,
otherwise the command itself would fail saying either a locking failure
or another transaction is in progress and it won't output anything else.

More information about the Gluster-devel mailing list