Unnamed repository
f8d7090b59
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. v4->v5: Per Vivek's comment, add a helper function is_fs_dump_target. Then is_user_configured_dump_target is rewrite with these helper functions. v5->v7: No v6 for this patch. Just use newly introduced function is_fs_type_nfs in handle_default_dump_target. Signed-off-by: Baoquan He <bhe@redhat.com> Acked-by: Vivek Goyal <vgoyal@redhat.com> |
||
---|---|---|
po | ||
.gitignore | ||
98-kexec.rules | ||
dracut-kdump.sh | ||
dracut-module-setup.sh | ||
dracut-monitor_dd_progress | ||
firstboot_kdump.py | ||
kdump-dep-generator.sh | ||
kdump-in-cluster-environment.txt | ||
kdump-lib.sh | ||
kdump.conf | ||
kdump.conf.5 | ||
kdump.init | ||
kdump.service | ||
kdump.sysconfig | ||
kdump.sysconfig.i386 | ||
kdump.sysconfig.ia64 | ||
kdump.sysconfig.ppc64 | ||
kdump.sysconfig.s390x | ||
kdump.sysconfig.x86_64 | ||
kdumpctl | ||
kexec-kdump-howto.txt | ||
kexec-tools-2.0.3-build-makedumpfile-eppic-shared-object.patch | ||
kexec-tools-2.0.3-disable-kexec-test.patch | ||
kexec-tools-2.0.4-makedumpfile-memset-in-cyclic-bitmap-initialization-introdu.patch | ||
kexec-tools-2.0.5-vmcore-dmesg-stack-smashing-happend-in-extreme-case.patch | ||
kexec-tools.spec | ||
mkdumprd | ||
mkdumprd.8 | ||
README | ||
rhcrashkernel-param | ||
sources | ||
zanata-notes.txt |
Adding a patch to kexec-tools ============================= There is a mailing list kexec@lists.fedoraproject.org where all the dicussion related to fedora kexec-tools happen. All the patches are posted there for inclusion and committed to kexec-tools after review. So if you want your patches to be included in fedora kexec-tools package, post these to kexec@lists.fedoraproject.org. One can subscribe to list and browse through archives here. https://admin.fedoraproject.org/mailman/listinfo/kexec