From owner-freebsd-current Sat Nov 23 3:29:51 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CBF6E37B401 for ; Sat, 23 Nov 2002 03:29:49 -0800 (PST) Received: from falcon.mail.pas.earthlink.net (falcon.mail.pas.earthlink.net [207.217.120.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6F73F43E9C for ; Sat, 23 Nov 2002 03:29:49 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0024.cvx22-bradley.dialup.earthlink.net ([209.179.198.24] helo=mindspring.com) by falcon.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 18FYTr-0007OV-00; Sat, 23 Nov 2002 03:29:47 -0800 Message-ID: <3DDF631A.8FA84679@mindspring.com> Date: Sat, 23 Nov 2002 03:14:34 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Garance A Drosihn Cc: current@FreeBSD.org Subject: Re: fsck's, "current" vs "earlier releases" References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Garance A Drosihn wrote: > I have 4.6.2-release, 4.7-release, and 5.0-dp2-release on a single PC. > After some bouncing between versions, and an occasional 'disklabel' > command, I seem to have the partitions for 4.6.2 in an odd state. > Both 4.7 and 5.0-dp2 have no problem mounting them, but if I try to > boot up the 4.6.2 system it fails because 4.6.2 finds that "values > in super block disagree with those in first alternate". 4.6.2 wants > me to 'fsck' the partitions manually, but I *think* I remember that > using the older fsck might cause trouble. Yes. You need to recompile a "-STABLE" fsck on the older version of the OS, so that it can do the right thing about the "don't care" areas of the superblock. A generic fix would grow "don't care" regions down, and "care" regions up, with a boundary offset (which started in the top 25% for forward compatability, and grew down), above which you didn't complain about differences. It's too late to implement that, now that people have hacked up the superblock, an there is an existing installed base with it hacked the wrong way for automatic binary compatability. Right now, all you can do is compile a new version of fsck for your old version of the OS, to make it ignore differences in those areas. - Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message