<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
hi,<br>
<br>
I have a four peers gluster and one is failing, well, kind of..<br>
If on a working peer I do:<br>
<br>
$ gluster volume add-brick QEMU-VMs replica 3
10.5.6.49:/__.aLocalStorages/0/0-GLUSTERs/0GLUSTER-QEMU-VMs force<br>
volume add-brick: failed: Commit failed on whale.priv Please check
log file for details.<br>
<br>
but:<br>
<br>
$ gluster vol info QEMU-VMs<br>
Volume Name: QEMU-VMs<br>
Type: Replicate<br>
Volume ID: 8709782a-daa5-4434-a816-c4e0aef8fef2<br>
Status: Started<br>
Snapshot Count: 0<br>
Number of Bricks: 1 x 3 = 3<br>
Transport-type: tcp<br>
Bricks:<br>
Brick1: 10.5.6.100:/__.aLocalStorages/1/0-GLUSTERs/1GLUSTER-QEMU-VMs<br>
Brick2: 10.5.6.17:/__.aLocalStorages/1/0-GLUSTERs/QEMU-VMs<br>
Brick3:
10.5.6.49:/__.aLocalStorages/0/0-GLUSTERs/0GLUSTER-QEMU-VMs #
<= so it is here, also this command on that failing peers reports
correctly.<br>
<br>
Interestingly,<br>
<br>
$ gluster volume remove-brick<br>
<br>
removes no errors, but this change is not propagated to the failing
peer. Vol info still reports its brick is part of the volume.<br>
<br>
And the failing completely part: every command on failing peer
reports:<br>
<br>
$ gluster volume remove-brick QEMU-VMs replica 2
10.5.6.49:/__.aLocalStorages/0/0-GLUSTERs/0GLUSTER-QEMU-VMs force<br>
Removing brick(s) can result in data loss. Do you want to Continue?
(y/n) y<br>
volume remove-brick commit force: failed: Commit failed on
10.5.6.32. Please check log file for details.<br>
Commit failed on rider.priv Please check log file for details.<br>
Commit failed on 10.5.6.17. Please check log file for details.<br>
<br>
I've been watching logs but honestly, don't know which one(s) I
should paste in here.<br>
b.w.<br>
L.<br>
<br>
</body>
</html>