893e0b
.TH MKDUMRD 8 "Fri Feb 9 2007"
893e0b
.SH NAME
893e0b
mkdumprd \- creates initial ramdisk images for kdump crash recovery 
893e0b
.SH SYNOPSIS
893e0b
\fBmkdumprd\fR [OPTION]
893e0b
893e0b
.SH DESCRIPTION
893e0b
\fBmkdumprd\fR creates an initial ram file system for use in conjunction with
893e0b
the booting of a kernel within the kdump framework for crash recovery.
893e0b
\fBmkdumprds\fR purpose is to create an initial ram filesystem capable of copying
893e0b
the crashed systems vmcore image to a location specified in \fI/etc/kdump.conf 
893e0b
893e0b
\fBmkdumprd\fR interrogates the running system to understand what modules need to
893e0b
be loaded in the initramfs (based on configuration retrieved from
893e0b
\fI/etc/kdump.conf)\fR
893e0b
893e0b
\fBmkdumprd\fR add a new \fBdracut\fR module 99kdumpbase and use \fBdracut\fR
8f4abc
utility to generate the initramfs. When generating a kdump initramfs, \fBmkdumprd\fR
8f4abc
will determine how much disk space is available, if the dump target's available
8f4abc
space is not greater than the total system memory, \fBmkdumprd\fR will print a
8f4abc
warning to remind that there might not be enough space to save a vmcore. The
8f4abc
warning covers extreme scenarios such as the slab explodes with non-zero data or
8f4abc
a full vmcore, etc. Therefore, need to prevent users from having minimum disk
8f4abc
space for crash dump.
893e0b
893e0b
\fBmkdumprd\fR was not intended for casual use outside of the service
893e0b
initialization script for the kdump utility, and should not be run manually.  If
893e0b
you require a custom kdump initramfs image, it is suggested that you use the
893e0b
kdump service infrastructure to create one, and then manually unpack, modify and
893e0b
repack the image.
893e0b
893e0b
893e0b
.SH OPTIONS
893e0b
.TP
893e0b
All options here are passed to dracut directly, please refer \fBdracut\fR docs
893e0b
for the info.
893e0b
893e0b
.SH "SEE ALSO"
893e0b
.BR dracut (8)