From owner-freebsd-current Mon Dec 6 21:57:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from mta3.snfc21.pbi.net (mta3.snfc21.pbi.net [206.13.28.141]) by hub.freebsd.org (Postfix) with ESMTP id D564E14D7D for ; Mon, 6 Dec 1999 21:57:46 -0800 (PST) (envelope-from jazepeda@pacbell.net) Received: from zippy.dyn.ml.org ([207.214.149.187]) by mta3.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FMC00G80W809B@mta3.snfc21.pbi.net> for current@freebsd.org; Mon, 6 Dec 1999 21:50:31 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by zippy.dyn.ml.org (Postfix) with ESMTP id 2B5BC91846; Mon, 06 Dec 1999 21:50:24 -0800 (PST) Date: Mon, 06 Dec 1999 21:50:24 -0800 (PST) From: Alex Zepeda Subject: Re: mount(2) broken? In-reply-to: To: Nick Hibma Cc: Poul-Henning Kamp , vallo@matti.ee, "Brian W. Buchanan" , FreeBSD CURRENT Mailing List Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII 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. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message