From: Dave Young <dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Vivek Goyal <vgoyal-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] Add option to bring up a device in initramfs
Date: Tue, 14 Aug 2012 14:27:27 +0800 [thread overview]
Message-ID: <5029EFCF.4060005@redhat.com> (raw)
In-Reply-To: <20120813151029.GE24876-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
On 08/13/2012 11:10 PM, Vivek Goyal wrote:
> On Thu, Aug 09, 2012 at 11:08:48AM +0800, Dave Young wrote:
>>
>> Kdump support dump to raw device which could be on top of complex storage
>> such as multipath and iscsi which are standalone dracut modules.
>>
>> Add a --device option to dracut which will add the device to host_devs so
>> dracut can add the dependent modules automaticlly and enable them in initramfs.
>>
>
> You have not specified any format for --device argument? What do you expect
> there? Device name, UUID, udev persistent link, or what?
It's a device name, should metion it in doc as well.
>
> Secondly, do we need some extra code to make sure somebody waits for
> this device to come up? Who makes sure that initqueue does not exit
> till this device node comes up.
I see there's a wait-mount-dev.sh in 95fstab-sys module which is for
waiting for the mount needed dev.
Currently dracut maintains host_devs and host_fs_types, host_fs_types
are mainly used inst the fs kernel modules. Other than the filesystem
modules we should use host_devs instead, ie. introduce
for_each_host_devs for modules such as multipath and iscsi using.
Another issue is waiting for host_devs should be handled in generic code
instead of 95fstab-sys.
This patch need an update to address these issues IMHO.
>
> Thanks
> Vivek
>
>> Signed-off-by: Dave Young <dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
>> Tested-by: Chao Wang <chaowang-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
>> ---
>> dracut.8.asc | 3 +++
>> dracut.sh | 3 +++
>> 2 files changed, 6 insertions(+)
>>
>> --- dracut.orig/dracut.sh
>> +++ dracut/dracut.sh
>> @@ -133,6 +133,7 @@ Creates initial ramdisk images for prelo
>> --mount "[DEV] [MP] [FSTYPE] [FSOPTS]"
>> Mount device [DEV] on mountpoint [MP] with filesystem
>> [FSTYPE] and options [FSOPTS] in the initramfs
>> + --device "[DEV]" Bring up [DEV] in initramfs
>> -i, --include [SOURCE] [TARGET]
>> Include the files in the SOURCE directory into the
>> Target directory in the final initramfs.
>> @@ -261,6 +262,7 @@ TEMP=$(unset POSIXLY_CORRECT; getopt \
>> --long fscks: \
>> --long add-fstab: \
>> --long mount: \
>> + --long device: \
>> --long nofscks: \
>> --long ro-mnt \
>> --long kmoddir: \
>> @@ -327,6 +329,7 @@ while :; do
>> --fscks) push fscks_l "$2"; shift;;
>> --add-fstab) push add_fstab_l "$2"; shift;;
>> --mount) push fstab_lines "$2"; shift;;
>> + --device) push host_devs "$2"; shift;;
>> --nofscks) nofscks_l="yes";;
>> --ro-mnt) ro_mnt_l="yes";;
>> -k|--kmoddir) drivers_dir_l="$2"; shift;;
>> --- dracut.orig/dracut.8.asc
>> +++ dracut/dracut.8.asc
>> @@ -321,6 +321,9 @@ provide a valid _/etc/fstab_.
>> Mount _<device>_ on _<mountpoint>_ with _<filesystem type>_ and _<filesystem
>> options>_ in the initramfs
>>
>> +**--device** _<device>_ ::
>> + Bring up _<device>_ in initramfs
>> +
>> **-i, --include** _<SOURCE>_ _<TARGET>_::
>> include the files in the SOURCE directory into the
>> TARGET directory in the final initramfs. If SOURCE is a file, it will be
--
Thanks
Dave
next prev parent reply other threads:[~2012-08-14 6:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-09 3:08 [PATCH] Add option to bring up a device in initramfs Dave Young
[not found] ` <20120809030848.GA10460-je1gSBvt1Td3da3rpXeqgR/sF2h8X+2i0E9HWUfgJXw@public.gmane.org>
2012-08-13 15:10 ` Vivek Goyal
[not found] ` <20120813151029.GE24876-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-08-14 6:27 ` Dave Young [this message]
[not found] ` <5029EFCF.4060005-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-08-14 19:36 ` 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=5029EFCF.4060005@redhat.com \
--to=dyoung-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=chaowang-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=vgoyal-H+wXaHxf7aLQT0dZR+AlfA@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