[Bugs] [Bug 1262964] Cannot access volume when network down

bugzilla at redhat.com bugzilla at redhat.com
Thu Sep 17 15:00:04 UTC 2015


https://bugzilla.redhat.com/show_bug.cgi?id=1262964

Ravishankar N <ravishankar at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
              Flags|                            |needinfo?(huy.vu at mitel.com)



--- Comment #21 from Ravishankar N <ravishankar at redhat.com> ---
(In reply to Huy VU from comment #19)
> (In reply to Ravishankar N from comment #17)
> > So I see that the file has been edited from node 2 as well. 
> > 
> > `grep -rne "renaming /testfile.txt"  mnt-glusterd.log` shows entries from
> > the mount log of both nodes, leading to gfid split-brain. Is that right?
> 
> Hello Ravi,
> 
> I did a number of tests at different times. Some tests had me editing the
> file on node 1; some one node 2; some on both.

Hi VU,

I know that the time stamps are different. If you do modification operations
from different nodes while each node cannot see the other, it will result in 
split-brain.

Are you consistently able to repro the issue with the steps you described? (I
am not). If yes then please upload logs from that fresh test set-up (makes
debugging easier). Here is what I tried:

1. Create a 1x2 volume and mount on both nodes, create a file on the mount from
any mount.
2. Bring eth0 down on node2
3. Edit the file from node1's mount
4. Bring back node2.
5. Launch heal.

No split-brain observed.

Note that if you do any modifications on node-2 (even to another file) between
steps 2 and 4, the parent directories end up in entry split-brain and a
conservative merge is attempted, which fails to heal the file edited on step 3
due to gfid mismatch. This is what I think happened in your case.

 When you grep for 'renaming',
> please do so on both sets of logs (node 1's and node 2's) and compare the
> timestamps of the logs.

-- 
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