Date: Fri, 7 Mar 2014 15:41:57 -0800 (PST) From: "Chris H" <bsd-lists@bsdforge.com> To: "Wojciech Puchar" <wojtek@wojtek.tensor.gdynia.pl> Cc: freebsd-hackers@freebsd.org Subject: Re: kern.maxswzone Message-ID: <725ac3a0c66351a391ec272d7676fdc5.authenticated@ultimatedns.net> In-Reply-To: <alpine.BSF.2.00.1403072155140.5678@wojtek.tensor.gdynia.pl> References: <alpine.BSF.2.00.1403072155140.5678@wojtek.tensor.gdynia.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
Greetings, > i configured 4.7GB swap on 512MB computer and i see in logs > OK I'm a bit confused here. It /sounds/ like you said you put 4.7 GIGabytes on a 512 MEGabyte hard drive. Hmm, no that can't be right. I'll bet you meant you have a computer with 512Mb RAM, and you created a 4.7Gb slice for SWAP. OK, that probably exceeds the traditional 2.5 x RAM I remember it being. But still, as memory serves, the message(s) you're seeing won't have a definitive answer without first determining how large the "block size" is on your hard drive. While I'm inclined to think they're 4096Kb. I can't know for sure, and anyone attempting to help, will also need that number. The block size determines the /amount/ (number) of pages the kernel creates. > warning: total configured swap (1249880 pages) exceeds maximum recommended amount (986496 > pages). > warning: increase kern.maxswzone or reduce amount of swap. > > > fine, but after increasing maxswzone to 60000000 from less than 40 > millions of default, no difference in message > > tried even increasing it more - no effect, same messages > > change is in /boot/loader.conf and it sets properly as sysctl > kern.maxswzone confirms. > > what's wrong Best wishes. --Chris > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?725ac3a0c66351a391ec272d7676fdc5.authenticated>