Skip Navigation Links | |
Exit Print View | |
Oracle Solaris Administration: Common Tasks Oracle Solaris 11 Information Library |
1. Locating Information About Oracle Solaris Commands
2. Managing User Accounts and Groups (Overview)
3. Managing User Accounts and Groups (Tasks)
4. Booting and Shutting Down an Oracle Solaris System
5. Working With Oracle Configuration Manager
6. Managing Services (Overview)
9. Managing System Information (Tasks)
10. Managing System Processes (Tasks)
11. Monitoring System Performance (Tasks)
12. Managing Software Packages (Tasks)
14. Scheduling System Tasks (Tasks)
15. Setting Up and Administering Printers by Using CUPS (Tasks)
16. Managing the System Console, Terminal Devices, and Power Services (Tasks)
17. Managing System Crash Information (Tasks)
Managing System Crash Information (Task Map)
x86: System Crashes in the GRUB Boot Environment
Managing System Crash Dump Information
How to Display the Current Crash Dump Configuration
How to Modify a Crash Dump Configuration
How to Recover From a Full Crash Dump Directory (Optional)
How to Disable or Enable the Saving of Crash Dumps
18. Managing Core Files (Tasks)
19. Troubleshooting System and Software Problems (Tasks)
20. Troubleshooting Miscellaneous System and Software Problems (Tasks)
This section describes new or changed features for managing system resources in this Oracle Solaris release.
This feature enhancement enables the system to save crash dumps in less time, using less space. The time that is required for a crash dump to complete is now two to ten times faster, depending on the platform. The amount of disk space that is required to save crash dumps in the savecore directory is reduced by the same factors. To accelerate the creation and compression of the crash dump file, the fast crash dump facility utilizes lightly used CPUs on large systems. A new crash dump file, vmdump.n, is a compressed version of the vmcore.n and unix.n files. Compressed crash dumps can be moved over the network more quickly and then analyzed off-site. Note that the dump file must first be uncompressed to use it with tools like the mdb utility. You can uncompress a dump file by using the savecore command, either locally or remotely.
To support the new crash dump facility, the -z option has been added to the dumpadm command. Use this option to specify whether to save dumps in a compressed or an uncompressed format. The default format is compressed.
For more detailed information, see the dumpadm(1M) and the savecore(1M) man pages.