linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ming Zhang <mingz@ele.uri.edu>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: raid0 fail to detect drive failure
Date: Wed, 02 Nov 2005 08:40:47 -0500	[thread overview]
Message-ID: <1130938847.9447.111.camel@localhost.localdomain> (raw)
In-Reply-To: <4368822A.4050400@tls.msk.ru>

On Wed, 2005-11-02 at 12:08 +0300, Michael Tokarev wrote:
> Ming Zhang wrote:
> > Hi folks
> > 
> > I have a raid0 on top of 2 sata disk sda and sdb. after i hot unplug
> > sda, the raid0 still shows online and active. run dd to write to it will
> > fail and dmesg shows scsi io error. but /proc/mdstat shows everything is
> > ok.
> 
> Since raid0 isn't relly raid (as Redundrand) and can't really do
> anything with IO errors on component devices, this behaviour
> (returning IO errors to the application) is the only sane way
> to go.  It should not fail just like when your disk drive has
> a bad sector on it, the whole partition (or whole disk) with
> that bad sector isn't "marked as failed".  So what you see is
> exactly correct behaviour, in my opinion anyway.
> 
> /mjt

after I sent email, I read the raid0 code and there is no error handling
at all, so i knew why it looks like that. 

for my case, 2 disk raid0, 1 disk broke mean 50% sectors on a disk are
bad. i would like to call that disk a failed disk. and i bet you will
not use such disk any more even you call it not-failed disk. ;)

but as you said, raid0 is not a real raid, so maybe this is why no error
check here.

thanks!

Ming



      reply	other threads:[~2005-11-02 13:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-01 16:02 raid0 fail to detect drive failure Ming Zhang
2005-11-02  9:08 ` Michael Tokarev
2005-11-02 13:40   ` Ming Zhang [this message]

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=1130938847.9447.111.camel@localhost.localdomain \
    --to=mingz@ele.uri.edu \
    --cc=linux-raid@vger.kernel.org \
    --cc=mjt@tls.msk.ru \
    /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).