> On Mon, 6 Dec 1999, Nick Hibma wrote:
>
> > Most probably this is exactly the problem I was describing to you a
> > couple of days ago on IRC, phk.
> >
> > The solution is to boot single user, fsck / and reboot. After that
> > things are back to normal. Even crashing the machine does not make this
> > problem reoccur.
>
> Nah. This is about the third time I've seen this. I hadn't really
> gathered any useful information (and no data was lost) so I didn't bother
> to report it. I suspect it has something to do with soft-updates however.
<aol>
Me too.
</aol>
I just manifested this after a particularly nasty crash this evening
(about 500 outstanding buffers), but softupdates weren't active.
(It's too easy to kill the system with them enabled; there's a whole
realm of exploration still untouched there.)
--
\\ Give a man a fish, and you feed him for a day. \\ Mike Smith
\\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED]
\\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
