Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 23 May 2014 17:23:03 +0000
From:      Radim Kolar <hsn@sendmail.cz>
To:        Steven Hartland <killing@multiplay.co.uk>, "bug-followup@freebsd.org" <bug-followup@freebsd.org>, "freebsd-fs@freebsd.org" <freebsd-fs@freebsd.org>
Subject:   RE: kern/189355: [zfs] zfs panic on root mount 10-stable
Message-ID:  <BLU179-W1169CDB6C5F170815CBF48AD3E0@phx.gbl>
In-Reply-To: <BLU179-W28D0E7C369D1DA24F9019BAD3E0@phx.gbl>
References:  <9423EBFC865C4281A93352433E62219E@multiplay.co.uk>, <BLU179-W16C116F0E7B7E9A204290AD3E0@phx.gbl>, <BLU179-W28D0E7C369D1DA24F9019BAD3E0@phx.gbl>

next in thread | previous in thread | raw e-mail | index | archive | help
its not just about building custom kernel. GENERIC from 10-STABLE panics on=
 i386 mount ZFS root too.

Maybe ZFS should not be used on i386=2C but it should not panic system. If =
you are against changing default kernel configuration on i386 then add anot=
her warning to boot messages similar to this:

ZFS WARNING: Recommended minimum kmem_size is 512MB=3B expect unstable beha=
vior.
             Consider tuning vm.kmem_size and vm.kmem_size_max
             in /boot/loader.conf.
 		 	   		  =



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BLU179-W1169CDB6C5F170815CBF48AD3E0>