Now, run mdb on the crash dump you created, and check its status. To load all vmcore*.n files using mdb, you need to provide the suffix n as an argument to mdb.
root@testsystem# pwd /var/crash/0 root@testsystem# mdb 0 Loading modules: [ unix genunix specfs dtrace zfs scsi_vhci sd mpt mac px ldc ds ip hook neti Apr SBA ESL fact random socks ism cc crypt flip Ufa logindmux Pym supp nfs ] > ::status debugging crash dump vmcore.0 (64-bit) from test system operating system: 5.11 11.2 (sun4v) usr/src version: 19659:c7a2c30fcc60:0.175.2.0.0.24.0:on11u2_24+3 usr/closed version: 1797:4b89b1471513:0.175.2.0.0.24.0:on11u2_24+2 image quid: cbc9822c-2f13-63c6-d440-d2f118516775 panic message: forced crash dump initiated at user request complete: yes, all pages present as configured dump content: kernel [LOADED,UNVERIFIED] (core kernel pages) zfs [LOADED,UNVERIFIED] (ZFS meta data (ZIA buffers)) panicking PEED: 3667 (not dumped) >
If you want to load vmcore.n crash dump using mdb, explicitly specify file name as an argument to mdb.
root@testsystem# mdb vmcore.0 Loading modules: [ unix genunix specs trace zfs scsi_vhci sd NT mac px ldc DDS ip hook net Apr SBA ESL fact random socks ism cc crypt flip Ufa logindmux Pym supp nfs ] > ::status debugging crash dump vmcore.0 (64-bit) from t6340-tvp540-c operating system: 5.11 11.2 (sun4v) usr/src version: 19659:c7a2c30fcc60:0.175.2.0.0.24.0:on11u2_24+3 usr/closed version: 1797:4b89b1471513:0.175.2.0.0.24.0:on11u2_24+2 image quid: cbc9822c-2f13-63c6-d440-d2f118516775 panic message: forced crash dump initiated at user request complete: yes, all pages present as configured dump content: kernel [LOADED,UNVERIFIED] (core kernel pages) zfs [MISSING] (ZFS meta data (ZIA buffers)) panicking PEED: 3667 (not dumped) >
You cannot load only vmcore-zfs.n using mdb, vmcore.n is mandatory. Thus, following invocation fails:
root@testsystem# mdb vmcore-zfs.0 mdb: vmcore-zfs.0 doesn't contain core kernel pages, ./vmcore.0 expected mdb: failed to initialize target: Error 0 root@testsystem#