search for: contis_sys

...fattr) set the afr attribute to a null value before reconnecting the faulty brick, and it'll heal from the correct one. And for files which have been deleted/renamed/created on the correct node while the bad one was offline, how are those handled ? For example, I have /mnt/bricks/vmstore/prod/contis_sys.qcow2 ont btoh bricks. But, on the correct one, the file was deleted and recreated while the bad one was offline. So they haven't the same gfid now. How does gluster handle this ? Sorry for all those questions, I'm just a bit nervous :-) -- Daniel Berteaud FIREWALL-SERVICES SAS. Soci?t?...

...present. All gfids present in good will be created on the bad if not present. https://github.com/gluster/glusterfs-specs/blob/master/done/Features/afr-v1.md can give you an idea of how replication works in glusterfs-3.5 (which you are using) and earlier. -Ravi > > /mnt/bricks/vmstore/prod/contis_sys.qcow2 ont btoh bricks. But, on the correct one, the file was deleted and recreated while the bad one was offline. So they haven't the same gfid now. How does gluster handle this ? > > Sorry for all those questions, I'm just a bit nervous :-) >

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,