On 30/01/20 9:28 pm, Strahil Nikolov wrote:
On January 30, 2020 8:21:18 AM GMT+02:00, Ravishankar N
wrote:
On 30/01/20 11:41 am, Ravishankar N wrote:
I think for some reason setting of AFR xattrs on the parent dir did
not happen, which is why the files are stuck in split-brain (instead
of
On January 30, 2020 8:21:18 AM GMT+02:00, Ravishankar N
wrote:
>
>On 30/01/20 11:41 am, Ravishankar N wrote:
>> I think for some reason setting of AFR xattrs on the parent dir did
>> not happen, which is why the files are stuck in split-brain (instead
>> of getting recreated on repo2 using the
out which files corresponded to the mentioned GFIDs.
We think it must be either a bug or a undocumented behaviour in GlusterFS.
Stefan
- Original Message -
> Date: Wed, 29 Jan 2020 16:26:35 +
> To: "'gluster-users@gluster.org'"
> Subject: [Gluster-users] interp
On 30/01/20 11:41 am, Ravishankar N wrote:
I think for some reason setting of AFR xattrs on the parent dir did
not happen, which is why the files are stuck in split-brain (instead
of getting recreated on repo2 using the files from repo0 or 1).
Can you provide the getfattr output of the
On 29/01/20 9:56 pm, Cox, Jason wrote:
I have glusterfs (v6.6) deployed with 3-way replication used by ovirt
(v4.3).
I recently updated 1 of the nodes (now at gluster v6.7) and rebooted.
When it came back online, glusterfs reported there were entries to be
healed under the 2 nodes that
I have glusterfs (v6.6) deployed with 3-way replication used by ovirt (v4.3).
I recently updated 1 of the nodes (now at gluster v6.7) and rebooted. When it
came back online, glusterfs reported there were entries to be healed under the
2 nodes that had stayed online.
After 2+ days, the 2 nodes
