From owner-freebsd-current  Sat Nov 30  1:55:48 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 773ED37B401; Sat, 30 Nov 2002 01:55:47 -0800 (PST)
Received: from gull.mail.pas.earthlink.net (gull.mail.pas.earthlink.net [207.217.120.84])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 1037343E4A; Sat, 30 Nov 2002 01:55:47 -0800 (PST)
	(envelope-from tlambert2@mindspring.com)
Received: from pool0072.cvx21-bradley.dialup.earthlink.net ([209.179.192.72] helo=mindspring.com)
	by gull.mail.pas.earthlink.net with esmtp (Exim 3.33 #1)
	id 18I4LM-0003a1-00; Sat, 30 Nov 2002 01:55:24 -0800
Message-ID: <3DE88ABE.B22DFB84@mindspring.com>
Date: Sat, 30 Nov 2002 01:54:06 -0800
From: Terry Lambert <tlambert2@mindspring.com>
X-Mailer: Mozilla 4.79 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Kirk McKusick <mckusick@beastie.mckusick.com>
Cc: Manfred Antar <null@pozo.com>, current@FreeBSD.ORG,
	Robert Watson <rwatson@tislabs.com>, re@FreeBSD.ORG,
	Poul-Henning Kamp <phk@critter.freebsd.dk>
Subject: Re: Update to UFS2 Superblock Format
References: <200211300743.gAU7hj59078306@beastie.mckusick.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG

Kirk McKusick wrote:
>         Ah
>         No wonder, I tried editing the /sys/boot/i386/boot2/Makefile
>         to enable UFS2 bootblock but then disklabel complained that
>         boot2 was too big. I will have to revert to UFS1
>         Thanks
>         Manfred
> 
> You have hit upon the exact problem. UFS2 has a much bigger area
> reserved for the boot block, but the programs that set up disk labels
> and boot blocks don't know about it yet so assume that they have to
> cram into the much smaller UFS1 boot-block area.

Seems to be a candidate to explain the disklabel corruption,
actually.  The disklabel is expected to follow the initial
boot code, and preceed the region(s) it describes...

Basically, the boot blocks are going to have to know the
disklabel offset, as promiscuous knowledge (i.e. hard-wired
intot he code).

-- Terry

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message