From: Michael Tokarev <mjt@tls.msk.ru>
To: linux-raid@vger.kernel.org
Subject: Re: starting an array on Linux, advise needed
Date: Sat, 17 Jan 2004 03:34:32 +0300 [thread overview]
Message-ID: <40088318.6000002@tls.msk.ru> (raw)
In-Reply-To: <200401170004.i0H04mi15707@dns1.watkins-home.com>
Guy wrote:
> I found this old message, it may help.
> ======================================
> http://www.corpit.ru/mjt/mdctl.c - a very small utility similar to raidtools
Note it will not work correctly in the situation described.
Or at least it may not work. For the same reason as original
code does not work: "renamed" devices in 2.4 vs 2.6.
With raidstart (and this utility follows it logic), it is the
kernel who is reading the raid superblock, opening devices
and assembles the array. Most important part is the superblock:
kernel will pick up any devices found there (by major/minor
number). When booting 2.4 and 2.6, or when your devices are
using dynamically-assigned numbers, that numbers may be different
on next reboot, so kernel will not be able to find all required
devices.
While mdadm tries to examine all superblocks and find all
devices in between the ones listed on command line, in the
superblock or ones that are really present on your system
at any given time (--scan; depends on your mdadm.conf also).
So when you expect your device names/numbers to be instable
between reboots, it's best to use mdadm together with --scan
and proper mdadm.conf or with all possible devices listed in
command line. Mdassemble by Luca Berra will be useful here
too.
/mjt
P.S. Please trim original message somehow when replying.
next prev parent reply other threads:[~2004-01-17 0:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-16 23:46 Fwd: starting an array on Linux, advise needed Arkadiusz Miskiewicz
2004-01-16 23:55 ` Luca Berra
2004-01-17 0:04 ` Guy
2004-01-17 0:34 ` Michael Tokarev [this message]
2004-01-17 0:48 ` Michael
2004-01-17 2:04 ` Guy
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=40088318.6000002@tls.msk.ru \
--to=mjt@tls.msk.ru \
--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).