From owner-freebsd-stable  Mon Aug 18 09:17:17 1997
Return-Path: <owner-freebsd-stable>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id JAA00264
          for stable-outgoing; Mon, 18 Aug 1997 09:17:17 -0700 (PDT)
Received: from shell.uniserve.com (tom@shell.uniserve.com [204.244.210.252])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA00257
          for <stable@FreeBSD.ORG>; Mon, 18 Aug 1997 09:17:12 -0700 (PDT)
Received: from localhost (tom@localhost)
	by shell.uniserve.com (8.8.5/8.8.5) with SMTP id JAA03199;
	Mon, 18 Aug 1997 09:12:28 -0700 (PDT)
X-Authentication-Warning: shell.uniserve.com: tom owned process doing -bs
Date: Mon, 18 Aug 1997 09:12:28 -0700 (PDT)
From: Tom <tom@uniserve.com>
To: Simon Bennet <support@natsoft.com.au>
cc: stable@FreeBSD.ORG
Subject: Re: FreeBSD Partition Over 2048 Mega Bytes
In-Reply-To: <33F86CE6.6334@natsoft.com.au>
Message-ID: <Pine.BSF.3.96.970818091043.3187A-100000@shell.uniserve.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


On Mon, 18 Aug 1997, Simon Bennet wrote:

> 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.

  You shouldn't need to do bad block scanning on modern media.  IDE drives
should support auto-relocation of bad sectors.  As long as the reserved
area does not fill up, you should be ok.

Tom