have any more debugging questions, feel free to ask me
thanks
-Messaggio originale-
Da: Srinivas Eeda [mailto:[EMAIL PROTECTED]
Inviato: lunedì 22 gennaio 2007 18.30
A: Consulente3
Cc: ocfs2-users@oss.oracle.com
Oggetto: Re: [Ocfs2-users] kernel panic - not syncing
problem appears
problem appears to be that IO is taking more time than effective
O2CB_HEARTBEAT_THRESHOLD. Your configured value 31 doesn't seem to be
effective?
Index 6: took 1995 ms to do msleepIndex
Index 17: took 1996 ms to do msleep
Index 22: took 10001 ms to do waiting for read completion.
Can you
o2net timeout cannot cause the o2hb panic. The two are totally
different. From the outputs, I would guess o2hb is timing out but
I cannot say for sure till I don't see the full logs.
Andy Phillips wrote:
Its worth pointing out that the o2net idle timer is triggering on the
network heartbeat,
I understand that. But that's not what the user experienced in this case.
One node ran into the o2hb timeout (and panic) that caused the o2net
message on the other node.
These are two separate issues. FWIW, I am trying to get the o2net config
backported to the 1.2 tree.
Andy Phillips wrote:
Lot of ink has been spilled on this subject. ;)
Check out the heartbeat section in the FAQ. One easy solution is to
increase the hb timeout to 60 secs...
O2CB_HEARTBEAT_THRESHOLD = 31
We will leaning towards making that number the default in the 1.4 release.
George Liu wrote:
Both systems
: [Ocfs2-users] Kernel panic - not syncing: ocfs2 is very sorry
Lot of ink has been spilled on this subject. ;)
Check out the heartbeat section in the FAQ. One easy solution is to
increase the hb timeout to 60 secs...
O2CB_HEARTBEAT_THRESHOLD = 31
We will leaning towards making that number
