Date: Sat, 04 Jan 2003 09:57:59 +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: <7651.1041670679@critter.freebsd.dk> In-Reply-To: Your message of "Sat, 04 Jan 2003 01:59:36 %2B0100." <03a701c2b38c$8e3ad990$471b3dd4@dual>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <03a701c2b38c$8e3ad990$471b3dd4@dual>, "Willem Jan Withagen" writes: >Which seems a problem sticking up it's head once so often. >I had it happen to me now 3 times over the last day. It just drops into the debugger. >And I've foun little extra info in the archive. > >What dows this actually mean? Is something leaking in the kernel. >IF so how do I help it go away. > >I'm copy 100G from a W2K system to my vinum file server with a 170G raid5. >Current is as of 28 dec... Please try to move up to current as of today. On Dec 29th I commited code to make the desiredvnodes a limit rather than a vague suggestion and that should solve your problem I hope. -- 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?7651.1041670679>