kjournald hanging on RAID1 setup

[DSWS]

Every couple of days one of our servers seems to have kjournald hang. Something like this:

Assertion Failure on journal_commit_transaction() at commit.c:535:

Kernel BUG at commit.c:535!
invalid operand: 0000
CPU: 3
EIP: 0000;[<f884b034>] not tainted
EFLAGS: 00010286

A little research shows that the problem may be kernel related. See http://rhn.redhat.com/errata/RHBA-2002-085.html

Of course the RAID drivers do not work with the new kernel so a kernel update can not be done to fix this problem.

Server is a quad cpu p4 2ghz with 2GB ram.

Anyone else have a similar experience?

[Chicken]

Originally posted by DSWS
Server is a quad cpu p4 2ghz with 2GB ram.
Yeeeeeuuuuh, I have one of those... but mine's a single AMD K6/2-450 with 128MB of ram. *snaps suspenders* I know you are jealous! I've never heard of that issue, I just wanted to say that I have server envy.

[DSWS]

yeah - envy a server that hangs every two days... :D

All that server and no sites on it till it gets fixed... :mad:

and just for good measure - how about a banana man... :banana:

[Chicken]

I don't know if this will be helpful, but: Google Search (http://www.google.com/search?hl=en&lr=&ie=UTF-8&oe=UTF-8&q=%22journal_commit_transaction%28%29+at+commit.c% 3A535%3A%22)

Obviously this poses a problem (below), but I'm not sure if there's a workaround:
Originally posted by DSWS
Of course the RAID drivers do not work with the new kernel so a kernel update can not be done to fix this problem.

[DSWS]

There is a work around. Go into grub.conf and change default=0 to default=3.

Basically this boots into the non SMP kernel.

Of course this disables 3 outta 4 processors. :(