From: Goswin von Brederlow <goswin-v-b@web.de>
To: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Array over arrays - how to autoassemble correctly?
Date: Wed, 27 Jan 2010 21:51:53 +0100 [thread overview]
Message-ID: <877hr3nudy.fsf@frosties.localdomain> (raw)
In-Reply-To: <73e903671001271145p7b698661w3ca6562c2ced1018@mail.gmail.com> ("Kristleifur Daoason"'s message of "Wed, 27 Jan 2010 19:45:13 +0000")
Kristleifur Daðason <kristleifur@gmail.com> writes:
> On Wed, Jan 27, 2010 at 7:41 PM, Luca Berra <bluca@comedia.it> wrote:
>> On Wed, Jan 27, 2010 at 06:32:57PM +0000, Kristleifur Dađason wrote:
>>>
>>> # mdadm.conf
>>> #
>>>
>>> # by default, scan all partitions (/proc/partitions) for MD superblocks.
>>> # alternatively, specify devices to scan, using wildcards if desired.
>>> DEVICE partitions /dev/md/d0 /dev/md/d1
>>>
>>> # auto-create devices with Debian standard permissions
>>> # CREATE owner=root group=disk mode=0660 auto=mdp
>>>
>>> # automatically tag new arrays as belonging to the local system
>>> HOMEHOST <system>
>>>
>>> # definitions of existing MD arrays
>>>
>>> ARRAY /dev/md/d0 metadata=1.1 name=mamma:d0
>>> UUID=7f98e926:206a8ebe:59fc8d7b:4644a883 level=raid6 num-devices=6 #
>>> container=6f98a7a8:d7b50181:587c27d1:59d6d137
>>>
>>> ARRAY /dev/md/d1 metadata=1.1 name=mamma:d1
>>> UUID=da547022:042a6f68:d5fe251e:5e89f263 level=raid6 num-devices=6 #
>>> container=6f98a7a8:d7b50181:587c27d1:59d6d137
>>>
>>> ARRAY /dev/md/tank metadata=1.1 name=mamma:tank
>>> UUID=6f98a7a8:d7b50181:587c27d1:59d6d137 level=raid0 num-devices=2
>>> devices=/dev/md/d0,/dev/md/d1
>>>
>>
>> this kind of setup should be working without any issue on recent mdadm
>> try removing
>> DEVICE partitions /dev/md/d0 /dev/md/d1
>> and the "devices=/dev/md/d0,/dev/md/d1" from mdadm.conf
>> and let it discover things on boot by itself
>>
>> L.
>>
>
> Many thanks for the reply!
>
> However, that's how the mdadm.conf looked like until today - adding
> the DEVICE and devices stuff is something I put in to get things to
> autoassemble themselves fully, as I thought 'man mdadm.conf' indicated
> it.
>
> Still, I'll certianly try - with and without - and double-checking
> that my initramfs is OK.
>
> Any further input most well appreciated.
Alternative add a scriplet into the initramfs config that calls the
mdadm assembling a second time.
MfG
Goswin
--
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:[~2010-01-27 20:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-27 18:32 Array over arrays - how to autoassemble correctly? Kristleifur Daðason
2010-01-27 19:41 ` Luca Berra
2010-01-27 19:45 ` Kristleifur Daðason
2010-01-27 20:51 ` Goswin von Brederlow [this message]
2010-01-30 10:17 ` Luca Berra
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=877hr3nudy.fsf@frosties.localdomain \
--to=goswin-v-b@web.de \
--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