Emergency UNIX and Linux Support

Hi Everyone,

This seems to be Kernel bug, as par this vmware link "http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=51306&sliceId=1&docTypeID=DT_KB_1_1&dialogID=283139327 &stateId=0%200%20283141315"

it is suggested to patch the server, which are made against kernel version 2.6.18-8.1.4.el5 from kernel-2.6.9-55.EL

Code:

# uname -r
2.6.18-274.3.1.el5
# more /etc/redhat-release
CentOS release 5.7 (Final)

I am currently CentOS 5.7, and kernel version is listed above, not sure weather this patch is included in part of installation. Can someone please suggest.

Thanks,

I don't think this is your problem. kernel-2.6.9-55.EL is a RHEL 4 kernel, so this is an old bug from 2007. The bug was addressed by Red Hat bug 228108 - bugzilla.redhat.com/show_bug.cgi?id=228108

Your current kernel of 2.6.18-274.3.1.el5 is already much newer than the 2.6.18-8.1.4.el5 kernel (release 5.1) they want you to patch to.

See bugzilla.redhat.com/show_bug.cgi?id=228108 for RHEL/Centos kernel versions versus releases.

I still think you have an underlying problem with the storage at the ESX level.

Hello,

We had similar issue repeating again, as we are using iscsi storage for ESX server.
Actual the issue was network switch got rebooted, all the linux VM's had read-only filesystem error. All version of Linux OS are CentOS 5.7.

Is their any patch available for this kind of this kind of issue, that will be really helpful.

Sick of rebooting each and every server.

Thanks,

As mentioned earlier, I would second the thought that it's not an RHEL issue. Rather it's an ESX issue. Somehow the hypervisor is failing to do what it's supposed to do once the switches come back.

Did you check by executing "mount -o remount,rw /"?

Can you please check your ESX server's log and check with VMWare support?

Storage is not intended to be intermittently connected and disconnected while in operation. You have a single point of failure there and the ext3 component of RHEL is trying to protect your data when your network fails and the one and only path to your disks go down.

The "patch" would be to provide redundant paths to your storage, which with iSCSI would give the added implicit benefit of redundant network connections.

Additionally, your environment would benefit from some form of change control, so that the potential impact of every proposed change to the environment - such as rebooting a network switch - is carefully considered and approved before it happens and is clearly documented.

If nothing is working then try to upgrade your firmware, sometime upgradation of firmware solve the problem.