From: Randy Terbush <randy@terbush.org>
To: linux-raid@vger.kernel.org, neilb@suse.de
Subject: Re: [PATCH] (Re: Questions regarding startup of imsm container)
Date: Tue, 23 Mar 2010 06:58:33 -0600 [thread overview]
Message-ID: <7db987b31003230558l5993817fwb283c66bbf3633e9@mail.gmail.com> (raw)
In-Reply-To: <20100323080419.GA9374@maude.comedia.it>
On Tue, Mar 23, 2010 at 2:04 AM, Luca Berra <bluca@comedia.it> wrote:
>> # mdadm --version
>> mdadm - v3.1.2 - 10th March 2010
>>
>> # mdadm -Es
>> ARRAY metadata=imsm UUID=30223250:76fd248b:50280919:0836b7f0
>> ARRAY /dev/md/Volume0 container=30223250:76fd248b:50280919:0836b7f0
>> member=0 UUID=8a4ae452:da1e7832:70ecf895:eb58229c
>>
>> # ls -l /dev/md/
>> total 0
>> lrwxrwxrwx 1 root root 6 Mar 22 20:54 0 -> ../md0
>> lrwxrwxrwx 1 root root 8 Mar 22 20:54 127 -> ../md127
>> lrwxrwxrwx 1 root root 8 Mar 22 20:54 Volume0_0 -> ../md127
>>
>> As you can see, the name for the link in /dev/md does not agree with
>> the name that the Examine is coming up with.
>
> please read mdadm.conf manpage, under the section "HOMEHOST"
If I understand this correctly, I think there still may be a problem
as I am not clear on how I could have set the homehost in the metadata
for this imsm array. The Volume0 is provided by imsm and is configured
in the option ROM.
The underlying question here is should the ARRAY entry in mdadm.conf
be changed to reflect the on disk name of the device, or is the
startup process munging that entry when it processes mdadm.conf to
strip the _0.
I'll try setting HOMEHOST <ignore> to see if I am getting expected results.
I seem to have some problems with startup still as I have the
following entry where the container is now md127. Was md0 when
originally created.
# cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md126 : active raid5 sdb[3] sdc[2] sdd[1] sde[0]
2930280448 blocks super external:/md127/0 level 5, 64k chunk,
algorithm 0 [4/4] [UUUU]
md127 : inactive sde[3](S) sdb[2](S) sdc[1](S) sdd[0](S)
9028 blocks super external:imsm
unused devices: <none>
I am also running into a problem where fsck will crash during boot on
the ext4 filesystems that this array contains. No problem running fsck
after the boot process has completed so have not seemed to find the
magic with order of startup for this device.
>
>> Is it better to just forgo the ARRAY statements and go with an AUTO +imsm?
>>
next prev parent reply other threads:[~2010-03-23 12:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-23 3:56 Questions regarding startup of imsm container Randy Terbush
2010-03-23 8:04 ` [PATCH] (Re: Questions regarding startup of imsm container) Luca Berra
2010-03-23 12:58 ` Randy Terbush [this message]
2010-03-23 14:22 ` Luca Berra
2010-03-23 14:33 ` Randy Terbush
2010-03-23 14:49 ` Randy Terbush
2010-03-23 15:56 ` Luca Berra
2010-03-23 22:41 ` Dan Williams
2010-03-24 21:35 ` Randy Terbush
2010-03-23 23:06 ` [PATCH] " Dan Williams
2010-03-24 0:57 ` Neil Brown
2010-03-24 6:12 ` Luca Berra
2010-03-24 14:49 ` Dan Williams
2010-03-23 21:01 ` Questions regarding startup of imsm container Dan Williams
2010-03-23 21:41 ` Randy Terbush
2010-03-23 22:16 ` Dan Williams
2010-03-23 23:25 ` Randy Terbush
2010-03-24 0:23 ` Randy Terbush
2010-03-24 4:14 ` Randy Terbush
2010-03-24 5:54 ` Dan Williams
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=7db987b31003230558l5993817fwb283c66bbf3633e9@mail.gmail.com \
--to=randy@terbush.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.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).