linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Neil Brown <neilb@cse.unsw.edu.au>
To: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Software RAID Stopped Working With Aurora Kernel
Date: Wed, 22 May 2002 09:51:55 +1000 (EST)	[thread overview]
Message-ID: <15594.56731.169389.603464@notabene.cse.unsw.edu.au> (raw)
In-Reply-To: message from Calvin D. Webster on Tuesday May 21

On Tuesday May 21, cwebster@ec.rr.com wrote:
> 
> There is only one thing that doesn't look right to me. That is the
> contents of "/proc/mdstat".
> The device numbers seem mismatched to their device names.
> 
> Also, different from what I'm used to seeing, is that the spare drive
> (sdc1) is not shown in the "active" list as it was before.

It is not there because you didn't tell "mdadm --assemble" about it.
mdadm will only assemble the drives that you give it.  It doesn't
matter what order you give them, but you should list all the drives
that part of the array (live or spare).
You can hot add /dev/sdc1 back in with
   mdadm /dev/md0 --add /dev/sdc1
or
   raidhotadd /dev/md0 /dev/sdc1

> 
> ## /proc/mdstat before (with 2.2 kernel):
> 
> ----------------------------------------------------------------------------------
> Personalities : [raid5]
> read_ahead 1024 sectors
> md0 : active raid5 sdf1[5] sde1[4] sdd1[3] sdc1[2] sdb1[1] sda1[0]
> 70726656 bloc
> ks level 5, 128k chunk, algorithm 0 [5/5] [UUUUU]
> unused devices: <none>
> ----------------------------------------------------------------------------------
> 
> ## /proc/mdstat after (with 2.4 kernel, fixed with mdadm):
> 
> ----------------------------------------------------------------------------------
> Personalities : [raid5] 
> read_ahead 1024 sectors
> md0 : active raid5 sda1[4] sde1[3] sdd1[2] sdf1[1] sdb1[0]
>       70726656 blocks level 5, 128k chunk, algorithm 0 [5/5] [UUUUU]
>       
> unused devices: <none>
> ----------------------------------------------------------------------------------

I don't know what caused the different numbering.  However as the raid
drive is clearly putting the right disks in the right places I
wouldn't worry about it.

I'm glad all went well.

NeilBrown

  reply	other threads:[~2002-05-21 23:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-19 23:38 Software RAID Stopped Working With Aurora Kernel Calvin Webster
2002-05-20 11:26 ` Neil Brown
2002-05-20 19:25   ` Cal Webster
2002-05-20 21:09     ` Neil Brown
2002-05-20 21:33       ` Calvin D. Webster
2002-05-21 11:24   ` Calvin D. Webster
2002-05-21 12:10     ` Neil Brown
2002-05-21 17:30       ` Cal Webster
2002-05-21 20:46         ` Neil Brown
2002-05-21 22:12           ` Calvin D. Webster
2002-05-21 23:51             ` Neil Brown [this message]
2002-05-22 12:00               ` Calvin D. Webster
2002-05-27  4:59                 ` Neil Brown
2002-05-29 13:07                   ` Calvin Webster
2002-05-29 23:16                     ` 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=15594.56731.169389.603464@notabene.cse.unsw.edu.au \
    --to=neilb@cse.unsw.edu.au \
    --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).