Am 11.11.10 11:51, schrieb Ville Ojamo:
Some generic ideas:
Looks like the zdb output is cut, is it cut because of mail reader or
because zdb died for some reason? If died pstack core..
What does panic stack trace say?
Does zpool import work any better with option -f or -F? Some have in
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
Hi,
# savecore -vf vmdump.0
This should produce two files: unix.0 and vmcore.0
Now we use mdb on these as follows:
# mdb unix.0 vmcore.0
Now when presented with the '' prompt, type ::status and send us all the
output please?
---
W. A. Khushil Dep - khushil@gmail.com - 07905374843
Visit
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
David,
thanks so much (and of course to all other helpful souls here as well)
for providing such great guidance!
Here we go:
Am 11.11.10 16:17, schrieb David Blasingame Oracle:
The vmdump.0 is a compressed crash dump. You will need to convert it
to a format that can be read.
# savecore
In this function, the second argument is a pointer to the osname
(mount). You can dump out the string of what it is.
ff0023b7db50 zfs_domount+0x17c(ff0588aaf698, ff0580cb3d80)
mdb unix.0 vmcore.0
ff0580cb3d80/S
Should print out the offending FS. You could try to then import
David,
thanks a lot for your support. I have been able to get both of my zpools up
again by checking which zfs fs caused these problems.
And... today I also learned at least a bit about zpool troubleshooting.
Thanks
Stephan
--
Von meinem iPhone iOS4
gesendet.
In this function, the second
