From mboxrd@z Thu Jan 1 00:00:00 1970 From: Neil Brown Subject: Re: handling mdmon in the initramfs Date: Fri, 2 Oct 2009 17:39:17 +1000 Message-ID: <19141.44581.425618.711550@notabene.brown> References: <4AC53A0D.6060806@intel.com> <19141.24565.657477.284252@notabene.brown> <4AC56AF1.5030801@intel.com> <19141.29719.815785.550499@notabene.brown> <4AC5A85F.8060608@redhat.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: message from Hans de Goede on Friday October 2 Sender: initramfs-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-ID: Content-Type: text/plain; charset="us-ascii" To: Hans de Goede Cc: Dan Williams , Harald Hoyer , "initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , "Ciechanowski, Ed" , "Labun, Marcin" , "Danecki, Jacek" , "Patelczyk, Maciej" 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". NeilBrown -- 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