mkinitrd unification across distributions
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Dave Young <dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: chaowang-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
	harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
	initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [patch 1/3] wait host devs in base module
Date: Mon, 20 Aug 2012 10:59:46 -0400	[thread overview]
Message-ID: <20120820145946.GD31044@redhat.com> (raw)
In-Reply-To: <5031D0ED.4070901-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

On Mon, Aug 20, 2012 at 01:53:49PM +0800, Dave Young wrote:
> On 08/18/2012 12:57 AM, Vivek Goyal wrote:
> 
> > On Fri, Aug 17, 2012 at 08:35:20PM +0800, dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org wrote:
> >> each dev in host_devs[] should be waited in initqueue to make sure they
> >> are oneline before initqueue finish.
> >>
> >> Add a new wait_host_devs.sh in base module to make this a generic thing.
> >> Because all the devs in fstab lines are also added to host_devs, so no need
> >> do same wait in fstab-sys module anymore.
> >>
> >> Chaowang: add slave devices to host_devs as well.
> > 
> > Why should we wait for slave devices? If slave device does not come up,
> > top level device will not come up anyway. So I don't think we should wait
> > for slave devices.
> 
> 
> Yes, agree. Adding the slaves is only for patch 2/3, ie. is_scsi with
> for_each_host_dev. I think I do not fully understand the relations
> beteen the master and slave devices of iscsi/multipath/etc.
> 
> 
> > 
> > Secondly, trying to list slave devices is dangerous as the names you
> > seem to be stroing are not persistent and device renaming will hang
> > the system.
> > 
> > So whereever you are waiting for a device to come up, make sure you
> > are using persistent device name as generated by udev.
> 
> 
> Agree too, this is a problem. Looking at the fstab-sys
> wait_mount_dev.sh, there's same issue if the dev name in fstab is not
> the "persistent device name"

Non persistent names in /etc/fstab will not make sense as system will
be broken across reboots. So it is a requirement to put persistent
names only in /etc/fstab.

I think last time I did partial patch to wait for device nodes. But we
still need mechanism to convert UUID= and LABEL= into respective
persistent device names. Can you please take care of that too while you
are at it.

Thanks
Vivek

  parent reply	other threads:[~2012-08-20 14:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-17 12:35 [patch 0/3] add --device option dyoung-H+wXaHxf7aLQT0dZR+AlfA
2012-08-17 12:35 ` [patch 1/3] wait host devs in base module dyoung-H+wXaHxf7aLQT0dZR+AlfA
     [not found]   ` <20120817123905.089958024-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-08-17 16:57     ` Vivek Goyal
     [not found]       ` <20120817165709.GA11604-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-08-20  5:53         ` Dave Young
     [not found]           ` <5031D0ED.4070901-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-08-20 14:59             ` Vivek Goyal [this message]
     [not found]               ` <20120820145946.GD31044-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-08-21  7:32                 ` Dave Young
2012-08-17 12:35 ` [patch 2/3] Add for_each_host_dev for device only checking dyoung-H+wXaHxf7aLQT0dZR+AlfA
     [not found]   ` <20120817123905.206266546-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-08-17 17:02     ` Vivek Goyal
     [not found]       ` <20120817170217.GB11604-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-08-20  5:56         ` Dave Young
     [not found]           ` <5031D18B.2070208-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-08-20 14:56             ` Vivek Goyal
2012-08-17 12:35 ` [patch 3/3] Add a dracut option --device to bring up a device in initramfs dyoung-H+wXaHxf7aLQT0dZR+AlfA
     [not found]   ` <20120817123905.353853040-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-08-17 17:04     ` Vivek Goyal

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=20120820145946.GD31044@redhat.com \
    --to=vgoyal-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=chaowang-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=initramfs-u79uwXL29TY76Z2rM5mHXA@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox