The vmdump.0 is a compressed crash dump. You will need to convert it to
a format that can be read.
# savecore -f ./vmdump.0 ./
This will create a couple of files, but the ones you will need next is
unix.0 & vmcore.0. Use mdb to print out the stack.
# mdb unix.0 vmcore.0
run the following to print the stack. This would at least tell you what
function the system is having a panic in. You could then do a sunsolve
search or google search.
$C
and gather zio_state data
::zio_state
And check the msgbuf to see if there are any hardware problems.
::msgbuf
Then quit mdb. More drill down would be dependent on what you see.
::quit
Dave
On 11/11/10 08:51, Stephan Budach wrote:
Am 11.11.10 14:26, schrieb Steve Gonczi:
Dumpadm should tell you how your
Dumps are set up
Also you could load mdb before importing
I have located the dump, it's called vmdump.0. I also loaded mdb
before I imported the pool, but that didn't help. Actually I tried it
this way:
mdb -K -F
:c
zpool import -f -o readonly <pool>
Afterwards I tried to get back to mdb by hitting F1-a, but that didn't
work - it was only printing 'a' on the console. Otherwise I would have
tried <systemdump, but that didn't came to pass.
Is there anything I can do with the vmdump.0 file. Unfortuanetly I am
not a Kernel hacker…
Thanks
-
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
