| To: | xfs@xxxxxxxxxxx |
|---|---|
| Subject: | Re: Page allocation failure writing to an XFS volume via NFS on CentOS 4.3 |
| From: | "Luca Maranzano" <liuk001@xxxxxxxxx> |
| Date: | Mon, 24 Jul 2006 13:49:37 +0200 |
| Domainkey-signature: | a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=CfEvVDcyfgVH76bYXyrB87cH2IVVqZqAPJ7/ur0G2PbQTPF8IMErCrF0WAOc99eI9avhw019+w5dg1R+5eK+5PbV6xYjkeYhjefU5RGLI1hmJrLPR6MiaD6iyCUfX/oouBKJSkkTDvsLCYX+OatuAjftb3u8xEcb1x0TNRzPwaQ= |
| In-reply-to: | <20060721161326.GE12347@xxxxxxxxxxxxxxxxxxxxx> |
| References: | <68559cef0607210519q9f382c6n7104bef9cf9716f3@xxxxxxxxxxxxxx> <20060721161326.GE12347@xxxxxxxxxxxxxxxxxxxxx> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
Could it be an issue about the min_free_kbytes kernel parameter? On my server its current value is 957, but I've read that this could lead to kernel memory allocation failure even if there is actually enough RAM available. Since my trouble seem to be correlated to NFS access, could it be an interaction between network and disk I/O to trigger this problem? Thanks again. Regards, Luca On 7/21/06, Chris Wedgwood <cw@xxxxxxxx> wrote: On Fri, Jul 21, 2006 at 02:19:34PM +0200, Luca Maranzano wrote: > kswapd0: page allocation failure. order:0, mode:0xd0 you're out of memory, see what's being so piggy |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: XFS setting custom extent size: real-time section only?, Heilige Gheist |
|---|---|
| Next by Date: | Re: Page allocation failure writing to an XFS volume via NFS on CentOS 4.3, Shailendra Tripathi |
| Previous by Thread: | Re: Page allocation failure writing to an XFS volume via NFS on CentOS 4.3, Luca Maranzano |
| Next by Thread: | Re: Page allocation failure writing to an XFS volume via NFS on CentOS 4.3, Shailendra Tripathi |
| Indexes: | [Date] [Thread] [Top] [All Lists] |