Skip Navigation Links | |
Exit Print View | |
System Administration Guide: Advanced Administration Oracle Solaris 10 8/11 Information Library |
1. Managing Terminals and Modems (Overview)
2. Setting Up Terminals and Modems (Tasks)
3. Managing Serial Ports With the Service Access Facility (Tasks)
4. Managing System Resources (Overview)
5. Displaying and Changing System Information (Tasks)
7. Managing UFS Quotas (Tasks)
8. Scheduling System Tasks (Tasks)
9. Managing System Accounting (Tasks)
10. System Accounting (Reference)
11. Managing System Performance (Overview)
12. Managing System Processes (Tasks)
13. Monitoring System Performance (Tasks)
14. Troubleshooting Software Problems (Overview)
16. Managing Core Files (Tasks)
17. Managing System Crash Information (Tasks)
Managing System Crash Information (Task Map)
Oracle Solaris ZFS Support for Swap Area and Dump Devices
x86: System Crashes in the GRUB Boot Environment
Dump Devices and Volume Managers
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 Saving Crash Dumps
18. Troubleshooting Miscellaneous Software Problems (Tasks)
19. Troubleshooting File Access Problems (Tasks)
20. Resolving UFS File System Inconsistencies (Tasks)
This section describes new or changed features for managing system resources in this Oracle Solaris release.
Oracle Solaris 10 9/10: 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 2 to 10 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.