zfs panic with yesterday -current



Hi,

I wanted to do sme tests with zfs and got this panic with
yesterday cvsup of -CURRENT :

http://grumly.eu.org/freebsd/zfs_panic.png

it is running inside vmware with 2 CPU, 1024M allocated to the VM,
GENERIC amd64 kernel without invariants and witnesses.
I paused the VM in the debugger so I can run any command after
in the debugger if needed.

It is a raidz2 pool with 10 ggate devices of 64M each.

Cédric
_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"



Relevant Pages

  • Re: zfs panic with yesterday -current
    ... yesterday cvsup of -CURRENT: ... it is running inside vmware with 2 CPU, 1024M allocated to the VM, ... I paused the VM in the debugger so I can run any command after ...
    (freebsd-current)
  • Re: zfs panic with yesterday -current
    ... yesterday cvsup of -CURRENT: ... it is running inside vmware with 2 CPU, 1024M allocated to the VM, ... I paused the VM in the debugger so I can run any command after ...
    (freebsd-current)
  • Re: zfs panic with yesterday -current
    ... yesterday cvsup of -CURRENT: ... it is running inside vmware with 2 CPU, 1024M allocated to the VM, ... I paused the VM in the debugger so I can run any command after ...
    (freebsd-current)
  • Re: debuging a hung kernel
    ... that could theoretically be made to drop to the debugger. ... generates an NMI to the debugger from the watchdog CPU. ... scheduler changes in the last few years, ...
    (freebsd-net)
  • Re: debuging a hung kernel
    ... that could theoretically be made to drop to the debugger. ... generates an NMI to the debugger from the watchdog CPU. ... scheduler changes in the last few years, ...
    (freebsd-stable)