From owner-freebsd-stable@FreeBSD.ORG Sat Aug 20 00:51:03 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 56142106566B for ; Sat, 20 Aug 2011 00:51:03 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-gw0-f54.google.com (mail-gw0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id 1912F8FC18 for ; Sat, 20 Aug 2011 00:51:02 +0000 (UTC) Received: by gwb15 with SMTP id 15so2352159gwb.13 for ; Fri, 19 Aug 2011 17:51:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=mthNhNDly5UeuehxGgrRZJoGGvFlzBzKGLh3/jP2/RU=; b=P2lh2vxgDkC8yPuWt2HSEIrPrLYgHu6CYUMTIi9OS1p+mhxx736x9V//SlygrMtUc7 O6ni74t7P7dnbjWwRVc8hAwzDmvk8bBcXBCiGo/rwm8fKEr7cS1JCpEzjLnkhWWaUGHK GdIjR3M9A6c51UVO6SdlarDDTNqlK1iPZzGu8= MIME-Version: 1.0 Received: by 10.150.236.9 with SMTP id j9mr36820ybh.167.1313801462341; Fri, 19 Aug 2011 17:51:02 -0700 (PDT) Received: by 10.151.98.3 with HTTP; Fri, 19 Aug 2011 17:51:02 -0700 (PDT) In-Reply-To: <20110819235719.GA64220@night.db.net> References: <1B4FC0D8-60E6-49DA-BC52-688052C4DA51@langille.org> <20110819235719.GA64220@night.db.net> Date: Fri, 19 Aug 2011 17:51:02 -0700 Message-ID: From: Kevin Oberman To: Dan Langille Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@freebsd.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: Sat, 20 Aug 2011 00:51:03 -0000 On Fri, Aug 19, 2011 at 4:57 PM, Diane Bruce wrote: > On Fri, Aug 19, 2011 at 04:50:01PM -0400, Dan Langille wrote: >> System in question: FreeBSD 8.2-STABLE #3: Thu Mar =A03 04:52:04 GMT 201= 1 >> >> After a recent power failure, I'm seeing this in my logs: >> >> Aug 19 20:36:34 bast smartd[1575]: Device: /dev/ad2, 2 Currently unreada= ble (pending) sectors >> > > Personally, I'd replace that drive now. > >> Searching on that error message, I was led to believe that identifying t= he bad sector and >> running dd to read it would cause the HDD to reallocate that bad block. > > No, as otherwise mentioned (Hi Jeremy!) you need to read and write the > block. This could buy you a few more days or a few more weeks. Personally= , > I would not wait. Your call. > While I largely agree, it depends on several factors as to whether I'd replace the drive. First, what does SMART show other then these errors? If the reported statistics look generally good, and considering that you a mirror with one "good" copy of the blocks in question, the impact is zero unless the other drive fails. That is why the blocks need to be re-written so that they will be re-located on the drive. Second, how critical is the data? The mirror gives good integrity, but you also need good backups. If the data MUST be on-line with high reliability, buy a replacement drive. You need to look at cost-benefit (or really the cost of replacement vs. cost of failure). It's worth mentioning that all drives have bad blocks. Most are hard bad blocks and are re-mapped before the drive is shipped, but marginal bad blocks can and do slip through to customers and it is entirely possible that the drive is just fine for the most part and replacing it is really a waste of money. Only you can make the call, but if further bad blocks show up in the near term, I'll go along with recommending replacement. --=20 R. Kevin Oberman, Network Engineer - Retired E-mail: kob6558@gmail.com