Date: Tue, 07 Jan 2003 10:11:05 +0100 From: phk@freebsd.org To: "Willem Jan Withagen" <wjw@withagen.nl> Cc: current@freebsd.org Subject: Re: panic with panic: kmem_malloc(4096): kmem_map too small... Message-ID: <31595.1041930665@critter.freebsd.dk> In-Reply-To: Your message of "Tue, 07 Jan 2003 10:04:59 %2B0100." <01e701c2b62b$db07ddd0$471b3dd4@dual>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <01e701c2b62b$db07ddd0$471b3dd4@dual>, "Willem Jan Withagen" writes: >I was able to copy the full 100+Gb. >Next I'm going to try and fill the disk to the max as user, but i guess it'll not trigger this bug. > >And to that fact I have a question: > At the moment 8% of the disk is reserved. > It being a 170Gb raid, that wastes a good 13,6Gb, which I find at lot. > tunefs lets me bring that down to 5% = 8,5Gb without speed penalty. > But is for this size of spare space such a large threshold really required?? > And IF i would like to experiment, where do I look for the knop to turn?? Basically you don't need to reserve anything, but as you get closer to filling the disk the time to find a free space increases rapidly and your files get very fragmented. Trouble is: they never get defragmented unless you copy them (or do a full dump/restore). I'm not sure how to nail the "right" number of % down, and I'm sure that both Kirk and I would like to hear your numbers :-) -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?31595.1041930665>