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