From owner-freebsd-hackers Tue Sep 5 17:15:56 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.11/8.6.6) id RAA12454 for hackers-outgoing; Tue, 5 Sep 1995 17:15:56 -0700 Received: from UUCP-GW.CC.UH.EDU (UUCP-GW.CC.UH.EDU [129.7.1.11]) by freefall.freebsd.org (8.6.11/8.6.6) with SMTP id RAA12444 for ; Tue, 5 Sep 1995 17:15:52 -0700 Received: from Taronga.COM by UUCP-GW.CC.UH.EDU with UUCP id AA01589 (5.67a/IDA-1.5); Tue, 5 Sep 1995 18:49:21 -0500 Received: (from peter@localhost) by bonkers.taronga.com (8.6.11/8.6.9) id SAA25384; Tue, 5 Sep 1995 18:38:13 -0500 From: peter@taronga.com (Peter da Silva) Message-Id: <199509052338.SAA25384@bonkers.taronga.com> Subject: Re: Bad superblock? To: terry@lambert.org (Terry Lambert) Date: Tue, 5 Sep 1995 18:38:12 -0500 (CDT) Cc: peter@taronga.com, terry@lambert.org, hackers@FreeBSD.ORG In-Reply-To: <199509052241.PAA24452@phaeton.artisoft.com> from "Terry Lambert" at Sep 5, 95 03:41:33 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 903 Sender: hackers-owner@FreeBSD.ORG Precedence: bulk > If this isn't your issue, then you don't have an issue; your superblock > is good, use it instead of trying to play with a backup. 8-). You are completely missing the point. When I umount under 2.0.5 it updates the clean bit on the superblock but not on the backup superblock. When I boot 1.1.5.1, it sees the superblocks are different and forces a manual fsck. Nothing is bad. I'm just wondering why umount doesn't set the clean bit in the backup superblock. It's not saving anything, since the system is routinely writing to the backup superblock anyway. And it provides the *illusion* of a bad file system when the file system is perfectly good. (yes, I know, it's not designed to handle switching file systems between the two, but that's what you do during an upgrade on production hardware... the system should be designed to make upgrades as easy as possible when it doesn't cost anything)