From: NeilBrown <neilb@suse.de>
To: Curtis <serverascode@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Determining if a stripe/RAID0 has failed
Date: Wed, 10 Jul 2013 07:46:09 +1000 [thread overview]
Message-ID: <20130710074609.37ff918d@notabene.brown> (raw)
In-Reply-To: <CAJ_JamCpdFHRyYOzEg=yH4k_rv0KnZD8UJ_GwvSrSmHHOSzFAA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1064 bytes --]
On Tue, 9 Jul 2013 15:33:29 -0600 Curtis <serverascode@gmail.com> wrote:
> Hi All,
>
> I'm wondering what the best way to determine when a RAID0 has failed?
>
> We have some stateless servers that use a stripe/RAID0, but we'll need
> to know if it failed so we can pull it out of the "cluster" and
> rebuild it. It would be better to find out sooner than later that the
> stripe has failed.
>
> I know from reading the man page that I can't use mdadm to monitor the
> stripe. Is it basically just that the device becomes unusable in some
> fashion?
>
How would you determine if a lone drive had failed?
Presumably by error messages in the kernel logs, or similar.
Use exactly the same mechanism to test if a RAID0 has failed.
(A "RAID0" doesn't fail as whole. Bits of it might, other bits might keep
working, just like a drive which can lose some sectors but other sectors keep
working. Certainly a whole drive can fail if it's logic-board dies.
Similarly a whole RAID0 can fail if the SATA/SCSI/USB controller dies.)
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2013-07-09 21:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-09 21:33 Determining if a stripe/RAID0 has failed Curtis
2013-07-09 21:46 ` NeilBrown [this message]
2013-07-09 21:52 ` Curtis
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=20130710074609.37ff918d@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=serverascode@gmail.com \
/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.