Re: lots of 'self heal' messages with unify

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

 



Also, then many times after I'll get the below error messages and then /glusterfs actually becomes "transport endpoint disconnected".

2009-01-14 10:59:41 E [client-protocol.c:263:call_bail] distfs01- stripe: activating bail-out. pending frames = 2. last sent = 2009-01-14 10:58:56. last received = 2009-01-14 10:58:56. transport- timeout = 42 2009-01-14 10:59:41 C [client-protocol.c:298:call_bail] distfs01- stripe: bailing transport 2009-01-14 10:59:41 E [client-protocol.c:263:call_bail] distfs02- stripe: activating bail-out. pending frames = 2. last sent = 2009-01-14 10:58:56. last received = 2009-01-14 10:58:56. transport- timeout = 42

What do those mean? I see no errors on any of the servers.

Dan Parsons


On Jan 14, 2009, at 10:57 AM, Dan Parsons wrote:

I'm seeing a lot of messages like this, any time a directory is even just ls'd:

2009-01-14 10:56:15 W [unify-self-heal.c:593:unify_sh_checksum_cbk] unify: Self-heal triggered on directory /bio/data/gene_flagging/ evigan_input/bp1_genomes/44/SUPERFAM

I think I read that this was a known issue and that I can ignore the self heals, but that it would be fixed in a future patch. I'm running the latest TLA, so is this actually an issue?


Dan Parsons




_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxx
http://lists.nongnu.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