From: Peter Rabbitson <rabbit+list@rabbit.us>
To: Sean Hildebrand <silverwraithii@gmail.com>
Cc: David Greaves <david@dgreaves.com>, linux-raid@vger.kernel.org
Subject: Re: Rebuilding an array with a corrupt disk.
Date: Sun, 15 Jun 2008 17:09:28 +0200 [thread overview]
Message-ID: <485530A8.3050601@rabbit.us> (raw)
In-Reply-To: <fa037c550806150454v68089bcbg50203b454ae593e0@mail.gmail.com>
Sean Hildebrand wrote:
>
> <snip>
>
>
> To answer that: The drive was brand new. The thing I find odd about
> this failure is that it was integrated into the array without issue,
> meaning the disk has no issues writing to the bad sectors, just
> reading. Never had that before.
>
> In any case, I'm very glad to have got my data with minimal loss. And
> to think, all this could have been avoided if I'd just made my array a
> RAID6 when it was first built. Certainly when I have a new fifth disk
> the array will be rebuilt as such.
>
When you get your new disk (or any disk for that matter) run badblocks -svw on
it. It takes about 8 hours on average drive sizes today, but guards precisely
against the problem you faced. Additionally the drive will receive a hefty
does of "break in", so you know it performed well under stress at least for
several hours.
next prev parent reply other threads:[~2008-06-15 15:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-14 2:22 Rebuilding an array with a corrupt disk Sean Hildebrand
2008-06-14 6:21 ` David Greaves
2008-06-14 10:54 ` Sean Hildebrand
2008-06-14 11:47 ` David Greaves
2008-06-15 11:54 ` Sean Hildebrand
2008-06-15 13:32 ` David Greaves
2008-06-15 15:09 ` Peter Rabbitson [this message]
2008-06-19 4:57 ` Neil Brown
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=485530A8.3050601@rabbit.us \
--to=rabbit+list@rabbit.us \
--cc=david@dgreaves.com \
--cc=linux-raid@vger.kernel.org \
--cc=silverwraithii@gmail.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.