From owner-freebsd-current Sun Dec 19 20:26:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from mta2.snfc21.pbi.net (mta2.snfc21.pbi.net [206.13.28.123]) by hub.freebsd.org (Postfix) with ESMTP id ACFA114F69 for ; Sun, 19 Dec 1999 20:26:31 -0800 (PST) (envelope-from jazepeda@pacbell.net) Received: from zippy.dyn.ml.org ([207.214.116.51]) by mta2.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FN0000I0UVUEA@mta2.snfc21.pbi.net> for current@freebsd.org; Sun, 19 Dec 1999 20:23:55 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by zippy.dyn.ml.org (Postfix) with ESMTP id 6C2D89184A for ; Sun, 19 Dec 1999 20:23:53 -0800 (PST) Date: Sun, 19 Dec 1999 20:23:53 -0800 (PST) From: Alex Zepeda Subject: fsck not cleaning on first try To: current 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 Hmm. It happened again. This time I was playing around with the vmware stuff (the linux procfs thingy refused to buildsorta, but FWIW, I think this is the way to go, not bloating *our* procfs), and eventually when run panic'd the system. I just rebooted it (nearly a day later), and fsck cleaned it and printed some info, but then mount refused to mount it. A simple reboot from the comandline seems to have worked. Hmmm indeed. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message