On 03/27/14 at 02:29pm, Vivek Goyal wrote:
On Fri, Mar 21, 2014 at 05:55:20PM +0800, Baoquan He wrote:
When user does not specify dump target explicitly, it's better to dump to the "path" specified. That means after dump user enter into 1st kernel, can find vmcore in the "path". If that path is in root fs, vmcore is stored in root fs. If separate disk is mounted on any tier of "path", we just dump vmcore into the left path on the left separate disk.
E.g in kdump.conf path /mnt/nfs
in mount info, /dev/vdb on /mnt type ext4 (rw,relatime,seclabel,data=ordered)
Then vmcore will be saved in /nfs of /dev/vdb.
In this patch, pass mount info to dracut in this case if separate disk is mounted on any tier of "path".
Meanwhile introduce a function in kdump-lib.sh to check if any target is specified.
Can you rebase this patch on top of current tree and repost. We can now also introduce two new functions is_fs_dump_target() and is_raw_dump_target().
Yes, will do.
Thanks Vivek
Signed-off-by: Baoquan He bhe@redhat.com Acked-by: Vivek Goyal vgoyal@redhat.com