Re: RELENG_7 amd64; memory and vm.kmem_size
- From: Oliver Fromme <olli@xxxxxxxxxxxxxxxxx>
- Date: Fri, 30 May 2008 13:50:32 +0200 (CEST)
Jeremy Chadwick wrote:
[...]
vm.kmem_size="3584M"
vm.kmem_size_max="3584M"
Upon reboot, the kernel immediately panic'd with the following message:
kmem_suballoc(): bad status return of 3.
I then chose smaller values (going with 2048M); same panic.
I remember someone on the -fs list explained that there's
currently a hard limit for kmem at 2 GB minus epsilon.
So I suggest trying to set it to slightly less than 2 GB.
And yes, I agree that is unfortunate, because there are
high ZFS workloads where more than 2 GB kmem would be
useful. I hope this design limitation can be alleviated
somehow in the future.
Best regards
Oliver
--
Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M.
Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung:
secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün-
chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart
FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd
"The last good thing written in C was
Franz Schubert's Symphony number 9."
-- Erwin Dieterich
_______________________________________________
freebsd-stable@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@xxxxxxxxxxx"
- References:
- RELENG_7 amd64; memory and vm.kmem_size
- From: Jeremy Chadwick
- RELENG_7 amd64; memory and vm.kmem_size
- Prev by Date: Re: broken re(4)
- Next by Date: Re: broken re(4)
- Previous by thread: RELENG_7 amd64; memory and vm.kmem_size
- Next by thread: JDK+libthr on STABLE
- Index(es):
Relevant Pages
|
|
