o2hb is timing out because the io to the device is taking too much time.
Not much one can do other than increase the time out. Say 2mins.
O2CB_HEARTBEAT_THRESHOLD = 61
Consulente3 wrote:
I can reprodute it, every time on heavy IO
I have read this FAQ:
I encounter "Kernel panic - not syncing:
Not really. The mainline tree is labeled 1.3.x because it is the tree
we add new features too. But bug fixes are applied to both 1.2 and
1.3 separately so it is hard to tell by the version# alone.
This is the fix in the git tree:
commit 4b1af774451bbc8440719e3fe441934a337c3b63
Author: Kurt Hacke
On 1/23/07, Sunil Mushran <[EMAIL PROTECTED]> wrote:
This was the lvb issue that was fixed long ago. In the 1.2 tree, it was
fixed in 1.2.2.
2.6.18 should definitely have the fix for this.
it seems it's even more recent:
/var/log/messages.4:Dec 27 19:40:40 rack1 kernel: OCFS2 Node Manager 1.
This was the lvb issue that was fixed long ago. In the 1.2 tree, it was
fixed in 1.2.2.
2.6.18 should definitely have the fix for this.
davide rossetti wrote:
OS: Fedora Core release 4 (Stentz)
KERNEL: Linux rack1.ape 2.6.17-1.2142_FC4smp #1 SMP Tue Jul 11
22:57:02 EDT 2006 i686 i686 i386 GNU/
OS: Fedora Core release 4 (Stentz)
KERNEL: Linux rack1.ape 2.6.17-1.2142_FC4smp #1 SMP Tue Jul 11 22:57:02 EDT
2006 i686 i686 i386 GNU/Linux
CLUSTER: 11 Linux kernels, mixed environment FC4,FC5,FC6
SAN: FC Infortrend storage, QLogic16 port FC switch, FC adapter LSI FC929X
(21224,1):ocfs2_trunca
I can reprodute it, every time on heavy IO
I have read this FAQ:
I encounter "Kernel panic - not syncing: ocfs2 is very sorry to be fencing this
system by panicing" whenever I run a heavy io load?
so, i have append on node "becks" , the string "elevator=deadline" on boot
node ocfs2, has the de
