From owner-freebsd-questions@FreeBSD.ORG Wed May 12 19:48:46 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 CDA24106566B for ; Wed, 12 May 2010 19:48:46 +0000 (UTC) (envelope-from ahamiltonwright@mta.ca) Received: from smtpx.mta.ca (smtpx.mta.ca [138.73.1.138]) by mx1.freebsd.org (Postfix) with ESMTP id 9FCB18FC0A for ; Wed, 12 May 2010 19:48:46 +0000 (UTC) Received: from [138.73.29.51] (port=49186 helo=qemg.org) by smtpx.mta.ca with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.71) (envelope-from ) id 1OCHv9-0008Vu-T6; Wed, 12 May 2010 16:48:43 -0300 Date: Wed, 12 May 2010 16:48:43 -0300 (ADT) From: "A. Wright" To: Mike Tancsa In-Reply-To: <201005121456.o4CEurEZ078671@lava.sentex.ca> Message-ID: References: <201005121456.o4CEurEZ078671@lava.sentex.ca> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: ahamiltonwright@mta.ca 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 19:48:46 -0000 On Wed, 12 May 2010, Mike Tancsa wrote: > At 09:46 AM 5/12/2010, A. Wright wrote: >> Does anyone have any thoughts on how to conclusively >> prove that the drive is at fault? I have not seen any >> errors logged to dmesg. > > Start with smartmontools to ask your disk if it has logged any errors > and check once a day or so to see if sectors are being remapped. Thanks for the tip. So I ran the "short" test, and am now running the "long" test. After the short test, I have been examining the output (using smartctl -a), and there seem to be no errors reports. 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? Thanks, Andrew.