Date: Wed, 14 Sep 2005 16:13:54 -0700 From: John-Mark Gurney <gurney_j@resnet.uoregon.edu> To: Kris Kennaway <kris@obsecurity.org> Cc: stable@freebsd.org, Ivan Voras <ivoras@fer.hr> Subject: Re: ENOMEM in swap_pager Message-ID: <20050914231354.GR793@funkthat.com> In-Reply-To: <20050914192543.GA79143@xor.obsecurity.org> References: <20050914211535.L97204@geri.cc.fer.hr> <20050914192543.GA79143@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Kris Kennaway wrote this message on Wed, Sep 14, 2005 at 15:25 -0400:
> On Wed, Sep 14, 2005 at 09:20:48PM +0200, Ivan Voras wrote:
> > On a P3 server with 1GB of memory, every now and then (about twice a
> > month) I get a log full of errors like this:
> >
> > swap_pager: I/O error - pageout failed; blkno 167,size 4096, error 12
^^
> > swap_pager: I/O error - pageout failed; blkno 182,size 4096, error 12
> > swap_pager: I/O error - pageout failed; blkno 199,size 8192, error 12
> > swap_pager: I/O error - pageout failed; blkno 12456,size 20480, error 12
> > swap_pager: I/O error - pageout failed; blkno 222,size 8192, error 12
> >
> > The server runs fine otherwise, and it doesn't seem to affect applications
> > in any way I'm able to detect. It's running latest 5.4-RELEASE, swap is
> > on a SCSI disk, single processor.
> >
> > IIRC GEOM should handle ENOMEMs by retrying the IO, but I'm asking just in
> > case - are these errors something I should worry about?
>
> I/O errors suggest your disk is failing.
Unless for some reason his disk is running out of memory:
grep 12 /usr/include/errno.h
#define ENOMEM 12 /* Cannot allocate memory */
--
John-Mark Gurney Voice: +1 415 225 5579
"All that I will do, has been done, All that I have, has not."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050914231354.GR793>