linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Colin Simpson" <csimpson@csl.co.uk>
To: David Rees <drees76@gmail.com>
Cc: Richard Scobie <richard@sauce.co.nz>,
	Linux RAID Mailing List <linux-raid@vger.kernel.org>
Subject: Re: Linux Software RAID a bit of a weakness?
Date: Mon, 26 Feb 2007 17:26:58 +0000	[thread overview]
Message-ID: <1172510818.11898.33.camel@cowie> (raw)
In-Reply-To: <72dbd3150702260856p5053d028je85cacffb15a5536@mail.gmail.com>


On Mon, 2007-02-26 at 08:56 -0800, David Rees wrote:
>
> > You could configure smartd to do regular long selftests, which would
> > notify you on failures and allow you to take the drive offline and dd,
> > replace etc.
> 
> So what do you do when your drives in your array don't support SMART
> self tests for some reason?
> 
> The best solution I have thought of so far is to do a `dd if=/dev/mdX
> of=/dev/null` periodically, but this isn't as nice as running a check
> in the later kernels as it's not guaranteed to read blocks from all
> disks. I guess you could instead do the same thing but with the
> underlying disks instead of the raid device, then make sure you watch
> the logs for disk read errors.
> 
> -Dave

SATA isn't supported on RH 4's SMART.

If I say, 

dd if=/dev/sda2 of=/dev/null

where /dev/sda2 is a component of an active md device.

Will the RAID subsystem get upset that someone else is fiddling with the
disk (even in just a read only way)? And will a read error on this dd
(caused by a bad block) cause md to knock out that device?

Thanks

Colin

This email and any files transmitted with it are confidential and are intended solely for the use of the individual or entity to whom they are addressed.  If you are not the original recipient or the person responsible for delivering the email to the intended recipient, be advised that you have received this email in error, and that any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. If you received this email in error, please immediately notify the sender and delete the original.



  reply	other threads:[~2007-02-26 17:26 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
2007-02-26 16:56       ` David Rees
2007-02-26 17:26         ` Colin Simpson [this message]
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=1172510818.11898.33.camel@cowie \
    --to=csimpson@csl.co.uk \
    --cc=drees76@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=richard@sauce.co.nz \
    /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).