On 05/23/2016 08:21 PM, Kevin Lemonnier wrote:
Looks like it crashed, if I do a /etc/init.d/gluster-server stop on the third
node and
ps aux | grep gluster after that there is still a lot of processes listed.
Should I kill everything ?
When you create a file from the mount, does it get replicated to the
third brick?
In any case you can kill all brick processes of a node with `pkill
glusterfsd`. Then if you restart glusterd on the same node with `service
glusterd restart`, it should bring back all brick processes. You might
want to just try restarting glusterd without actually killing the bricks
first.
On Mon, May 23, 2016 at 04:31:28PM +0200, Kevin Lemonnier wrote:
Hi,
We have in production 3 nodes for a volume storing VM files on 3.7.6,
suddenly the third node isn't seen by the others. For exemple in the heal
infos :
Status: Brick is not connected
The network seems to be working fine, the 3 nodes are in cluster and can ping
each other. gluster volume status lists the 3 bricks and I restarted the daemon
on the third node to be sure, still the same result.
The brick is stored on xfs on /mnt/vg1-storage and all the files seems to be
there,
it's not read only or anything.
Where can I check ?
Thanks
--
Kevin Lemonnier
PGP Fingerprint : 89A5 2283 04A0 E6E9 0111
_______________________________________________
Gluster-users mailing list
[email protected]
http://www.gluster.org/mailman/listinfo/gluster-users
_______________________________________________
Gluster-users mailing list
[email protected]
http://www.gluster.org/mailman/listinfo/gluster-users
_______________________________________________
Gluster-users mailing list
[email protected]
http://www.gluster.org/mailman/listinfo/gluster-users
