Re: How does GD_SYNCOP work?

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

 



On Fri, Sep 12, 2014 at 06:31:55AM +0200, Emmanuel Dreyfus wrote:
> It is fine for me that glusterd_bricks_select_heal_volume() finds 3
> bricks, they are the 3 remaining alive bricks. However I am surprised to
> see the first in the list having rpc->conn.name = "management". It
> should be a brick name here, right? Or is this glustershd?

Reading the code, it has to be glustershd.

I tracked down most of the problem. The request to glustershd times out
before the reply comes, because glustershd gets stuck in an infinite loop.

In afr_shd_gather_index_entries(), the obtained offset is corrupted
(huge negative value), and the loop never ens.

I will not look for why this offset is corrupted.

-- 
Emmanuel Dreyfus
manu@xxxxxxxxxx
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-devel




[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