From owner-freebsd-hackers Tue Jan 4 11:53:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from venera.isi.edu (venera.isi.edu [128.9.176.32]) by hub.freebsd.org (Postfix) with ESMTP id 5730A14BC8 for ; Tue, 4 Jan 2000 11:53:43 -0800 (PST) (envelope-from faber@ISI.EDU) Received: from ted.isi.edu (ted.isi.edu [128.9.160.104]) by venera.isi.edu (8.8.7/8.8.6) with ESMTP id LAA01391 for ; Tue, 4 Jan 2000 11:53:37 -0800 (PST) Received: from ted.isi.edu (localhost [127.0.0.1]) by ted.isi.edu (8.9.3/8.9.3) with ESMTP id LAA11428 for ; Tue, 4 Jan 2000 11:53:41 -0800 (PST) (envelope-from faber@ted.isi.edu) Message-Id: <200001041953.LAA11428@ted.isi.edu> X-Mailer: exmh version 2.1.0 04/14/1999 To: freebsd-hackers@freebsd.org Subject: Someone should close kern/11222 X-Url: http://www.isi.edu/~faber Date: Tue, 04 Jan 2000 11:53:41 -0800 From: Ted Faber Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I noticed that the behavior that prompted me to submit kern/11222 (spurious fscks on when an mfs file system was in use at boot time) disappeared under 3.3-RELEASE, and today I finally had time to check the CVS logs to see what happened. It looks to me like Andrew Gallatin's patch to kern_shutdown.c (1.41->1.42) did the trick. I think his fix allows an mfs that is backed to a local disk file to wind up as inconsistent after a reboot, but I don't think that's a big issue. At any rate, if someone wants to clear one more bug report, as the submitter, I'd be happy to call it closed. - ---------------------------------------------------------------------- Ted Faber faber@isi.edu USC/ISI Computer Scientist http://www.isi.edu/~faber (310) 822-1511 x190 PGP Keys: http://www.isi.edu/~faber/pubkeys.asc -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use Charset: noconv iQA/AwUBOHJPxWlM93/mX/l7EQKJegCfTHHRlIC5KTYuAPxoyJT20sAhrSUAn1bB lYCKpQr5Q8Cd5MRlMjoMgtDN =YoPe -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message