From owner-freebsd-questions@FreeBSD.ORG Wed May 12 20:03:06 2010 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 55EBE1065670 for ; Wed, 12 May 2010 20:03:06 +0000 (UTC) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by mx1.freebsd.org (Postfix) with ESMTP id 182EE8FC14 for ; Wed, 12 May 2010 20:03:05 +0000 (UTC) Received: from mdt-xp.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.14.3/8.14.3) with ESMTP id o4CK34II080338; Wed, 12 May 2010 16:03:04 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <201005122003.o4CK34II080338@lava.sentex.ca> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Wed, 12 May 2010 16:03:00 -0400 To: "A. Wright" From: Mike Tancsa In-Reply-To: References: <201005121456.o4CEurEZ078671@lava.sentex.ca> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Cc: "freebsd-questions@freebsd.org" Subject: Re: Long I/O pauses on same mass storage 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: Wed, 12 May 2010 20:03:06 -0000 At 03:48 PM 5/12/2010, A. Wright wrote: >I just noticed, however, the following two interesting lines that >/var/log/messages seems to have acquired: > May 12 15:44:00 qemg kernel: ad8: FAILURE - SMART > status=51 error=4 > May 12 16:05:27 qemg kernel: swap_pager: indefinite wait > buffer: bufobj: 0, blkno: 294, size: 8192 >The first dates from the point at which I turned on SMART data logging. >The second one, however looks more interesting to me -- am I correct >in thinking that there is no good reason why the "swap_pager" error >would appear, aside from some sort of hardware related failure? When I see errors from the OS, but not on the actual disk itself, apart from driver errors (relatively rare on FreeBSD) it can be a cable issue or bad SATA port. But as chuck said, post all of the output from smartctl -a ---Mike