Date: Sun, 15 Jun 2008 15:05:45 +0400 (MSD) From: Dmitry Morozovsky <marck@rinet.ru> To: Kostik Belousov <kostikbel@gmail.com> Cc: delphij@freebsd.org, current@freebsd.org Subject: Re: tmpfs panic Message-ID: <20080615145943.X43777@woozle.rinet.ru> In-Reply-To: <20080615101918.GA94309@deviant.kiev.zoral.com.ua> References: <20080615130037.J43777@woozle.rinet.ru> <20080615101918.GA94309@deviant.kiev.zoral.com.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 15 Jun 2008, Kostik Belousov wrote: KB> On Sun, Jun 15, 2008 at 01:06:24PM +0400, Dmitry Morozovsky wrote: KB> > Hi there, KB> > KB> > at contemporary RELENG_7/amd64 [snip] KB> I suspect this may be my mistake. KB> IN case you can reproduce it, please, try the patch below. Will try, thank you. KB> > Also, active tmpfs usage easy leads to "swap zone exhausted, increase KB> > kern.maxswzone", even with 2G RAM + 4G swap and approx 2-3G of tmpfs KB> > in use -- any hints? KB> KB> I think the message is pretty much self-explanatory. Kernel tried to KB> allocate the meatadata to track the swap metadata, and zone appears KB> exhausted. It is not the swap space shortage. Instead, this is kernel KB> zone used to track swap allocation shortage. KB> KB> It is quite non-obvious how to automatically tune this limit, since zone KB> is allocated before swap is configured. Well, but loader(8) man page said: The default of 32MB allows the kernel to support a maximum of ~7GB of swap. and I have only 4G, and system freezes with maxswzone exaustion well before that... Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: marck@FreeBSD.org ] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080615145943.X43777>