Hi all,
we have a problem with a distributed dispersed volume (GlusterFS 3.12). We have
files that lost their permissions or gained sticky bits. The files
themselves seem to be okay.
It looks like this:
# ls -lah $file1
-- 1 www-data www-data 45M Jan 12 07:01 $file1
# ls -lah $file2
Found it.
Filesystem on 1 of the nodes was corrupt. Removing that brick, fixing the
filesytem and adding the brick again solved the problem.
From: Graaf, Max de
Sent: Friday, January 25, 2019 1:32:41 PM
To: Gluster-users
Subject: Brick stays offline after
We have 2 nodes running CentOS 7.3. Running just fine with glusterfs
4.1.6-1.el7. This morning update both to 4.1.7-1.el7 and the only brick
configured stays offline.
gluster peer status show no problems:
Number of Peers: 1
Hostname: 10.159.241.35
Uuid: 7453dbec-44fb-4e57-9471-6e653d287d3b
We have 2 nodes running CentOS 7.3. Running just fine with glusterfs
4.1.6-1.el7. This morning update both to 4.1.7-1.el7 and the only brick
configured stays offline.
gluster peer status show no problems:
Number of Peers: 1
Hostname: 10.159.241.35
Uuid: 7453dbec-44fb-4e57-9471-6e653d287d3b
Amudhan,
So here's the issue:
In node3, 'cat /var/lib/glusterd/peers/* ' doesn't show up node2's details
and that's why glusterd wasn't able to resolve the brick(s) hosted on node2.
Can you please pick up 0083ec0c-40bf-472a-a128-458924e56c96 file from
/var/lib/glusterd/peers/ from node 4 and
Hi,
I'm just going through the concepts of quorum and split-brains with a
cluster in general, and trying to understand GlusterFS quorums again which
I previously found difficult to accurately understand.
When we talk about server quorums, what I understand is that the concept is
similar to
