Date: Wed, 8 Dec 1999 04:50:13 +1100 (EST) From: Bruce Evans <bde@zeta.org.au> To: Mike Smith <msmith@FreeBSD.ORG> Cc: Alex Zepeda <jazepeda@pacbell.net>, FreeBSD CURRENT Mailing List <current@FreeBSD.ORG> Subject: Re: mount(2) broken? Message-ID: <Pine.BSF.4.10.9912080443390.6397-100000@alphplex.bde.org> In-Reply-To: <199912070604.WAA00482@mass.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 6 Dec 1999, Mike Smith wrote:
> > 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.
>
> <aol>
> Me too.
> </aol>
"mount -f /" on a dirty root file system causes the clean flag to stay off
forever. (I forgot to change the unclean flag for mount -u.)
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(
Bruce
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?Pine.BSF.4.10.9912080443390.6397-100000>