Hi
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 value apply CentOS v.5.4 and 5.5 as well to resolve the issue?
On 13 Feb 2011, at 14:40, "Kwan Lowe" <kwan.lowe@xxxxxxxxx> wrote:
> On Sun, Feb 13, 2011 at 9:09 AM, Adam Tauno Williams
> <awilliam@xxxxxxxxxxxxx> 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.
> _______________________________________________
> CentOS mailing list
> CentOS@xxxxxxxxxx
> http://lists.centos.org/mailman/listinfo/centos
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
