Dell PowerEdge M IO Aggregator Command Reference Manual page 283

Figure 22-19. Mini application core file naming example
FTOS#dir
Directory of flash:
1 drw- 16384
2 drwx 1536
3 drw- 512
4 d--- 512
5 -rw- 8693
6 -rw- 8693
7 -rw- 156
8 -rw- 156
9 -rw- 156
10 -rw- 156
11 -rw- 156
12 -rw- 156
13 -rw- 156
flash: 3104256 bytes total (2959872 bytes free)
FTOS#
When a member or standby unit crashes, the mini core file gets uploaded to master unit. When the master
unit crashes, the mini core file is uploaded to new master. In the Aggregator, only the master unit has the
ability to upload the coredump.
Figure 22-20. Mini core text file example
------------------------PANIC STRING -----------------
panic string is :<null>
----------------------STACK TRACE START---------------
0035d60c <f10_save_mmu+0x120>:
00274f8c <panic+0x144>:
0024e2b0 <db_fncall+0x134>:
0024dee8 <db_command+0x258>:
0024d9c4 <db_command_loop+0xc4>:
002522b0 <db_trap+0x158>:
0026a8d0 <mi_switch+0x1b0>:
0026a00c <bpendtsleep>:
------------------------STACK TRACE END----------------
---------------------------FREE MEMORY---------------
uvmexp.free = 0x2312
The panic string contains key information regarding the crash. Several panic string types exist, and they are
displayed in regular English text to allow easier understanding of the crash cause.
Jan 01 1980 00:00:00 +00:00 .
Sep 03 2009 16:51:02 +00:00 ..
Aug 07 2009 13:05:58 +00:00 TRACE_LOG_DIR
Aug 07 2009 13:06:00 +00:00 ADMIN_DIR
Sep 03 2009 16:50:56 +00:00 startup-config
Sep 03 2009 16:44:22 +00:00 startup-config.bak
Aug 28 2009 16:16:10 +00:00 f10StkUnit0.mrtm.acore.mini.txt
Aug 28 2009 17:17:24 +00:00 f10StkUnit0.vrrp.acore.mini.txt
Aug 28 2009 18:25:18 +00:00 f10StkUnit0.sysd.acore.mini.txt
Aug 28 2009 19:07:36 +00:00 f10StkUnit0.frrp.acore.mini.txt
Aug 31 2009 16:18:50 +00:00 f10StkUnit2.sysd.acore.mini.txt
Aug 29 2009 14:28:34 +00:00 f10StkUnit0.ipm1.acore.mini.txt
Aug 31 2009 16:14:56 +00:00 f10StkUnit0.acl.acore.mini.txt
VALID MAGIC
Debugging and Diagnostics | 269