From owner-freebsd-current Sun Dec 19 20:28:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id B999414CC4 for ; Sun, 19 Dec 1999 20:28:57 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id D631B1C4A; Sun, 19 Dec 1999 23:28:29 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by jade.chc-chimes.com (Postfix) with ESMTP id C7316381B; Sun, 19 Dec 1999 23:28:29 -0500 (EST) Date: Sun, 19 Dec 1999 23:28:29 -0500 (EST) From: Bill Fumerola To: Alex Zepeda Cc: current Subject: Re: fsck not cleaning on first try In-Reply-To: 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 Sun, 19 Dec 1999, Alex Zepeda wrote: > 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. Ditto. mount was telling me my fs wasn't clean, but after I rebooted it was fine and it didn't fsck that second time. -- - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message