From: Goswin von Brederlow <goswin-v-b@web.de>
To: Doug Ledford <dledford@redhat.com>
Cc: LinuxRaid RAID <linux-raid@vger.kernel.org>, Neil Brown <neilb@suse.de>
Subject: Re: [Patch] mdadm: move mdadm.map file into /dev/md
Date: Tue, 07 Apr 2009 08:05:29 +0200 [thread overview]
Message-ID: <87tz51dmmu.fsf@frosties.localdomain> (raw)
In-Reply-To: <E2135ED2-AC92-48FE-843E-9E8C83B12729@redhat.com> (Doug Ledford's message of "Mon, 6 Apr 2009 10:52:10 -0400")
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?
You say largely udev specific so there might not be an udev running
and no tmpfs on /dev.
MfG
Goswin
next prev parent reply other threads:[~2009-04-07 6:05 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 [this message]
2009-04-07 10:55 ` Luca Berra
2009-04-07 21:04 ` Goswin von Brederlow
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=87tz51dmmu.fsf@frosties.localdomain \
--to=goswin-v-b@web.de \
--cc=dledford@redhat.com \
--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