Description of problem: Facing GFID mismatch on 1x3 replica volumes Version-Release number of selected component (if applicable): glusterfs-3.7.9-12.el7rhgs How reproducible: Customer Environment Actual results: cluster.quorum-type is set to default,still facing GFID mismatch issue in the cluster Expected results: When cluster.quorum-type is set to default, volume accessibility should become read-only and no new writes should be happening,thus preventing from GFID mismatch issue Additional info: Customer has already acknowledge that there is some network issue between peers that why many disconnection is happening.
Abhishek, please provide the following: 1. sosreports of the servers and clients accessing the volume. 2. For any one file in gfid-split-brain, please provide the file name and `getfattr -d -m . -e hex` output for both the file *and* the parent directory.
Hi Abhishek, please also provide the fuse client logs from the clients. Note: Abhishek told me over IRC that the workload is running dovecot on the gluster volume and pointed me to the gfid split-brain messages in the shd logs.