Linux RAID subsystem development
 help / color / mirror / Atom feed
From: "NeilBrown" <neilb@suse.de>
To: Federico <undicizeri@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: mdadm raid1 stops to work after kernel panic
Date: Mon, 5 May 2008 21:41:54 +1000 (EST)	[thread overview]
Message-ID: <54900.192.168.1.70.1209987714.squirrel@neil.brown.name> (raw)
In-Reply-To: <26c008d70805050256q65972fa7jb86c6d5254828fc1@mail.gmail.com>

[please don't drop the list from the cc: line - I've re-added it]

On Mon, May 5, 2008 7:56 pm, Federico wrote:
> wax@persifae:~$sudo !!
> sudo mdadm --examine /dev/sda1 /dev/sdc1

Thanks.  That looks fairly normal.  sda1 is thought to be out-of-date
so you would expect mdadm to assemble the array with just sdc1
as a member.  You would then need to add sda1 as a spare and it would
rebuild.
I wonder why it isn't including sdc1 at first.

What happens if you:
  mdadm -S /dev/md2
  mdadm -A /dev/md2 /dev/sda1 /dev/sdc1
??

NeilBrown


> Parola d'ordine:
> /dev/sda1:
>           Magic : a92b4efc
>         Version : 00.90.00
>            UUID : 62a5cb51:36ca61a3:1298e6c2:30fde3ba
>   Creation Time : Mon May  5 04:39:59 2008
>      Raid Level : raid1
>   Used Dev Size : 293049600 (279.47 GiB 300.08 GB)
>      Array Size : 293049600 (279.47 GiB 300.08 GB)
>    Raid Devices : 2
>   Total Devices : 2
> Preferred Minor : 2
>
>     Update Time : Mon May  5 06:15:31 2008
>           State : active
>  Active Devices : 2
> Working Devices : 2
>  Failed Devices : 0
>   Spare Devices : 0
>        Checksum : 27e6bd76 - correct
>          Events : 0.9
>
>
>       Number   Major   Minor   RaidDevice State
> this     0       8        1        0      active sync   /dev/sda1
>
>    0     0       8        1        0      active sync   /dev/sda1
>    1     1       8       33        1      active sync   /dev/sdc1
> /dev/sdc1:
>           Magic : a92b4efc
>         Version : 00.90.00
>            UUID : 62a5cb51:36ca61a3:1298e6c2:30fde3ba
>   Creation Time : Mon May  5 04:39:59 2008
>      Raid Level : raid1
>   Used Dev Size : 293049600 (279.47 GiB 300.08 GB)
>      Array Size : 293049600 (279.47 GiB 300.08 GB)
>    Raid Devices : 2
>   Total Devices : 1
> Preferred Minor : 0
>
>     Update Time : Mon May  5 09:16:19 2008
>           State : active
>  Active Devices : 1
> Working Devices : 1
>  Failed Devices : 0
>   Spare Devices : 0
>        Checksum : 27e6e7e5 - correct
>          Events : 0.11
>
>
>       Number   Major   Minor   RaidDevice State
> this     1       8       33        1      active sync   /dev/sdc1
>
>    0     0       0        0        0      removed
>    1     1       8       33        1      active sync   /dev/sdc1
>


  parent reply	other threads:[~2008-05-05 11:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-05  6:47 mdadm raid1 stops to work after kernel panic Federico
2008-05-05  9:32 ` NeilBrown
     [not found]   ` <26c008d70805050256q65972fa7jb86c6d5254828fc1@mail.gmail.com>
2008-05-05 11:41     ` NeilBrown [this message]
2008-05-05 12:09       ` Federico
2008-05-06  2:50         ` Neil Brown
2008-05-06  5:46           ` Federico

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=54900.192.168.1.70.1209987714.squirrel@neil.brown.name \
    --to=neilb@suse.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=undicizeri@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox