From owner-freebsd-stable@FreeBSD.ORG Sun Aug 21 02:13:19 2011 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 68D771065670 for ; Sun, 21 Aug 2011 02:13:19 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (agora.rdrop.com [IPv6:2607:f678:1010::34]) by mx1.freebsd.org (Postfix) with ESMTP id 452768FC13 for ; Sun, 21 Aug 2011 02:13:19 +0000 (UTC) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id p7L2DH8v092487 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 20 Aug 2011 19:13:18 -0700 (PDT) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id p7L2DHoJ092486; Sat, 20 Aug 2011 19:13:17 -0700 (PDT) Received: from fbsd81 ([192.168.200.81]) by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA20887; Sat, 20 Aug 11 19:00:55 PDT Date: Sun, 21 Aug 2011 02:00:33 -0700 From: perryh@pluto.rain.com To: freebsd@jdc.parodius.com Message-Id: <4e50c931.gCNlQFqn5sVQXXax%perryh@pluto.rain.com> References: <1B4FC0D8-60E6-49DA-BC52-688052C4DA51@langille.org> <20110819232125.GA4965@icarus.home.lan> <20110820032438.GA21925@icarus.home.lan> <4774BC00-F32B-4BF4-A955-3728F885CAA1@langille.org> <4E4FF4D6.1090305@os2.kiev.ua> <20110820183456.GA38317@icarus.home.lan> In-Reply-To: <20110820183456.GA38317@icarus.home.lan> User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: ml@os2.kiev.ua, freebsd-stable@freebsd.org, dan@langille.org Subject: Re: bad sector in gmirror HDD 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: Sun, 21 Aug 2011 02:13:19 -0000 Jeremy Chadwick wrote: > ... using dd to find the bad LBAs is the only choice he has. or sysutils/diskcheckd. It uses a 64KB blocksize, falling back to 512 -- to identify the bad LBA(s) -- after getting a failure when reading a large block, and IME it runs something like 10x faster than dd with bs=64k. It would be advisable to check syslog configuration before using diskcheckd, since that is how it reports and there is reason to suspect that the as-shipped syslog.conf may discard at least some of diskcheckd's messages.