From owner-freebsd-current@FreeBSD.ORG Fri Dec 18 10:39:27 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 56FD5106566B for ; Fri, 18 Dec 2009 10:39:27 +0000 (UTC) (envelope-from alexz@visp.ru) Received: from mail.visp.ru (srv1.visp.ru [91.215.204.2]) by mx1.freebsd.org (Postfix) with ESMTP id 066588FC13 for ; Fri, 18 Dec 2009 10:39:26 +0000 (UTC) Received: from 91-215-205-255.static.visp.ru ([91.215.205.255] helo=zagrebin) by mail.visp.ru with esmtp (Exim 4.66 (FreeBSD)) (envelope-from ) id 1NLaF3-00062X-UL; Fri, 18 Dec 2009 13:39:25 +0300 From: "Alexander Zagrebin" To: "'Daniel O'Connor'" References: <39309F560B98453EBB9AEA0F29D9D80E@vosz.local><4C1C2598-4157-4B04-8DB8-C84F353AB8B8@nevada.net.nz><6FAA390A-1E40-4D7A-AAD5-DC72578CE974@nevada.net.nz> <200912182027.11632.doconnor@gsoft.com.au> Date: Fri, 18 Dec 2009 13:39:25 +0300 Keywords: freebsd-current Message-ID: <5C4BD0F81D1348B287B2ECD55EF283E1@vosz.local> MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 Thread-Index: Acp/yJtZzlq7sDI3RmqTpeKIApYg/AAAwuFw X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5512 In-Reply-To: <200912182027.11632.doconnor@gsoft.com.au> Cc: freebsd-current@freebsd.org Subject: RE: 8.0-RELEASE: disk IO temporarily hangs up (ZFS or ATA related problem) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Dec 2009 10:39:27 -0000 > I doubt this is the problem, I have WD10EADS disks in my ZFS > array and I > see the same issue. > > It strikes me as extremely unlikely that both of us would have dud > disks.. > > In any case it seems to be a general problem not limited to > one area of > the disk so a dud sector is an unlikely reason. Big thanks for confirmation! Your confirmation is important for me. There should be a way to define where the bug is: in the ata (or filesystem) driver or in the drive's firmware.... -- Alexander Zagrebin