linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Scobie <richard@sauce.co.nz>
To: Linux RAID Mailing List <linux-raid@vger.kernel.org>
Subject: Re: Linux Software RAID a bit of a weakness?
Date: Mon, 26 Feb 2007 10:02:24 +1300	[thread overview]
Message-ID: <45E1F960.4090603@sauce.co.nz> (raw)
In-Reply-To: <Pine.LNX.4.64.0702251504090.21918@coffee.psychology.mcmaster.ca>

Mark Hahn wrote:

> is it known what a long self-test does?  for instance, ultimately you
> want the disk to be scrubbed over some fairly lengthy period of time.
> that is, not just read and checked, possibly with parity "fixed",
> but all blocks read and rewritten (with verify, I suppose!)

The smartctl man page is a little vague, but it looks like it does no 
writing.


Paraphrasing somewhat:

short selftest - The  "Self"  tests check  the  electrical and 
mechanical performance as well as the read performance of the disk.

long selftest - This is a  longer  and  more  thorough version  of the 
Short Self Test described above.

Richard

  reply	other threads:[~2007-02-25 21:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-23 19:19 Linux Software RAID a bit of a weakness? Colin Simpson
2007-02-23 19:55 ` Steve Cousins
2007-02-23 20:08   ` Justin Piszcz
2007-02-25 12:24   ` Colin Simpson
2007-02-25 19:15     ` Richard Scobie
2007-02-25 20:08       ` Mark Hahn
2007-02-25 21:02         ` Richard Scobie [this message]
2007-02-26 16:56       ` David Rees
2007-02-26 17:26         ` Colin Simpson
2007-02-26 19:40           ` Joshua Baker-LePain
2007-02-26 21:13           ` David Rees
2007-02-26 21:22             ` Neil Brown
2007-02-27 20:12               ` David Rees
2007-02-26 22:38           ` Jeff Garzik
2007-02-27  4:10         ` berk walker
2007-02-23 20:25 ` Neil Brown
2007-02-24  4:14   ` Richard Scobie
2007-02-25 20:08 ` Bill Davidsen

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=45E1F960.4090603@sauce.co.nz \
    --to=richard@sauce.co.nz \
    --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).