From: Xavier Brochard <xavier@alternatif.org>
To: hansbkk@gmail.com
Cc: linux-raid@vger.kernel.org
Subject: Re: disk order problem in a raid 10 array
Date: Fri, 18 Mar 2011 21:12:49 +0100 [thread overview]
Message-ID: <201103182112.49660.xavier@alternatif.org> (raw)
In-Reply-To: <AANLkTin0L4wV3uFFhkeWPptvEddsS5ZntxVx51x2rjW_@mail.gmail.com>
Le vendredi 18 mars 2011 18:22:34 hansbkk@gmail.com, vous avez écrit :
> On Fri, Mar 18, 2011 at 9:49 PM, Xavier Brochard <xavier@alternatif.org>
wrote:
> > disk order is mixed between each boot - even with live-cd.
> > is that normal?
>
> If nothing is changing and the order is swapping really every boot,
> then IMO that is odd.
nothing has changed, except kernel minor version
>
> Part of my SOP is now to record both mdadm and the boot loader's
> ordering against serial number and UUID of drives when creating an
> array, and to put the relevant information on labels securely attached
> to the physical drives, along with creating a map of their physical
> location and taping that inside the case.nt
>
> It's critical to know what's what in a crisis. . .
exactly, in my case mdadm --examine output is somewhat weird as it shows:
/dev/sde1
this 0 8 33 0 active sync /dev/sdd1
/dev/sdd1
this 0 8 33 0 active sync /dev/sdc1
/dev/sdc1
this 0 8 33 0 active sync /dev/sde1
and /dev/sdf1 as sdf1
I think I can believe mdadm?
and that /proc/mdstat content comes directly from mdadm (that is with "exact"
sdc,d,e)?
what trouble me is that after I removed 2 disk drive from the bay, mdadm start
to recover:
md0 : active raid10 sdb1[1] sdc1[4] sdd1[3]
976767872 blocks 64K chunks 2 near-copies [4/2] [_U_U]
[=>...................] recovery = 5.0% (24436736/488383936)
finish=56.2min speed=137513K/sec
I guess that it is ok, and that it is recovering with the spare. But I would
like to be sure...
Xavier
xavier@alternatif.org - 09 54 06 16 26
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-03-18 20:12 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-18 14:49 disk order problem in a raid 10 array Xavier Brochard
2011-03-18 17:22 ` hansbkk
2011-03-18 20:09 ` Xavier Brochard
2011-03-18 20:12 ` Xavier Brochard [this message]
2011-03-18 22:22 ` NeilBrown
2011-03-18 20:26 ` Adaptive throttling for RAID1 background resync Hari Subramanian
2011-03-18 20:28 ` Roberto Spadim
2011-03-18 20:31 ` Hari Subramanian
2011-03-18 20:36 ` Roberto Spadim
2011-03-18 20:54 ` Hari Subramanian
2011-03-18 21:02 ` Roberto Spadim
2011-03-18 22:11 ` NeilBrown
2011-03-21 21:02 ` Hari Subramanian
2011-03-18 22:14 ` disk order problem in a raid 10 array NeilBrown
[not found] ` <201103182350.19281.xavier@alternatif.org>
[not found] ` <20110319102039.52cc2282@notabene.brown>
2011-03-18 23:59 ` Xavier Brochard
2011-03-19 0:05 ` Xavier Brochard
2011-03-19 0:07 ` Roberto Spadim
2011-03-19 0:25 ` Xavier Brochard
2011-03-19 1:42 ` NeilBrown
2011-03-19 13:44 ` Xavier Brochard
2011-03-19 15:14 ` Xavier Brochard
2011-03-20 3:53 ` NeilBrown
2011-03-20 10:40 ` Xavier Brochard
2011-03-19 12:01 ` Xavier Brochard
-- strict thread matches above, loose matches on Subject: below --
2011-03-18 23:06 Xavier Brochard
2011-03-18 23:06 Xavier Brochard
2011-03-18 23:57 ` Roberto Spadim
2011-03-19 0:03 ` Xavier Brochard
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=201103182112.49660.xavier@alternatif.org \
--to=xavier@alternatif.org \
--cc=hansbkk@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 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.