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 2/3] Add for_each_host_dev for device only checking
Date: Mon, 20 Aug 2012 10:56:35 -0400 [thread overview]
Message-ID: <20120820145635.GC31044@redhat.com> (raw)
In-Reply-To: <5031D18B.2070208-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
On Mon, Aug 20, 2012 at 01:56:27PM +0800, Dave Young wrote:
> On 08/18/2012 01:02 AM, Vivek Goyal wrote:
>
> > On Fri, Aug 17, 2012 at 08:35:21PM +0800, dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org wrote:
> >> For lvm, multipath, iscsi modules they do not care about the filesystem,
> >> Also there could be devcie in host_devs but it does not get formated.
> >>
> >> For these kind of modules, use for_each_host_dev will be better than use
> >> for_each_host_dev_fs, here add a new function to iterate the host_devs.
> >>
> >
> > If we decide not to add slave devices in host_devs, then this will not
> > work.
>
>
> If we add a line in fstab, then the dev|fs are added to host_fs_types.
> What I'm confusing now is why the for_each_host_dev_fs works without the
> slave devices in host_fs_types.
Because if slave devices have not come up, top level devices in the stack
will not come up. (I think multipath might be exception here).
So I think it should be sufficient to wait for top level block deivce to
come up.
Thanks
Vivek
next prev parent reply other threads:[~2012-08-20 14:56 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
[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 [this message]
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=20120820145635.GC31044@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