From owner-freebsd-current  Fri Aug 23 15:08:51 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id PAA18659
          for current-outgoing; Fri, 23 Aug 1996 15:08:51 -0700 (PDT)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA18654
          for <freebsd-current@freebsd.org>; Fri, 23 Aug 1996 15:08:48 -0700 (PDT)
Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id PAA02792; Fri, 23 Aug 1996 15:08:39 -0700 (PDT)
To: Julian Elischer <julian@whistle.com>
cc: nirva@ishiboo.com, freebsd-current@freebsd.org
Subject: Re: -current kills harddrives 
In-reply-to: Your message of "Fri, 23 Aug 1996 12:12:42 PDT."
             <321E02AA.5656AEC7@whistle.com> 
Date: Fri, 23 Aug 1996 15:08:38 -0700
Message-ID: <2790.840838118@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> > I seriously doubt that -current is killing your hard drives.
> > Some things you just can't do from software, even if you wanted
> > to.
> 
> That's not true.
> 
> when we enabled tagged queueing on teh wide busses we 
> effectively increased teh work the drive is doing, and we probably
> raised the temperature by another 2 or 3 degrees.

So we talk to the drives a little faster - you're saying that even
while remaining within spec, simply making the drives work to
performance levels is enough to expect failure?  Hmmmm.  An
interesting point of view.

					Jordan