When a hardware or software failure causes the storage system to panic, the system creates a core file that technical support can use to troubleshoot the problem. The storage system stores the core file in the /etc/crash directory on the root volume.
The savecore command, which is included in the default /etc/rc file on the root volume, performs the following tasks:
A core dump file contains the contents of memory and NVRAM. Core dumps are written over reserved sections of any working disk owned by the local storage system. When a core dump is created, it is stored in uncompressed format if sufficient space is available; otherwise, it is stored in compressed format. If there is insufficient space to store a complete core dump in compressed format, the core dump is canceled.
Note
If the failed storage system belongs to a cluster and options cf.takeover.on_panic is enabled, a core dump file is written to a spare disk on that system.
Core dump files are not compatible between Data ONTAP releases because where the core starts on disks depends on the release. Because of this incompatibility, Data ONTAP might fail to find a core dump file dumped by another release.
There are two options you can use to control core dump file creation, as listed in the following table:
|
Controls how many attempts are made to create a core dump file. | ||
|
Specifies whether the buffers containing user data are dumped. |
For more information about these options, see the na_options(1) man page.
Your storage system sends e-mail automatically to technical support upon each system reboot, if the AutoSupport feature is enabled and configured correctly. Technical support uses the AutoSupport message and the core file to troubleshoot the problem.
Note
If you have disabled AutoSupport e-mail, you should contact technical support when your system creates a core file.
Copyright © 1994-2005, Network Appliance, Inc. All rights
reserved.
Part No. 210-01077_B0
File: 7maint6.htm
Last updated: 21-Dec-2005 09:03:29