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

Adam Tauno Williams awilliam at whitemice.org
Mon Feb 14 22:02:09 UTC 2011


On Mon, 2011-02-14 at 13:01 -0800, Bazooka Joe wrote: 
> On Sun, Feb 13, 2011 at 4:03 PM, Adam Tauno Williams
> <awilliam at whitemice.org> wrote:
> > 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].
> I am experiencing the same issue.
> cent: current
> exsi v3.5 update 5
> storage nfs
> I am in the process of rebuilding the virtual server using a different
> os thinking it was just file system errors.

What other OS?

I've experienced one [possibly unrelated] corruption of the /tmp
filesystem on an openSUSE 11.1 VM.  So far Windows VMs seem immune to
the issue.




More information about the CentOS mailing list