From: "Stefan G. Weichinger" <lists@xunil.at>
To: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Cc: Jon@eHardcastle.com, Jon Hardcastle <jd_hardcastle@yahoo.com>
Subject: Re: raid5+hotspare: request for recommended procedure
Date: Wed, 29 Sep 2010 17:08:10 +0200 [thread overview]
Message-ID: <4CA3565A.8050802@xunil.at> (raw)
In-Reply-To: <285938.34612.qm@web51302.mail.re2.yahoo.com>
Am 2010-09-29 16:29, schrieb Jon Hardcastle:
> Personally I would trust nothing less than a dammed good thrashing
> from badblocks -svw ideally or -svn if the drive has data on it.
> Then an smart offline check to be sure the pending/reallocated
> sector counts have no increased.
>
> Before commissioning a new drive a do a badblocks -svw atleast 3
> times without any counters increasing (something there are bad
> sectors I just want to flush them out early) then I do some short,
> long and offline smart tests.
>
> Then I add to the array, then I run check a couple of times.
To be explicit:
This would mean to run "badblocks -svn" on md3 or sdb or sdb3 ?
just to make sure I understand you correctly ...
Does that step take long?
Stefan
next prev parent reply other threads:[~2010-09-29 15:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-29 9:03 raid5+hotspare: request for recommended procedure Stefan G. Weichinger
2010-09-29 10:03 ` Tim Small
2010-09-29 10:06 ` Tim Small
2010-09-29 12:42 ` Stefan G. Weichinger
2010-09-29 14:25 ` Stefan G. Weichinger
2010-09-29 14:29 ` Jon Hardcastle
2010-09-29 15:08 ` Stefan G. Weichinger [this message]
2010-09-29 15:39 ` Jon Hardcastle
2010-09-30 9:50 ` Stefan G. Weichinger
2010-10-01 9:00 ` Stefan G. Weichinger
2010-10-01 9:59 ` Stefan G. Weichinger
2010-10-01 21:20 ` Stefan G. Weichinger
2010-09-29 12:01 ` Michael Tokarev
2010-09-29 12:21 ` Tim Small
2010-09-29 12:38 ` Stefan G. Weichinger
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=4CA3565A.8050802@xunil.at \
--to=lists@xunil.at \
--cc=Jon@eHardcastle.com \
--cc=jd_hardcastle@yahoo.com \
--cc=linux-raid@vger.kernel.org \
/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.