From owner-freebsd-questions@FreeBSD.ORG Sun Jan 25 05:14:33 2009 Return-Path: Delivered-To: freebsd-questions@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B9839106566B for ; Sun, 25 Jan 2009 05:14:33 +0000 (UTC) (envelope-from freebsd@sopwith.solgatos.com) Received: from sopwith.solgatos.com (pool-71-117-207-61.ptldor.fios.verizon.net [71.117.207.61]) by mx1.freebsd.org (Postfix) with ESMTP id BF67D8FC18 for ; Sun, 25 Jan 2009 05:14:32 +0000 (UTC) (envelope-from freebsd@sopwith.solgatos.com) Received: by sopwith.solgatos.com (Postfix, from userid 66) id 364CCB64F; Sat, 24 Jan 2009 21:07:49 -0800 (PST) Received: from localhost by sopwith.solgatos.com (8.8.8/6.24) id RAA07150; Sat, 24 Jan 2009 17:06:50 GMT Message-Id: <200901241706.RAA07150@sopwith.solgatos.com> To: freebsd-questions@FreeBSD.org In-reply-to: Your message of "Sat, 24 Jan 2009 10:17:17 GMT." <497AEAAD.6020701@FreeBSD.org> Date: Sat, 24 Jan 2009 09:06:50 +0000 From: Dieter Cc: Subject: Re: swap_pager complaints but not using swap X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Jan 2009 05:14:34 -0000 > > AMD64 FreeBSD 7.0 2 GiB main memory > > > > My console says: > > > > login: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 22, size: 4096 > > swap_pager: indefinite wait buffer: bufobj: 0, blkno: 22, size: 4096 > > swap_pager: indefinite wait buffer: bufobj: 0, blkno: 22, size: 4096 > > swap_pager: indefinite wait buffer: bufobj: 0, blkno: 22, size: 4096 > > > > pstat -sk > > Device 1K-blocks Used Avail Capacity > > /dev/ad6s10 4590208 96 4590112 0% > > > > Wow, using a whole 96K of swap. I don't see any disk related > > complaints in dmesg. > > > > Is this something to worry about? > > Yes, the system was *trying* to do swap I/O and timing out while doing so. > > Kris Whoops, I forgot to change the subject line after adding the k option to pstat. Without the k it said 0 used. And this morning it occurs to me that even if swap used was zero, it could have been trying to *start* using swap. Anyway... given this timeout explaination, I'm guessing that page/swap has to compete with user processes for disk i/o, and thus probably suffers from the same lack of fair i/o scheduling that user processes suffer from. E.g. one process doing disk i/o can lock out another process for at least several minutes, probably indefinitely. :-(