dracut-kdump.sh: umount rootfs after dump_to_rootfs
In dracut-kdump.sh, kdump did not umount rootfs after dump_to_rootfs, just like dump_fs does. And in kdump, the FINAL_ACTION is "reboot -f", no umount action is taken. Even though "sync" has been executed, it's safer to take a "umount rootfs" action. Anyway no harm to umount. Signed-off-by: Baoquan He <bhe@redhat.com> Acked-by: Vivek Goyal <vgoyal@redhat.com>
This commit is contained in:
parent
224b700c82
commit
387a6de171
@ -100,6 +100,8 @@ dump_to_rootfs()
|
|||||||
|
|
||||||
$CORE_COLLECTOR /proc/vmcore $NEWROOT/$KDUMP_PATH/$HOST_IP-$DATEDIR/vmcore || return 1
|
$CORE_COLLECTOR /proc/vmcore $NEWROOT/$KDUMP_PATH/$HOST_IP-$DATEDIR/vmcore || return 1
|
||||||
sync
|
sync
|
||||||
|
umount $NEWROOT || return 1
|
||||||
|
return 0
|
||||||
}
|
}
|
||||||
|
|
||||||
dump_ssh()
|
dump_ssh()
|
||||||
|
Loading…
Reference in New Issue
Block a user