Table of Contents
Advertisement
NOTE
Step 2. Once the system file has been edited, build a new kernel file using the
Step 3. Save the existing kernel file (probably /stand/vmunix) to a safe place
Step 4. Boot the system from the new kernel file to activate the new dump device
Recovering from failures
Abnormal system shutdowns
• The logical volume cannot be used for file system storage, because the
whole logical volume is used.
To use logical volumes for dump devices (no matter how many logical
volumes are required), include the following dump statement in the
system file:
dump lvol
Configuring No Dump Devices—To configure a kernel with no dump
device, use the following dump statement in the system file:
dump none
To configured the kernel for no dump device, the above statement (
) must be used.
none
Omitting dump statements altogether from the system file results in a
kernel that uses the primary paging device (swap device) as the dump
device.
config command.
(such as /stand/vmunix.safe) in case the new kernel file can not be
booted.
definitions.
Runtime dump device definitions
If there is not a concern about capturing a dump that occurs during the
earliest stages of the boot process, replace or supplement any kernel
dump device definitions while the system is booting or running. There
are two ways to do this:
1. Using crashconf to read dump entries in the /etc/fstab file
(using crashconf's -a option)
2. Using arguments to the crashconf command, directly specifying
the devices to be configured
158
dump
Chapter 7
Advertisement
Table of Contents
