From: Stephan Stachurski <ses1984@gmail.com>
To: linux-raid@vger.kernel.org
Subject: Re: Can't re-assemble successfully after creation, initial sync and reboot
Date: Wed, 20 Jan 2010 08:24:22 -0500 [thread overview]
Message-ID: <959332b61001200524j7a879f15u5281e03b1da2cd43@mail.gmail.com> (raw)
In-Reply-To: <959332b61001180933n638b9255k5aa540be024f2e6f@mail.gmail.com>
Ok, I tried a couple of things, so far with no success.
I re-created the array, let it synchronize, then rebooted. When I
first created the array, the components devices looked like this:
md0 : active raid5 sda[0] sdb[1] sdc[2] sdd[3]
When I rebooted, it suddenly comes up like this, skipping component device 3:
md0 : active raid5 sda[0] sdd[4] sdb[1] sdc[2]
and it was automatically resyncing, destroying the last 6 hours I was
waiting for it to initially sync, and it changed my chunk size! Why do
I keep getting these problems?
On Mon, Jan 18, 2010 at 12:33 PM, Stephan Stachurski <ses1984@gmail.com> wrote:
> I'm having problems with an array that I just created. It's a raid
> level 5 with 4 devices using all of the default settings. I'm using
> the version of mdadm that's included in ubuntu 9.10 repositories.
>
> When I reboot the machine, /proc/mdstat shows this:
> md_d0 : inactive sdc[2](S)
>
> I can stop the device, and attempt the --assemble the array correctly,
> but something still is wrong:
>
> $ sudo mdadm --stop /dev/md_d0
> mdadm: stopped /dev/md_d0
> $ sudo mdadm --assemble /dev/md0 -fv /dev/sda /dev/sdb /dev/sdc /dev/sdd
> mdadm: looking for devices for /dev/md0
> mdadm: /dev/sda is identified as a member of /dev/md0, slot 0.
> mdadm: /dev/sdb is identified as a member of /dev/md0, slot 1.
> mdadm: /dev/sdc is identified as a member of /dev/md0, slot 2.
> mdadm: /dev/sdd is identified as a member of /dev/md0, slot 3.
> mdadm: added /dev/sdb to /dev/md0 as 1
> mdadm: added /dev/sdc to /dev/md0 as 2
> mdadm: added /dev/sdd to /dev/md0 as 3
> mdadm: added /dev/sda to /dev/md0 as 0
> mdadm: /dev/md0 has been started with 3 drives (out of 4).
> $ sudo cat /proc/mdstat
> md0: active raid5 sda[0] sdc[2] sdb[1]
> 2930287488 blocks level 5, 128k chunk, algorithm 2 [4/3] [UUU_]
>
> md_d0: inactive sdd[3](S)
> 976762496 blocks
>
> Why, if it correctly identifies the devices that are members of
> /dev/md0, and then adds them to /dev/md0, do I not get the complete
> array?
> --
> Stephan E Stachurski
>
next prev parent reply other threads:[~2010-01-20 13:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-18 17:33 Can't re-assemble successfully after creation, initial sync and reboot Stephan Stachurski
2010-01-20 13:24 ` Stephan Stachurski [this message]
2010-01-20 13:32 ` Majed B.
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=959332b61001200524j7a879f15u5281e03b1da2cd43@mail.gmail.com \
--to=ses1984@gmail.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).