Unnamed repository
fca70aadfd
For devices with filesystem, udev /dev/disk/by-uuid/* links are usually reliable. But one exception is multipath devices, child and top layer device may have same uuid. As dm devices maintain /dev/mapper/* as persistent names, so converting to /dev/mapper/* firstly then try by-uuid/* and by-id/* Also because user know better what's the persistent name we just document well to suggest user use persistent name in kdump.conf. it's suggested to to use lvm or multipath canonical names or uuid/label. Updated kdump.conf examples and related chunks in kexec-kdump-howto.txt use lvm /dev/vg/<devname> in examples Signed-off-by: Dave Young <dyoung@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.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-disable-kexec-test.patch | ||
kexec-tools-2.0.3-ppc-ppc64-compile-purgatory-code-with-gcc-option-msoft-float.patch | ||
kexec-tools-2.0.3-vmcore-dmesg-Do-not-write-beyond-end-of-buffer.patch | ||
kexec-tools-2.0.3-vmcore-dmesg-vmcore-dmesg-Make-it-work-with-new-stru.patch | ||
kexec-tools.spec | ||
mkdumprd | ||
mkdumprd.8 | ||
rhcrashkernel-param | ||
sources |