All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Herbszt <herbszt@gmx.de>
To: NeilBrown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org, Sebastian Herbszt <herbszt@gmx.de>
Subject: Re: How to identify a failed md array
Date: Sun, 1 Jun 2014 19:23:39 +0200	[thread overview]
Message-ID: <20140601192339.000062d9@localhost> (raw)
In-Reply-To: <20140529151851.2508bdb6@notabene.brown>

NeilBrown wrote:
> 
> On Mon, 26 May 2014 20:07:11 +0200 Sebastian Herbszt <herbszt@gmx.de> wrote:
> 

[snip]

> > How can I identify a failed array?
> > array_state reports "clean", the last raid member stays "in_sync" and
> > the value in degraded doesn't equal raid_disks.
> 
> You know the array is "failed" when you get an IO error.
> 
> When a RAID1 array gets down to just one drive remaining, it starts acting
> like it is just one drive.
> How do you tell if is single plain ordinary drive is failed?  You get an IO
> error.  ditto with RAID1.
> 
> NeilBrown
> 

Since md knows the current state I hoped it would provide the required
information for an application to distinguish between degraded and failed
arrays. Any reason this is not the case?
This would allow mdadm to not only report "DegradedArray" but also
"FailedArray". Currently it does not generate any event when the last drive
fails.

Sebastian

  reply	other threads:[~2014-06-01 17:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-26 18:07 How to identify a failed md array Sebastian Herbszt
2014-05-29  5:18 ` NeilBrown
2014-06-01 17:23   ` Sebastian Herbszt [this message]
2014-06-01 22:54     ` NeilBrown

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=20140601192339.000062d9@localhost \
    --to=herbszt@gmx.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    /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.