Oroblems with Insight Storage Driver and Kernel 2.4.9

[Ayman Altounji]

Hallo Support,

We want to use 8 ML370 in 2 Piranha Cluster under Redhat 7.2.

Because the 2.4.7 Kernel has some Security issues we now want to use 2.4.9 kernel. Since updating to 2.4.9 the Server crashes probably in in kjornald sometimes after 2 hours sontimes after 24 hours - and they are not in Produktion at the moment - so almost nothing is happening on the server.

Is there a solution for this problem ?
When are the 5.40 Drivers released ? (I see only the Insight Network Drivers online: http://www.compaq.com/support/files/server/us/download/14379.html)
Are they for kernel 2.4.18 (Redhat 7.3) ? Or also for 7.2 with 2.4.9 ?

If 2.4.18 is the RedHat rawhide kernel 2.4.18 stable with the 5.40 drivers ?

Futher information :

EXT3 Filesystem
Remote Insight lights-out card with installed insight drivers.

4 Webserver :
squid
sendmail
apache

4 Piranha Server:
Piranha (http://www.redhat.com/support/resources/howto/piranha/ and http://ftp.linux.org.uk/pub/linux/piranha/7.2/)

Thnak you in advance :)
Christian Jacobsen

[Ayman Altounji]

Hallo,

I have some more infomation.

I hav posted the same thing at RedHat : https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=64906

It seems to be the Insight Drivers. I have disabled one of the processes
of the Insight Drivers that showed up in the Screen Output : cmaidad
Since Friday that Server did not crash anymore.

Maybee it is the Smart Array Driver not working 100% with the Insight Driver :(

The bad thing (for me) is that that process is monitoring the Array Controller
(Raid 5) and that means I am not getting any errors wenn Harddisks fail :(

I am not 100% sure,I have 8 ML370 and only tested this on one over the weekend.
Today I and am going to expand this to 4 Maschines and watch it a couple of
Days to see what happens.

Christian Jacobsen

[Ayman Altounji]

Hallo,

to solve the problem you can use the NEW Insight Drivers 5.40 wich are now released ;) They seem to bee stabel - have only tested 1 day :)

Or disabling cmaidad on 5.30 solves the problem. Then you have no Surveilance of the Raid Adapter and the Harddisks. This is how to do it :

##########################################################

/etc/rc.d/init.d/cmastor stop

"vi /etc/rc.d/init.d/cmastor? change : PNAMES="cmastorpeerd cmaidad cmafcad cmaided cmascsid" in : # PNAMES="cmastorpeerd cmaidad cmafcad cmaided cmascsid" PNAMES="cmastorpeerd cmafcad cmaided cmascsid"

Then /etc/rc.d/init.d/cmastor start

##########################################################