Re: split brain: how should it be cured?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Jun 19, 2012 at 04:01:16AM +0200, Emmanuel Dreyfus wrote:
> Um, now both bricks have the split brain flag. How removing the file on
> one brick will make it recreated on the other one, but the split brain
> flag is sticky!

I was about to resume investigation more than a day later, and the
offending file can now be readen without getting EIO. The split
brain flags are stil lthere, though (see below). Does that makes
sens, or did I overlooked something or got confused? Anyone can 
explain me how this thing is supposed to work?

On brick1, yesterday:
trusted.afr.pfs-client-0   00 00 00 00 00 00 00 03 00 00 00 00
trusted.afr.pfs-client-1   00 00 00 00 00 00 00 01 00 00 00 00
Today:
trusted.afr.pfs-client-0   00 00 00 00 00 00 00 00 00 00 00 00
trusted.afr.pfs-client-1   00 00 00 00 00 00 00 01 00 00 00 00

On brick2, yesterday:
trusted.afr.pfs-client-0   00 00 00 00 00 00 00 00 00 00 00 00
trusted.afr.pfs-client-1   00 00 00 00 00 00 00 01 00 00 00 00
Today:
trusted.afr.pfs-client-0   00 00 00 00 00 00 00 03 00 00 00 00
trusted.afr.pfs-client-1   00 00 00 00 00 00 00 00 00 00 00 00

-- 
Emmanuel Dreyfus
manu@xxxxxxxxxx



[Index of Archives]     [Gluster Users]     [Ceph Users]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux