[CentOS] Journal Aborts in VMware ESX (Filesystem Corruption)

[Adam Tauno Williams]

On Sun, 2011-02-13 at 20:28 +0000, Keith Beeby wrote:
> Also seeing this issue with CentOS 5.4 and 5.5 with NFS shared
> storage, according the the VMware knowledge base article this should
> have been resolved in v5.1 update??.
> Does changing the vm.min_free_kbytes valu  apply CentOS v.5.4 and 5.5
> as well to resolve the issue?

I guess we'll see [this issue has become extremely frustrating].

I suppose it is 'good' to see that someone else sees the issue as well.
One issue with virtualization is that debugging these types of issues is
an order-of-magnitude more difficult [virtualized OS, virtualized
storage, virtualization platform, or some interaction of all the
above... ugh].

> On 13 Feb 2011, at 14:40, "Kwan Lowe" <kwan.lowe at gmail.com> wrote:
> > On Sun, Feb 13, 2011 at 9:09 AM, Adam Tauno Williams
> > <awilliam at whitemice.org> wrote:
> >> I have several CentOS5 hosts in a VMware ESX 3.5.0 226117 environment
> >> using iSCSI storage.  Recently we've begun to experience journal aborts
> >> resulting in remounted-read-only filesystems as well as other filesystem
> >> issues - I can unmount a filesystem and force a check with "fsck -f" and
> >> occasionally find errors.
> > http://communities.vmware.com/message/245983 
> > The setting we used to resolve was vm.min_free_kbytes = 8192
> > Previous to this we were seeing the error pop up every week or so.