> 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.
Bruce posted (but did not commit) what may be a fix for this a while back:
diff -c2 ffs_vfsops.c~ ffs_vfsops.c
*** ffs_vfsops.c~ Thu Nov 25 23:27:44 1999
--- ffs_vfsops.c Sun Dec 5 05:12:51 1999
***************
*** 218,222 ****
--- 220,226 ----
}
+ fs->fs_flags &= ~FS_UNCLEAN;
if (fs->fs_clean == 0) {
+ fs->fs_flags |= FS_UNCLEAN;
if (mp->mnt_flag & MNT_FORCE) {
printf(
--
\\ Give a man a fish, and you feed him for a day. \\ Mike Smith
\\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED]
\\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
