From owner-freebsd-current Mon Dec 6 22: 2:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (castles552.castles.com [208.214.165.116]) by hub.freebsd.org (Postfix) with ESMTP id 3E19514D7D for ; Mon, 6 Dec 1999 22:02:14 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id WAA00482; Mon, 6 Dec 1999 22:04:14 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912070604.WAA00482@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Alex Zepeda Cc: FreeBSD CURRENT Mailing List Subject: Re: mount(2) broken? In-reply-to: Your message of "Mon, 06 Dec 1999 21:50:24 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 06 Dec 1999 22:04:14 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 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. Me too. 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, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message