Date: Mon, 9 Jun 2014 16:15:33 -0400 From: grarpamp <grarpamp@gmail.com> To: freebsd-fs@freebsd.org Subject: Re: ZFS import panic (kgdb backtrace attached) Message-ID: <CAD2Ti2_DZqDbOnbwap-YrOEjavyRZ4H7JZ1r8mkk4_OPrYQEUg@mail.gmail.com> In-Reply-To: <A2A7DF1F550D4691B84F4CE2903F1B31@multiplay.co.uk> References: <CAD2Ti29gKmED34S5z6NEUnaGOsx8m2uPEJiPWPZLcebJ6PD-mw@mail.gmail.com> <A2A7DF1F550D4691B84F4CE2903F1B31@multiplay.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jun 9, 2014 at 3:01 PM, Steven Hartland <killing@multiplay.co.uk> wrote: > ZFS doesn't really like i386 due to the limited stack size > > So the first think I would try is increasing your kernel stack size: > options KSTACK_PAGES=4 If it's not a genuine bug (ie: just the usual ZFS on i386 issues), I can move it to default x64 with 8GB in maybe a week. I forgot to include, this is stock GENERIC with: real memory = 2147483648 (2048 MB) vm.kmem_size=650000000 I don't recall why I set kmem_size. And when wired mem gets above 600 things get unrecoverably slow and the box will lock/panic if I press on zfs at/above 600. With the 100 or so heavy write panics and a dozen+ power cuts across multiple zfs/pool/bsd versions, I'm amazed I still have any readable zfs fs's at all. Anyway, posted in case it's a genuine bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAD2Ti2_DZqDbOnbwap-YrOEjavyRZ4H7JZ1r8mkk4_OPrYQEUg>