Hi,
So the 'fix' is applied directly to the host os, is this the correct thing to
do?
sysctl -w vm.min_free_kbytes = 8192
Keith
On 14 Feb 2011, at 10:36, Kwan Lowe wrote:
On Sun, Feb 13, 2011 at 7:00 PM, Adam Tauno Williams
awill...@whitemice.org wrote:
em and force a check with fsck
On Mon, 2011-02-14 at 12:08 +, Keith Beeby wrote:
Hi,
So the 'fix' is applied directly to the host os,
no, to the *guest* OS instances. [please, do not top-post].
is this the correct thing to do?
sysctl -w vm.min_free_kbytes = 8192
No space(s) I believe.
sysctl -w
On Mon, Feb 14, 2011 at 8:00 AM, Adam Tauno Williams
awill...@whitemice.org wrote:
On Mon, 2011-02-14 at 12:08 +, Keith Beeby wrote:
Hi,
So the 'fix' is applied directly to the host os,
no, to the *guest* OS instances. [please, do not top-post].
is this the correct thing to do?
sysctl
On 02/14/2011 07:31 AM, Kwan Lowe wrote:
On Mon, Feb 14, 2011 at 8:00 AM, Adam Tauno Williams
awill...@whitemice.org wrote:
On Mon, 2011-02-14 at 12:08 +, Keith Beeby wrote:
Hi,
So the 'fix' is applied directly to the host os,
no, to the *guest* OS instances. [please, do not top-post].
It's certainly possible that the error I was receiving was a different
reason, though similar symptoms. We started seeing filesystems go
read-only, and only rebooting would clear it up.
I use that setting on the Host OS for VMWare to prevent a whole vm
from getting killed.
That setting
On Sun, Feb 13, 2011 at 4:03 PM, Adam Tauno Williams
awill...@whitemice.org wrote:
On Sun, 2011-02-13 at 20:28 +, 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
On Mon, 2011-02-14 at 13:01 -0800, Bazooka Joe wrote:
On Sun, Feb 13, 2011 at 4:03 PM, Adam Tauno Williams
awill...@whitemice.org wrote:
On Sun, 2011-02-13 at 20:28 +, Keith Beeby wrote:
Also seeing this issue with CentOS 5.4 and 5.5 with NFS shared
storage, according the the VMware
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
On Sun, Feb 13, 2011 at 9:09 AM, Adam Tauno Williams
awill...@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
On Sun, Feb 13, 2011 at 9:09 AM, Adam Tauno Williams
awill...@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
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
On Sun, 2011-02-13 at 09:40 -0500, Kwan Lowe wrote:
On Sun, Feb 13, 2011 at 9:09 AM, Adam Tauno Williams
awill...@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
On Sun, 2011-02-13 at 20:28 +, 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
13 matches
Mail list logo
