Rechercher une page de manuel
Version: 175185 (fedora - 06/07/09)
Section: 8 (Commandes administrateur)
NAMEmkdumprd - creates initial ramdisk images for kdump crash recovery
SYNOPSISmkdumprd [--version] [-v] [-f] [-d]
DESCRIPTIONmkdumprd creates an initial ram file system for use in conjunction with the booting of a kernel within the kdump framework for crash recovery. mkdumprds purpose is to create an initial ram filesystem capable of copying the crashed systems vmcore image to a location specified in /etc/kdump.conf
Any module options specified in /etc/modprobe.conf are passed to the modules as they are loaded by the initial ramdisk.
mkdumprd interrogates the running system to understand what modules need to be loaded in the initramfs (based on configuration retrieved from /etc/kdump.conf)
mkdumprd was origionally derived from the mkinitrd utility (hence the simmilarity in option sets), however mkdumprds purpose and mission is significantly different than that of mkinitrd. As such, while most of the options still exist, and may work, they are largely vestigual at this point. mkdumprd was not intended for casual use outside of the service initialization script for the kdump utility, and should not be run manually. If you require a custom kdump initramfs image, it is suggested that you use the kdump service infrastrucutre to create one, and then manually unpack, modify and repack the image.
- Act as if module is built into the kernel being used. mkdumprd will not look for this module, and will not emit an error if it does not exist. This option may be used multiple times.
- Allows mkdumprd to overwrite an existing image file.
- Use fstab to automatically determine what type of filesystem the root device is on. Normally, /etc/fstab is used.
- The kernel version number is appended to the initrd image path before the image is created.
- Normally the created initrd image is compressed with gzip. If this option is specified, the compression is skipped.
- Do not load any lvm modules, even if /etc/fstab expects them.
- Do not load any raid modules, even if /etc/fstab and /etc/raidtab expect them.
- Do not load any scsi modules, including 'scsi_mod' and 'sd_mod' modules, even if they are present.
- Load the module module in the initial ramdisk image. The module gets loaded before any SCSI modules which are specified in /etc/modprobe.conf. This option may be used as many times as necessary.
- Prints out verbose information while creating the image (normally the mkdumprd runs silently).
- Query /etc/kdump for initrd construction configuration
- Prints the version of mkdumprd that's being used and then exits.
- Specifies modules to be loaded and module options to be used.
SEE ALSOfstab(5), insmod(1) mkinitrd(8)
Ben c'est exactement ce que je fait, et Daniel est non-content !
-+- Noëlle, sur fr.rec.photo -+-