From: Goswin von Brederlow <goswin-v-b@web.de>
To: LinuxRaid RAID <linux-raid@vger.kernel.org>
Subject: Re: [Patch] mdadm: move mdadm.map file into /dev/md
Date: Tue, 07 Apr 2009 23:04:30 +0200 [thread overview]
Message-ID: <87myastbtt.fsf@frosties.localdomain> (raw)
In-Reply-To: <20090407105520.GA29222@maude.comedia.it> (Luca Berra's message of "Tue, 7 Apr 2009 12:55:21 +0200")
Luca Berra <bluca@comedia.it> writes:
> On Tue, Apr 07, 2009 at 08:05:29AM +0200, Goswin von Brederlow wrote:
>>Doug Ledford <dledford@redhat.com> writes:
>>
>>> Originally, mdadm used /var/run/mdadm/mdadm.map file to store the
>>> temporary mappings of incrementally added devices to device names.
>>> Unfortunately, this breaks incremental assembly if used early in the
>>> booting process. Specifically, root may still be read only. Since
>>> incremental assembly is largely a udev specific feature, and udev
>>> needs a writable /dev tmpfs mount even when root is still read only,
>>> it's safer to put our mdadm.map file in /dev/md so that we can write
>>> to the map file no matter how early in the boot process we are
>>> attempting to use incremental assembly.
>>
>>What about /lib/init/rw?
>
> What is that?, i never heard of '/lib/init/rw' before
>
> L.
At least under debian that is a tmpfs mounted in
/etc/rcS.d/S02mountkernfs.sh for programs that need to write somewhere
early in the boot process while potentially / is read-only and tmp and
var are still missing.
It even runs before /etc/rcS.d/S03udev.
MfG
Goswin
next prev parent reply other threads:[~2009-04-07 21:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-06 14:52 [Patch] mdadm: move mdadm.map file into /dev/md Doug Ledford
2009-04-06 19:36 ` Luca Berra
2009-04-07 6:05 ` Goswin von Brederlow
2009-04-07 10:55 ` Luca Berra
2009-04-07 21:04 ` Goswin von Brederlow [this message]
2009-04-07 12:16 ` Doug Ledford
2009-04-07 21:26 ` NeilBrown
2009-04-07 22:14 ` Doug Ledford
2009-04-08 6:38 ` Neil Brown
2009-04-09 19:28 ` Doug Ledford
2009-04-08 0:15 ` Goswin von Brederlow
2009-04-08 6:31 ` Neil Brown
2009-04-09 19:25 ` Doug Ledford
2009-04-14 1:12 ` 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=87myastbtt.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