I get a timeout when trying to force start the volume from serv3, but I can stop the volume ...
Isn't the error linked to "0-glusterfs: failed to submit rpc-request" ? (from the log i send in the first place)
Merwan
De : Atin Mukherjee <amukherj@xxxxxxxxxx>
Envoyé : dimanche 4 juin 2017 15:31:34 À : Merwan Ouddane Cc : gluster-users Objet : Re: Adding a new replica to the cluster Apologies for the delay!
This looks like in serv3 the newly added brick failed to come up. You'd have to look at the same brick log file on serv3 to see what was the reason. As a workaround, does gluster v start <volname> force bring up this brick now? As far as glusterd configuration
data is concerned, everything seems fine, no inconsistency.>From the logs: [2017-05-31 13:06:35.839780] E [MSGID: 106005] [glusterd-utils.c:4877:glusterd_brick_start] 0-management: Unable to start brick 156.125.102.103:/data/br0/vm0 [2017-05-31 13:06:35.839869] E [MSGID: 106074] [glusterd-brick-ops.c:2493:glusterd_op_add_brick] 0-glusterd: Unable to add bricks On Wed, May 31, 2017 at 6:53 PM, Merwan Ouddane
<merwan19@xxxxxxx> wrote:
|
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-users