Thread (15 messages) 15 messages, 4 authors, 2010-10-01

Re: raid5+hotspare: request for recommended procedure

From: Jon Hardcastle <hidden>
Date: 2010-09-29 15:39:28

--- On Wed, 29/9/10, Stefan G. Weichinger <lists@xunil.at> wrote:
From: Stefan G. Weichinger <redacted>
Subject: Re: raid5+hotspare: request for recommended procedure
To: "linux-raid@vger.kernel.org" <redacted>
Cc: Jon@eHardcastle.com, "Jon Hardcastle" <redacted>
Date: Wednesday, 29 September, 2010, 16:08
Am 2010-09-29 16:29, schrieb Jon
Hardcastle:
quoted
Personally I would trust nothing less than a dammed
good thrashing 
quoted
from badblocks -svw ideally or -svn if the drive has
data on it.
quoted
Then an smart offline check to be sure the
pending/reallocated
quoted
sector counts have no increased.

Before commissioning a new drive a do a badblocks -svw
atleast 3 
quoted
times without any counters increasing (something there
are bad 
quoted
sectors I just want to flush them out early) then I do
some short, 
quoted
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
This step is run on the drives that form the array so sdb... and it can take a long time.. depends on how many times you run it through and how the drive is connected...


      
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help