Hi,
Isn't the trusted.afr.dirty attribute missing from Brick 2? Shouldn't it be
increased
and decreased, but never removed?
Could that be the reason why GlusterFS is confused?
What could be the reason for gfid mismatches?
Regards
Andreas
Brick1 getfattr -d -m . -e hex config.ior
# file:
On 08/13/2015 07:42 PM, Andreas Hollaus wrote:
Isn't the trusted.afr.dirty attribute missing from Brick 2? Shouldn't
it be increased and decreased, but never removed?
If one brick of a replica 2 setup is down, and files are written to, the
dirty xattr is never set on the brick that is up.
On 08/13/2015 07:30 PM, Lakshmi Anusha wrote:
Hello,
We managed to collect below command outputs:
Brick1 getfattr -d -m . -e hex
/opt/lvmdir/c2/brick/logfiles/security/EVENT_LOG.xml
getfattr: Removing leading '/' from absolute path names
# file:
On 08/11/2015 03:28 PM, Lakshmi Anusha wrote:
From the extended attributes, an entry split-brain seems to be
appeared. Since gfid is different for the original file and its replica.
Can you please let us know why the split-brain files are not shown in
gluster volume heal vol info split-brain
Hello,
We are using glusterfs version 3.7.2.
There are few i/o errors reported during our testing and i/o errors are due
to split brain files.
We tried to find the split brain files with gluster volume heal vol info
split-brain.
But strangely the command shows that the number of split brain files
