On Sun, May 7, 2017 at 10:06 PM, Tahereh Fattahi
wrote:
> Thanks a lot
> For gv2, I have two bricks, second peer is in peer list from node I want
> to delete.
> But there are other nodes for other volumes, not gv2, that are in peer
> list but are not connected. How can I
Thanks a lot
For gv2, I have two bricks, second peer is in peer list from node I want to
delete.
But there are other nodes for other volumes, not gv2, that are in peer list
but are not connected. How can I remove these nodes from peer list?
On Sun, May 7, 2017 at 9:00 PM, Atin Mukherjee
Can you please paste the output of 'gluster peer status' from the node
where volume delete CLI failed? Also during this failure did you find out
which node(s) are down (as per the command) from the glusterd logs?
On Sun, 7 May 2017 at 21:53, Tahereh Fattahi wrote:
> Hi
>
Hi
When I want to delete my test volume I get error:
volume delete: gv2: failed: Some of the peers are down
But all nodes are up (service glsterd, connetion, ip , .. all things are ok
) and before stop or after start (after trying for deletion) work correctly.
So how can I delete the volume?
Thanks Ravi, I now manually created the missing "dirty" directory and do not
get any error messages in the gluster self-heal daemon log file.
There is still one warning message which I see often in my brick log file and
would be thankful if you could let me know what this means or what the