search for: bilbao_sys

...The good copy will have non-zero trusted.afr* xattrs that blame > the bad one and heal will happen from good to bad.? If both bricks have > attrs blaming the other, then the file is in split-brain. Thanks. So, say I have a file with this on the correct node # file: mnt/bricks/vmstore/prod/bilbao_sys.qcow2 security.selinux=0x73797374656d5f753a6f626a6563745f723a66696c655f743a733000 trusted.afr.vmstore-client-0=0x00050f7e0000000200000000 trusted.afr.vmstore-client-1=0x000000000000000100000000 trusted.gfid=0xe86c24e5fc6b4fc6bf2b896f3cc8537d And this on the bad one # file: mnt/bricks/vmstore/prod...

...non-zero trusted.afr* xattrs that blame >> the bad one and heal will happen from good to bad.? If both bricks have >> attrs blaming the other, then the file is in split-brain. > Thanks. > > So, say I have a file with this on the correct node > # file: mnt/bricks/vmstore/prod/bilbao_sys.qcow2 > security.selinux=0x73797374656d5f753a6f626a6563745f723a66696c655f743a733000 > trusted.afr.vmstore-client-0=0x00050f7e0000000200000000 > trusted.afr.vmstore-client-1=0x000000000000000100000000 > trusted.gfid=0xe86c24e5fc6b4fc6bf2b896f3cc8537d > > And this on the bad one &gt...

On 11/16/2017 12:54 PM, Daniel Berteaud wrote: > Le 15/11/2017 ? 09:45, Ravishankar N a ?crit?: >> If it is only the brick that is faulty on the bad node, but >> everything else is fine, like glusterd running, the node being a part >> of the trusted storage pool etc,? you could just kill the brick first >> and do step-13 in "10.6.2. Replacing a Host Machine with

Le 15/11/2017 ? 09:45, Ravishankar N a ?crit?: > If it is only the brick that is faulty on the bad node, but everything > else is fine, like glusterd running, the node being a part of the > trusted storage pool etc,? you could just kill the brick first and do > step-13 in "10.6.2. Replacing a Host Machine with the Same Hostname", > (the mkdir of non-existent dir,