All of lore.kernel.org
 help / color / mirror / Atom feed
From: Durval Menezes <durval.menezes@gmail.com>
To: Brad Campbell <lists2009@fnarfbargle.com>
Cc: Brad Campbell <brad@fnarfbargle.com>,
	linux-raid@vger.kernel.org, Drew <drew.kay@gmail.com>
Subject: Re: Maximizing failed disk replacement on a RAID5 array
Date: Mon, 13 Jun 2011 02:56:47 -0300	[thread overview]
Message-ID: <BANLkTin58zxkr1GRut+kZTSe3RmAfFZbug@mail.gmail.com> (raw)
In-Reply-To: <4DEF2B59.7090408@fnarfbargle.com>

Hello Brad, folks,

On Wed, Jun 8, 2011 at 4:57 AM, Brad Campbell <lists2009@fnarfbargle.com> wrote:
> On 08/06/11 15:47, Durval Menezes wrote:
>
>> I'm sorry if I did not make myself clear; I've already run both a
>> "repair" on the RAID  (see above) and a "smart -t long" on the
>> particular disk... I had about 40 bad sectors before, and now have
>> just 4, but these 4 sectors persist as being marked in error... I
>> think the "RAID repair" didn't touch them.
[...]
> I've never had md not report a repaired sector when performing a repair
> operation.

Just to keep you posted: after I finished replacing that failing disk,
I wrote zeroes to all its sectors (dd bs=16065b </dev/zero >/dev/DISK)
and then checked SMART again.

Guess what? As expected, the 4 sectors that were being reported in
both "Current_Pending_Sector" and "Offline_Uncorrectable" just went
away... both counters now report a big round  "0".

So, it seems my hypothesis that these sectors were not being touched
by the md "repair" was indeed correct: once they were written to, they
ended up being automatically remapped (or at least cleaned out of the
above counters) by the HD firmware. Also, as the array resync reported
no errors whatsoever, it seems these sectors were simply not being
used by md.

Anyone has a good explanation to that? Inquiring minds want to know... :-)

Cheers,
-- 
   Durval Menezes.
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2011-06-13  5:56 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BANLkTimBYFhjQ-sC9DhTMO+PG-Ox+A9S2Q@mail.gmail.com>
2011-06-05 14:22 ` Fwd: Maximizing failed disk replacement on a RAID5 array Durval Menezes
2011-06-06 15:02   ` Drew
2011-06-06 15:20     ` Brad Campbell
2011-06-06 15:37       ` Drew
2011-06-06 15:54         ` Brad Campbell
2011-06-06 18:06           ` Durval Menezes
2011-06-07  5:03             ` Durval Menezes
2011-06-07  5:35               ` Brad Campbell
2011-06-08  6:58                 ` Durval Menezes
2011-06-08  7:32                   ` Brad Campbell
2011-06-08  7:47                     ` Durval Menezes
2011-06-08  7:57                       ` Brad Campbell
     [not found]                         ` <BANLkTi=BuXK4SBGR=FrEcHFC1WohNkUY7g@mail.gmail.com>
     [not found]                           ` <4DEF7775.5020407@fnarfbargle.com>
     [not found]                             ` <BANLkTin8dpbxWfSCG_VoOM_FMmqCkm2mJg@mail.gmail.com>
2011-06-13  5:32                               ` Durval Menezes
2011-06-13  5:56                         ` Durval Menezes [this message]
2011-06-07  8:52             ` John Robinson
2011-06-10 10:25               ` John Robinson
2011-06-11 22:35                 ` Durval Menezes

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BANLkTin58zxkr1GRut+kZTSe3RmAfFZbug@mail.gmail.com \
    --to=durval.menezes@gmail.com \
    --cc=brad@fnarfbargle.com \
    --cc=drew.kay@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=lists2009@fnarfbargle.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.