From owner-freebsd-stable  Sat Sep 27 18:50:48 1997
Return-Path: <owner-freebsd-stable>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id SAA26468
          for stable-outgoing; Sat, 27 Sep 1997 18:50:48 -0700 (PDT)
Received: from word.smith.net.au (ppp20.portal.net.au [202.12.71.120])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA26460
          for <freebsd-stable@freebsd.org>; Sat, 27 Sep 1997 18:50:41 -0700 (PDT)
Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1])
	by word.smith.net.au (8.8.7/8.8.5) with ESMTP id LAA03271;
	Sun, 28 Sep 1997 11:18:12 +0930 (CST)
Message-Id: <199709280148.LAA03271@word.smith.net.au>
X-Mailer: exmh version 2.0zeta 7/24/97
To: mdean <mdean@best.com>
cc: freebsd-stable@freebsd.org
Subject: Re: bad144 
In-reply-to: Your message of "Sat, 27 Sep 1997 17:42:40 MST."
             <Pine.SGI.3.95.970927174013.28472A-100000@shellx.best.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 28 Sep 1997 11:18:11 +0930
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-stable@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> 
> I've looked through the freebsd mail archive about this but can't find any
> reported bugs. Should bad144 fail on 4.0 gig ide drives or what? It is

I'm fairly sure that bad144 suffers on extents larger than 2GB, 
although I haven't actually tried it to see.

> digital) and it can't find any bad sectors---- should I ignore bad144 or is
> this a sign that it may be broken once I install --- my bios fully supports
> drives of this size (it is a fairly new ppro)

There's little point in using it unless you're sure your disk doesn't 
do bad sector forwarding. 

mike