All of lore.kernel.org
 help / color / mirror / Atom feed
From: EJ Vincent <ej@ejane.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: raid/device failure
Date: Sun, 10 Feb 2013 21:52:15 -0500	[thread overview]
Message-ID: <51185CDF.8000007@ejane.org> (raw)
In-Reply-To: <511852EF.9070201@turmel.org>

On 2/10/2013 9:09 PM, Phil Turmel wrote:
> Have these drives ever been scrubbed? (I vaguely recall you mentioning 
> new drives...) If they are new and already had a URE, I'd be concerned 
> about mishandling during shipping. If they aren't new, I'd 
> destructively exercise them and retest.

Hi Phil,

Could you elaborate on procedures and tools to thoroughly exercise newly 
purchased drives? Are you talking about programs such as 'badblocks'?

Thanks.

-EJ


  reply	other threads:[~2013-02-11  2:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-11  1:27 raid/device failure Thomas Fjellstrom
2013-02-11  2:09 ` Phil Turmel
2013-02-11  2:52   ` EJ Vincent [this message]
2013-02-11  3:44     ` Phil Turmel
2013-02-11 20:28       ` EJ Vincent
2013-02-11  2:55   ` Thomas Fjellstrom
2013-02-11  3:22 ` Brad Campbell
2013-02-11  7:55   ` Thomas Fjellstrom
2013-02-11  8:29 ` Roy Sigurd Karlsbakk
2013-02-11  9:13   ` Thomas Fjellstrom
2013-02-12 22:31 ` Thomas Fjellstrom

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=51185CDF.8000007@ejane.org \
    --to=ej@ejane.org \
    --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.