From owner-freebsd-stable  Tue Aug 19 04:39:49 1997
Return-Path: <owner-freebsd-stable>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id EAA29834
          for stable-outgoing; Tue, 19 Aug 1997 04:39:49 -0700 (PDT)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA29828
          for <stable@FreeBSD.ORG>; Tue, 19 Aug 1997 04:39:46 -0700 (PDT)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id VAA08777; Tue, 19 Aug 1997 21:32:47 +1000
Date: Tue, 19 Aug 1997 21:32:47 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199708191132.VAA08777@godzilla.zeta.org.au>
To: support@natsoft.com.au, tom@uniserve.com
Subject: Re: FreeBSD Partition Over 2048 Mega Bytes
Cc: stable@FreeBSD.ORG
Sender: owner-freebsd-stable@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>> When you run the bad block scan (bad144), at install time,  it fails at
>> the 2048 MByte point with every block past there being reported as
>> an error. This happens whether the drive is in LBA or NORMAL mode.
>
>  Quite likely bad144 doesn't support filesystems that big.

It should work, but it has the usual overflow bug in the lseek offset
calculation.

Bruce