From: Cong Wang <amwang-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Vivek Goyal <vgoyal-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: Dave Young <dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
kexec-kdump-list-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
Subject: Re: mount other than rootfs problem
Date: Tue, 04 Oct 2011 11:13:16 +0800 [thread overview]
Message-ID: <4E8A79CC.3080109@redhat.com> (raw)
In-Reply-To: <20110930190311.GH25891-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
于 2011年10月01日 03:03, Vivek Goyal 写道:
> On Fri, Sep 30, 2011 at 02:38:39PM -0400, Vivek Goyal wrote:
>> On Fri, Sep 30, 2011 at 11:40:12AM +0800, Dave Young wrote:
>>
>> [..]
>>>
>>> Add lvm_scan in mount-sys.sh also works, so if we can make lvm_scan
>>> being called automaticlly via dependencies it will be good. OTOH fstab
>>> is better than cmdlines as an interface for multi-target dumping
>>
>> Agreed that fstab.sys looks like a good interface to mouting non-root devices.
>
> Having said that, looks like dracut builds all the state using command
> line options. All the lvms, iscsi root, fcoe targets etc. So they might
> expect everything to be passed on command line. In that case it will
> become hard from kdump perspective.
Yeah, the problem is that we still need to detect which module is needed
to mount some specified device, which is duplicated, as the code is already
in these modules (e.g. is_lvm()).
Thanks.
next prev parent reply other threads:[~2011-10-04 3:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-29 2:55 mount other than rootfs problem Dave Young
[not found] ` <4E83DE33.4020204-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2011-09-29 15:18 ` Cong Wang
[not found] ` <4E848C48.6050506-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2011-09-30 2:17 ` Dave Young
[not found] ` <4E8526A6.30003-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2011-09-30 3:27 ` Cong Wang
[not found] ` <4E85370A.7020509-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2011-09-30 3:40 ` Dave Young
[not found] ` <4E853A1C.5070905-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2011-09-30 3:48 ` Cong Wang
2011-09-30 18:38 ` Vivek Goyal
[not found] ` <20110930183839.GF25891-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2011-09-30 19:03 ` Vivek Goyal
[not found] ` <20110930190311.GH25891-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2011-10-04 3:13 ` Cong Wang [this message]
2011-10-12 9:03 ` Dave Young
[not found] ` <4E9557F2.2060209-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2011-10-12 9:22 ` Harald Hoyer
[not found] ` <4E955C5A.1010406-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2011-10-12 19:07 ` Vivek Goyal
[not found] ` <20111012190744.GG12845-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2011-10-13 9:19 ` Harald Hoyer
[not found] ` <4E96AD07.6040806-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2011-10-13 14:43 ` Vivek Goyal
2011-10-12 8:59 ` Dave Young
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=4E8A79CC.3080109@redhat.com \
--to=amwang-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 \
--cc=kexec-kdump-list-H+wXaHxf7aLQT0dZR+AlfA@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