Date: Fri, 26 Jan 2007 17:12:00 -0500 From: Kris Kennaway <kris@obsecurity.org> To: Remco Bressers <remco@signet.nl> Cc: Remco Bressers <rbressers@signet.nl>, freebsd-bugs@FreeBSD.org, Kris Kennaway <kris@obsecurity.org> Subject: Re: kern/103455: "swap_pager: indefinite wait buffer" with page file enabled (causes lockups) Message-ID: <20070126221159.GA18237@xor.obsecurity.org> In-Reply-To: <1169847626.12665.4.camel@localhost> References: <200701251040.l0PAeNie054614@freefall.freebsd.org> <20070126185857.GB15976@xor.obsecurity.org> <1169847626.12665.4.camel@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jan 26, 2007 at 10:40:26PM +0100, Remco Bressers wrote: > On vr, 2007-01-26 at 13:58 -0500, Kris Kennaway wrote: > > On Thu, Jan 25, 2007 at 10:40:23AM +0000, Remco Bressers wrote: > > > The following reply was made to PR kern/103455; it has been noted by GNATS. > > > > > > From: Remco Bressers <rbressers@signet.nl> > > > To: bug-followup@FreeBSD.org, nick@nickwithers.com > > > Cc: > > > Subject: Re: kern/103455: "swap_pager: indefinite wait buffer" with page > > > file enabled (causes lockups) > > > Date: Thu, 25 Jan 2007 09:38:21 +0100 > > > > > > Hi, > > > > > > I noticed the same problem on 6.2-RELEASE on a heavily loaded storage > > > system running rsync. > > > When multiple clients connect to the rsync box and start filling up the > > > memory with file-lists, the machine (once in a while) locks up with the > > > same messages : > > > > > > swap_pager: indefinite wait buffer: bufobj: 0, blkno: 43638, size: 4096 > > > swap_pager: indefinite wait buffer: bufobj: 0, blkno: 43947, size: 32768 > > > swap_pager: indefinite wait buffer: bufobj: 0, blkno: 44007, size: 4096 > > > swap_pager: indefinite wait buffer: bufobj: 0, blkno: 47939, size: 32768 > > > > > > The machine becomes non-responsive unfortunatly. > > > > Are you sure it's the same, i.e. are you also using a swap file? > > > > Kris > > I'm using a swap filesystem. The machine has 1GB of RAM : Then no, it's not the same ;-) Anyway, check the archives for previous mails discussing this topic, including steps to try and work around and/or diagnose the problem. Kris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070126221159.GA18237>