All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Neil Brown <neilb-l3A5Bk7waGM@public.gmane.org>
Cc: Dan Williams
	<dan.j.williams-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	"initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"Ciechanowski,
	Ed" <ed.ciechanowski-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	"Labun,
	Marcin" <Marcin.Labun-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	"Danecki,
	Jacek" <jacek.danecki-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	"Patelczyk,
	Maciej"
	<maciej.patelczyk-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: handling mdmon in the initramfs
Date: Fri, 02 Oct 2009 10:02:36 +0200	[thread overview]
Message-ID: <4AC5B39C.10101@redhat.com> (raw)
In-Reply-To: <19141.44581.425618.711550-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>

Hi,

On 10/02/2009 09:39 AM, Neil Brown wrote:
> On Friday October 2, hdegoede-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org wrote:
>> Hi,
>>
>> There is no such thing in the initrd (a writable /var/run), but there is
>> a writable / (initrd == ramdisk), and mdadm will happily create /var/run
>> itself, if it would not do that, there would no issue.
>
> mdadm does not create directories (or at least not for the map file).
> So if /var/run does not exist, it will use a file in /dev.
>
>>
>> Although I do wonder how later, when we do have a writable /var/run, mdadm
>> decides which file to use. Once it has used /dev/.mdadm.map once it should
>> keep on using that.
>
> It always tries the first of
>    /var/run/mdadm/map  /var/run/mdadm.map /dev/.mdadm.map
>
> it will normally read, then write.
> So if /var/run doesn't exist, it will use /dev/.mdadm.map
> Once /var/run/mdadm exists, it will
>    read from /dev/.mdadm.map
>    write to /var/run/mdadm/map
>
> and from then on use /var/run/mdadm/map
>
> So if the initramfs really does not contain /var/run, then this aspect
> should "just work".
>

Ok,

Harald, I know we recently added some stuff to dracut with symlinks under
/var/run/mdadm. Since since then, we've opted to instead patch mdmon
to store its state under /dev/.mdadm (until a better fix is upstream), so the
symlink stuff can be removed and then the map stuff should just work.

Note that we will then still have issues with incremental assembly, as
dracut does incremental assembly, and if we then have partly assembled
arrays when switching over to /, rc.sysinit does a
mdadm -As --run, assembling everything in mdadm.conf, which will still
cause issues if some of them are already partly incremental assembled. But
I don't consider this a mdadm bug, but a distro one :)

Regards,

Hans
--
To unsubscribe from this list: send the line "unsubscribe initramfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2009-10-02  8:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-01 23:23 handling mdmon in the initramfs Dan Williams
2009-10-02  2:05 ` Neil Brown
     [not found]   ` <19141.24565.657477.284252-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2009-10-02  2:52     ` Dan Williams
2009-10-02  3:31       ` Neil Brown
     [not found]         ` <19141.29719.815785.550499-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2009-10-02  5:29           ` Kay Sievers
2009-10-02  7:14           ` Hans de Goede
2009-10-02  7:39             ` Neil Brown
     [not found]               ` <19141.44581.425618.711550-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2009-10-02  8:02                 ` Hans de Goede [this message]
     [not found] ` <4AC53A0D.6060806-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2009-10-02  7:09   ` Hans de Goede

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=4AC5B39C.10101@redhat.com \
    --to=hdegoede-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=Marcin.Labun-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=dan.j.williams-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=ed.ciechanowski-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=jacek.danecki-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=maciej.patelczyk-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=neilb-l3A5Bk7waGM@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.