zpool import reboots computer
Andriy Gapon
avg at FreeBSD.org
Thu Jan 19 20:10:26 UTC 2012
on 19/01/2012 21:58 Martin Ranne said the following:
> On 2012-01-19 18:55, Andriy Gapon wrote:
> on 19/01/2012 19:36 Martin Ranne said the following:
> On 2012-01-19 17:32, Andriy Gapon wrote:
> on 19/01/2012 17:36 Martin Ranne said the following:
>>>>> I had a failure in one server where i try to determine if it is memory or cpu. It shows up as memory failure in memtest86. >>The result is that it managed to damage the zpool which is a raidz2 with 6 disks.
>
>>>>> If I boot from a FreeBSD 9.0-RELEASE usb stick and import it with zpool -f -R /mnt/zroot zroot it will reboot the computer. >>I have also tried to import it in another computer which is running 9-STABLE with the same result. On the second computer I >>used zpool -f -R /mnt/zroot "zpool-id" serv06zroot
>
>>>>> Can I get some help on how to be able to debug this and in the end be able to import it to repair it.
>
>>>>> Data for the second computer can be found attached. The disks in question are da0 to da5 in this.
>
>>>> And the panic message is?
>
>>> I am trying to get a crash dump but it hangs when dumping.
>
>> Alternatives:
>> - serial console
>> - digital camera
>> - eyes plus pen and paper
>
> Finally here it is. Is there anything i can do in the debugger to make it possible to find what is crashing in there?
>
> Fatal trap 12: page fault while in kernel mode
> Fatal trap 12: page fault while in kernel mode
> cpuid = 0; cpuid = 2; apic id = 00
> apic id = 02
> fault virtual address = 0x88
> fault virtual address = 0x38
> fault code = supervisor read data, page not present
> fault code = supervisor read data, page not present
> instruction pointer = 0x20:0xffffffff814a7ef5
> instruction pointer = 0x20:0xffffffff814872a1
> stack pointer = 0x28:0xffffff8c10252ad0
> stack pointer = 0x28:0xffffff8c0d564f00
> frame pointer = 0x28:0xffffff8c10252b40
> frame pointer = 0x28:0xffffff8c0d564f30
> code segment = base 0x0, limit 0xfffff, type 0x1b
> code segment = base 0x0, limit 0xfffff, type 0x1b
> = DPL 0, pres 1, long 1, def32 0, gran 1
> = DPL 0, pres 1, long 1, def32 0, gran 1
> processor eflags = processor eflags = interrupt enabled, interrupt enabled, resume, resume, IOPL = 0
> IOPL = 0
> current process = current process = 2659 (zpool)
> 0 [ thread pid 2659 tid 100592 ]
Hmm, two traps running almost perfectly in parallel...
> stopped at zio_vdev_child_io+0x25: cmpq $0,0x88(%r10)
> db>
At least the 'bt' command.
It could be that the panic is caused by corrupted vdev label, but not sure...
--
Andriy Gapon
More information about the freebsd-fs
mailing list