Ongoing RedHat 5.0 Cloverleaf 5.6 SAN Issue

[Max Drown (Infor)]

Our platform: IBM 3650, VMWare ESX x3.5 Update 2, RedHat 5.0 Enterprise, EMC SAN CX3-40, Cloverleaf 5.6 rev2.

Every month or so seemingly randomly our RedHat server goes into a read-only state and we see a “kernel: journal commit I/O error” error pop up in open terminal windows. The server has to be rebooted to recover from this error. We’ve gone back and forth with the infrastructure people, RedHat, VMWare, and EMC and they all want us to upgrade to RedHat 5.1 which is not certified by HeatlhVision for Cloverleaf 5.6.

Has anyone out there had a similar problem? If so, how did you resolve it?

-- Max Drown (Infor)

Topic

[David Burks]

I have sent you 3 emails on this issue.  Please check to make sure you we are not getting filtered by your spam filters.

Also, please use techsupport@healthvision.com instead of support@healthvision.com.  Using the latter eventually gets to Cloverleaf support but only after waiting it’s turn in our internal support group and recognized as something that needs to be forwarded to us.

If you still have not received anything on this then my may want to call support.

[Max Drown (Infor)]

Ok. That was a confusing email thread, but after looking more closely at it I see that you responded with “Cloverleaf 5.6 is not supported on Linux 5.1. If upgrading the kernel means upgrading Linux from 5.0 to 5.1 then you will need to upgrade your Cloverleaf to 5.7.”

I knew this already, but doing an OS patch and Cloverleaf patch in a large organization is not a trivial thing due to the amount of people and applications involved.  So what I’ve been trying to find out from HealthVision and maybe from the user community is if anyone knows what RedHat kernel versions are supported (i.e., how far can you patch the RedHat kernel w/o taking RedHat to 5.1 and still working properly with Cloverleaf 5.6). It may not be possible to update the kernel at all without moving to 5.1, but I honestly don’t know enough about it.

Sorry for all the confusion, we are trying to get to 5.7 asap and are praying that that will take care of the SAN issues, but in the meantime we’re investigating every possible solution to our problem.

-- Max Drown (Infor)

[Author]

Replies