From: Bryan Christ <bryan.christ@hp.com>
To: Daniel Reichelt <mail@itamservices.de>
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: Raid array is not automatically detected.
Date: Fri, 17 Oct 2008 13:40:49 -0500 [thread overview]
Message-ID: <1224268849.17503.72.camel@tuxdev64> (raw)
In-Reply-To: <48F8AA24.7050607@itamservices.de>
thanks for the tip!
On Fri, 2008-10-17 at 15:07 +0000, Daniel Reichelt wrote:
> Hi Bryan,
> I was just having the same problem and the mdadm man page clearly states:
> ----------------------------
> --homehost=
> This will override any HOMEHOST setting in the config file and provides the
> identity of the host which should be considered the home for any arrays.
>
> When creating an array, the homehost will be recorded in the superblock.
> For version-1 superblocks, it will be prefixed to the array name. For
> version-0.90 superblocks, part of the SHA1 hash of the hostname will be stored
> in the later half of the UUID.
>
> When reporting information about an array, any array which is tagged for
> the given homehost will be reported as such.
>
> ****
> When using Auto-Assemble, only arrays tagged for the given homehost will be
> assembled.
> ****
> ----------------------------
>
> So just once stop your array and manually assemble it like
> mdadm -A <md-device> <components> --homehost=<somestring> --update=homehost
> and from the next reboot on, that array, too, will automatically be assembled
> by the linux kernel.
> HTH
> Daniel
next prev parent reply other threads:[~2008-10-17 18:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-17 15:07 Raid array is not automatically detected Daniel Reichelt
2008-10-17 18:40 ` Bryan Christ [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-07-13 20:36 Bryan Christ
2007-07-14 0:03 ` Zivago Lee
2007-07-14 2:09 ` Bryan Christ
2007-07-14 13:51 ` Bill Davidsen
2007-07-14 13:53 ` Justin Piszcz
2007-07-14 17:10 ` Bill Davidsen
2007-07-14 17:08 ` Justin Piszcz
2007-07-16 14:19 ` Bryan Christ
2007-07-16 15:21 ` David Greaves
2007-07-18 5:28 ` dean gaudet
2007-07-18 8:06 ` Justin Piszcz
2007-07-18 8:52 ` David Greaves
2007-07-18 14:39 ` Bryan Christ
2007-07-18 15:46 ` David Greaves
2007-07-18 15:49 ` Bryan Christ
2007-07-18 18:56 ` Bill Davidsen
2007-07-18 23:09 ` Neil Brown
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=1224268849.17503.72.camel@tuxdev64 \
--to=bryan.christ@hp.com \
--cc=linux-raid@vger.kernel.org \
--cc=mail@itamservices.de \
/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).