[Bugs] [Bug 1229226] Gluster split-brain not logged and data integrity not enforced

bugzilla at redhat.com bugzilla at redhat.com
Mon Jun 8 21:39:54 UTC 2015


--- Comment #2 from Jeff Darcy <jdarcy at redhat.com> ---
OK, I lied.  Previously, I had been cutting off access to each brick
sequentially, with client unmounts and remounts in between.  This time, I
mounted twice simultaneously, and cut off each client's connection to one
brick.  Something like this (your port numbers may vary).

> iptables -t mangle -I OUTPUT -p tcp --sport 1020 --dport 49152 -j DROP
> iptables -t mangle -I OUTPUT -p tcp --sport 1002 --dport 49153 -j DROP

With this, I got into a state where *one* client could still read the file from
the still-connected brick without error.  Interestingly, it was not symmetric;
the other client did report EIO, as it should.  Xattrs do show pending
operations for each other, and "heal info" shows split-brain from both sides.

As I wrote this, the state changed yet again.  Now both clients correctly
return EIO.  This strongly suggests that some state is being cached improperly
on the clients, but not infinitely.  The plot thickens.

You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.

More information about the Bugs mailing list