From: Brad Campbell <brad@wasp.net.au>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Neil Brown <neilb@suse.de>, Peb <peb-misc@peeble.net>,
linux-raid@vger.kernel.org
Subject: Re: md array numbering is messed up
Date: Mon, 30 Oct 2006 15:23:40 +0400 [thread overview]
Message-ID: <4545E0BC.5010103@wasp.net.au> (raw)
In-Reply-To: <4545DECE.7030705@tls.msk.ru>
Michael Tokarev wrote:
> Neil Brown wrote:
>> On Sunday October 29, peb-misc@peeble.net wrote:
>>> Hi,
>>>
>>> I have 2 arrays whose numbers get inverted, creating havoc, when booting
>>> under different kernels.
>>>
>>> I have md0 (raid1) made up of ide drives and md1 (raid5) made up of five
>>> sata drives, when booting with my current ubuntu 2.6.12-9 kernel. When I
>>> try to boot a more recent kernel (2.6.15-26 or 2.6.15-27) the
>>> order is inversed and my sata raid5 array shows up as md0.
>>>
>>> My arrays are part of evms volumes that just stop working if the
>>> numbering is inverted.
>>>
>>> any clues ?
>> Your arrays are being started the wrong way.
>> Do you have an mdadm.conf that lists the arrays? Can you show us what
>> it looked like?
>> If not, do you know how the arrays are started in ubuntu?
>
> My guess is that it's using mdrun shell script - the same as on Debian.
> It's a long story, the thing is quite ugly and messy and does messy things
> too, but they says it's compatibility stuff and continue shipping it.
>
> For the OP, the solution is to *create* mdadm.conf file - in that case
> mdrun should hopefully NOT run.
I'd suggest you are probably correct. By default on Ubuntu 6.06
brad@bklaptop2:~$ cat /etc/init.d/mdadm-raid
#!/bin/sh
#
# Start any arrays which are described in /etc/mdadm/mdadm.conf and which are
# not running already.
#
# Copyright (c) 2001-2004 Mario Jou/3en <joussen@debian.org>
# Distributable under the terms of the GNU GPL version 2.
MDADM=/sbin/mdadm
MDRUN=/sbin/mdrun
CONFIG=/etc/mdadm/mdadm.conf
DEBIANCONFIG=/etc/default/mdadm
. /lib/lsb/init-functions
test -x $MDADM || exit 0
AUTOSTART=true
test -f $DEBIANCONFIG && . $DEBIANCONFIG
case "$1" in
start)
if [ "x$AUTOSTART" = "xtrue" ] ; then
if [ ! -f /proc/mdstat ] && [ -x /sbin/modprobe ] ; then
/sbin/modprobe -k md > /dev/null 2>&1
fi
test -f /proc/mdstat || exit 0
log_begin_msg "Starting RAID devices..."
if [ -f $CONFIG ] && [ -x $MDADM ] ; then
$MDADM -A -s
elif [ -x $MDRUN ] ; then
$MDRUN
fi
log_end_msg $?
fi
;;
stop|restart|reload|force-reload)
;;
*)
log_success_msg "Usage: $0 {start|stop|restart|reload|force-reload}"
exit 1
;;
esac
exit 0
Brad
--
"Human beings, who are almost unique in having the ability
to learn from the experience of others, are also remarkable
for their apparent disinclination to do so." -- Douglas Adams
next prev parent reply other threads:[~2006-10-30 11:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-29 21:17 md array numbering is messed up Peb
2006-10-29 21:26 ` Neil Brown
2006-10-30 11:15 ` Michael Tokarev
2006-10-30 11:23 ` Brad Campbell [this message]
2006-10-30 11:58 ` dean gaudet
2006-10-30 23:50 ` Peb
2006-10-31 3:06 ` Neil Brown
2006-11-01 20:20 ` Peb
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=4545E0BC.5010103@wasp.net.au \
--to=brad@wasp.net.au \
--cc=linux-raid@vger.kernel.org \
--cc=mjt@tls.msk.ru \
--cc=neilb@suse.de \
--cc=peb-misc@peeble.net \
/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).