I should add that in /var/lib/glusterd/vols/gv0/gv0-shd.vol and in all other configs in /var/lib/glusterd/ on all three machines the nodes are consistently named client-2: zephyrosaurus client-3: alvarezsaurus client-4: nanosaurus This is normal. It was the second time that a brick was removed, so client-0 and client-1 are gone. So the problem is the file attibutes themselves. And there I see things like trusted.afr.gv0-client-0=0x000000000000000000000000 trusted.afr.gv0-client-1=0x000000000000000000000ab0 trusted.afr.gv0-client-3=0x000000000000000000000000 trusted.afr.gv0-client-4=0x000000000000000000000000 and trusted.afr.gv0-client-3=0x000000000000000000000000 trusted.afr.gv0-client-4=0x000000000000000000000000 and other such, where the only thing that is consistent, is inconsistency. When a brick is removed, shouldn't all files on the remaining bricks be re-fattr'ed to remove the pointers to the non-existent brick? I guess I can do this manually, but it will still leave me with those files where the value of all trusted.afr.gv0-client(s) is zero. How does healing deal with those? Cheers, Z -- Слава Україні! Путлер хуйло! ________ Community Meeting Calendar: Schedule - Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC Bridge: https://meet.google.com/cpu-eiue-hvk Gluster-users mailing list Gluster-users@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-users
