linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mario 'BitKoenig' Holbe <Mario.Holbe@TU-Ilmenau.DE>
To: linux-raid@vger.kernel.org
Subject: Re: Proactive Drive Replacement
Date: Tue, 21 Oct 2008 17:30:18 +0200	[thread overview]
Message-ID: <gdksib$nap$1@ger.gmane.org> (raw)
In-Reply-To: A20315AE59B5C34585629E258D76A97C025BF23B@34093-C3-EVS3.exchange.rackspace.com

David Lethe <david@santools.com> wrote:
> is correctly called the "SMART selective
> self-test routine".   By the way, this is an OFF-LINE scan.  

short, long, conveyance and selective tests are all offline.

> So bottom line, Mario is correct in that there is a way to get a PARTIAL
> list of bad blocks, if you have a disk
> that supports this command, and you're willing to run an off-line scan
> (not practical or a parity-protected RAID 
> environment).

Most modern (ATA) disks support "Suspend Offline collection upon new
command". Well, the tests take notably longer on a loaded disk and
(low-frequent) requests to that disk take notably longer as well
(high-frequent requests just keep the test suspended), but it works.

> It is possible that some vendor has implemented a SATA ON-LINE bad block
> scanning mechanism that reports results and
> doesn't kill I/O performance.  It would have to give full list of bad
> blocks, or at least startingblock + range.
>
> That would be wonderful as you could just read the list on regular
> interval and rebuild stripes as necessary. You'd have
> Self-healing parity.

echo check > /sys/block/mdx/md/sync_action

That's indeed way more powerful than any attempt to rely on any
S.M.A.R.T. thingy.


regards
   Mario
-- 
I thought the only thing the internet was good for was porn.  -- Futurama


  reply	other threads:[~2008-10-21 15:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-20 17:35 Proactive Drive Replacement Jon Nelson
2008-10-20 22:40 ` Mario 'BitKoenig' Holbe
2008-10-21  8:38   ` David Greaves
2008-10-21 13:05     ` Jon Nelson
2008-10-21 13:36       ` David Greaves
2008-10-21 13:50       ` David Lethe
2008-10-21 14:11         ` Mario 'BitKoenig' Holbe
2008-10-21 15:13           ` David Lethe
2008-10-21 15:30             ` Mario 'BitKoenig' Holbe [this message]
2008-10-21 19:39         ` David Greaves
2008-10-21 13:57     ` Mario 'BitKoenig' Holbe
2008-10-21 17:29       ` David Greaves
2008-10-24  5:57     ` Luca Berra
2008-10-24  8:09       ` David Greaves
2008-10-25 13:20         ` Luca Berra
2008-10-25 16:33           ` David Greaves

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='gdksib$nap$1@ger.gmane.org' \
    --to=mario.holbe@tu-ilmenau.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).