From owner-freebsd-stable@FreeBSD.ORG Sat Jan 26 20:16:41 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1E38516A417 for ; Sat, 26 Jan 2008 20:16:41 +0000 (UTC) (envelope-from joe@skyrush.com) Received: from shadow.wildlava.net (shadow.wildlava.net [67.40.138.81]) by mx1.freebsd.org (Postfix) with ESMTP id ECF5713C465 for ; Sat, 26 Jan 2008 20:16:40 +0000 (UTC) (envelope-from joe@skyrush.com) Received: from [10.1.2.160] (pawnee.wildlava.net [67.40.138.85]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by shadow.wildlava.net (Postfix) with ESMTP id 3C7118F44A for ; Sat, 26 Jan 2008 13:16:40 -0700 (MST) Message-ID: <479B94E3.2030905@skyrush.com> Date: Sat, 26 Jan 2008 13:15:31 -0700 From: Joe Peterson User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <479A0731.6020405@skyrush.com> <20080125162940.GA38494@eos.sc1.parodius.com> <479A3764.6050800@skyrush.com> <3803988D-8D18-4E89-92EA-19BF62FD2395@mac.com> <479A4CB0.5080206@skyrush.com> <20080126003845.GA52183@eos.sc1.parodius.com> <479A86E5.5060806@skyrush.com> <20080126012124.GA53400@eos.sc1.parodius.com> <479B7C60.7000800@skyrush.com> In-Reply-To: <479B7C60.7000800@skyrush.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: "ad0: TIMEOUT - WRITE_DMA" type errors with 7.0-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Jan 2008 20:16:41 -0000 Joe Peterson wrote: > So I have started a "SeaTools" (disk scanner from Seagate) "long test" of the > drive. The short test passed already. The results should be interesting. If > it finds nothing wrong, I am going to start to wonder if I am experiencing ZFS > bugs that just happen to look like drive problems. I already did a long read, > under linux, of disk contents, and got no messages about anything wrong. Update: both SHORT and LONG tests passed for this drive in SeaTools. Hmph... the mystery remains. -Joe