Date: Mon, 20 Dec 1999 16:58:59 +1030 From: Mark Newton <newton@internode.com.au> To: Bill Fumerola <billf@chc-chimes.com> Cc: Alex Zepeda <jazepeda@pacbell.net>, current <current@FreeBSD.ORG> Subject: Re: fsck not cleaning on first try Message-ID: <19991220165859.H1688@internode.com.au> In-Reply-To: <Pine.BSF.4.10.9912192327580.68220-100000@jade.chc-chimes.com> References: <Pine.BSF.4.10.9912192022130.261-100000@localhost> <Pine.BSF.4.10.9912192327580.68220-100000@jade.chc-chimes.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Dec 19, 1999 at 11:28:29PM -0500, Bill Fumerola wrote: > 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. I saw that too; I worked out it was because I hadn't done the MAKEDEV after upgrading to a -current without blkdevs (so it's surprising it worked at all). - mark -- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19991220165859.H1688>