Date: Sun, 5 Jan 2003 16:40:02 +0100 From: "Willem Jan Withagen" <wjw@withagen.nl> To: <phk@freebsd.org> Cc: <current@freebsd.org> Subject: Panic: Initiate_write_inodeblock_ufs1: already started Message-ID: <063601c2b4d0$ff02dc50$471b3dd4@dual> References: <7651.1041670679@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
Recompiled the kernel (GENERIC) and installed.
But now it panics on:
Initiate_write_inodeblock_ufs1: already started.
--WjW
PS: Once it trips into the debugger, how do I get it to dump?
panic just reboots.
----- Original Message -----
From: <phk@freebsd.org>
To: "Willem Jan Withagen" <wjw@withagen.nl>
Cc: <current@freebsd.org>
Sent: Saturday, January 04, 2003 9:57 AM
Subject: Re: panic with panic: kmem_malloc(4096): kmem_map too small...
> 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.
>
>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?063601c2b4d0$ff02dc50$471b3dd4>