linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: evoltech@2inches.com
To: linux-raid@vger.kernel.org
Subject: Re: /proc/mdstat showing a device missing from array
Date: Mon, 14 May 2007 12:42:11 -0700	[thread overview]
Message-ID: <1179171731.4648bb938d688@mail.2inches.com> (raw)
In-Reply-To: <17991.46650.304434.640289@notabene.brown>

Quoting Neil Brown <neilb@suse.de>:

> On Sunday May 13, evoltech@2inches.com wrote:
> > 
> > 
> > Hello all,
> > 
> > I just set up a new raid 5 array of 4 750G disks and am having a strange
> > experience where /proc/mdstat is showing that one device is missing from
> the
> > array.  The output from a "--detail" shows that there is some unnamed
> device
> > that has been removed from the array and I don't understand why or how to
> fix
> > it.  Can someone please shed some light?
> 
> A raid5 is always created with one missing device and one spare.  This
> is because recovery onto a spare is faster than resync of a brand new
> array.

This is unclear to me.  Do you mean that is how mdadm implements raid5 creation
 or do you mean that is how raid5 is designed?  I havn't read about this in any
raid5 documentation or mdadm documentation.  Can you point me in the right
direction?

> 
> The real problem here is that recovery has not started.
> If you 
>   mdadm -S /dev/md2
>   mdadm -A /dev/md2 /dev/sd[def]
>   mdadm /dev/md2 -a /dev/sdg
> it will start recovery.
> 
> This bug was fixed in mdadm-2.5.2

The recovery of the array has started, thanks!

Sincerely,
Dennison Williams

  reply	other threads:[~2007-05-14 19:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-13 18:33 /proc/mdstat showing a device missing from array evoltech
2007-05-14  1:07 ` Neil Brown
2007-05-14 19:42   ` evoltech [this message]
2007-05-14 23:35     ` Neil Brown

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=1179171731.4648bb938d688@mail.2inches.com \
    --to=evoltech@2inches.com \
    --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).