Date: Tue, 31 Jul 2007 10:47:25 +0200 From: Cedric Tabary <tabary@efrei.fr> To: Pawel Jakub Dawidek <pjd@FreeBSD.org> Cc: current@freebsd.org Subject: Re: zfs panic with yesterday -current Message-ID: <20070731084725.GB10243@efrei.fr> In-Reply-To: <20070731071442.GA10243@efrei.fr> References: <20070730145011.GC88466@efrei.fr> <20070730191443.GN1092@garage.freebsd.pl> <20070731071442.GA10243@efrei.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
On 31/07/2007 09:14, Cedric Tabary wrote: > On 30/07/2007 21:14, Pawel Jakub Dawidek wrote: > > On Mon, Jul 30, 2007 at 04:50:11PM +0200, Cedric Tabary wrote: > > > 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. > > > > What was the panic message? > > I don't remember, > is there a way to get it again inside ddb ? finally I managed to reproduce it : panic: kmem_malloc(16384): kmem_map too small: 343056384 total allocated cpuid = 1 KDB: enter: panic [thread pid 1206 tid 100154 ] Stopped at kdb_enter+0x31: popq %rbp Cédric.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070731084725.GB10243>