From owner-freebsd-current Tue Dec 7 9:50:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 0446614E19; Tue, 7 Dec 1999 09:50:32 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (beefcake.zeta.org.au [203.26.10.12]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id EAA19048; Wed, 8 Dec 1999 04:54:26 +1100 Date: Wed, 8 Dec 1999 04:50:13 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Mike Smith Cc: Alex Zepeda , FreeBSD CURRENT Mailing List Subject: Re: mount(2) broken? In-Reply-To: <199912070604.WAA00482@mass.cdrom.com> 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 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. > > > Me too. > "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