Re: lots of 'self heal' messages with unify

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

 



Here's another interesting error message. I shall re-try with your no heal option.

2009-01-14 12:08:28 E [client-protocol.c:263:call_bail] unify-switch- ns: activating bail-out. pending frames = 2. last sent = 2009-01-14 12:05:58. last received = 2009-01-14 12:05:58. transport-timeout = 42 2009-01-14 12:08:28 C [client-protocol.c:298:call_bail] unify-switch- ns: bailing transport 2009-01-14 12:08:28 E [client-protocol.c:263:call_bail] distfs01- stripe: activating bail-out. pending frames = 2. last sent = 2009-01-14 12:05:58. last received = 2009-01-14 12:05:58. transport- timeout = 42



Dan Parsons


On Jan 14, 2009, at 11:50 AM, Anand Avati 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

Under normal cases self-heal should not be triggered so much. Can you
describe briefly how you populated data into your mountpoint? Also
please post your volfiles (I'm sorry if you already have) just so that
I can review the configuration.

avati






[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