From owner-freebsd-stable Tue Nov 3 18:41:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA00715 for freebsd-stable-outgoing; Tue, 3 Nov 1998 18:41:04 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA00710 for ; Tue, 3 Nov 1998 18:41:03 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id SAA01502; Tue, 3 Nov 1998 18:39:07 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811040239.SAA01502@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Michael Robinson cc: perl@netmug.org, tom@uniserve.com, stable@FreeBSD.ORG Subject: Re: has this been fixed? In-reply-to: Your message of "Wed, 04 Nov 1998 10:34:52 +0800." <199811040234.KAA24822@public.bta.net.cn> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 03 Nov 1998 18:39:07 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Tom writes: > > It is hardware problem. Fix the hardware so it > >responds faster, and the warning message will disapear. > > > >> Or is there a way to keep that from happening? What causes that error? > >> An IDE timeout, right? > > > > You can lengthen the timeout, but this would just hide the problem. > >Your drive is taking a bit too long to respond. > > Just out of curiousity, how did the threshold for "a bit too long" get > determined? Is this defined in the IDE standard? Did someone conduct > a comprehensive survey of popular drives under various error-recovery modes? > Did the driver writer just pull a number out of the air? It's just a random number that was hoped to be "long enough". Some drives seem to take weeks to decide that a block is bad, some are really quick about it. The current value is 10 seconds; there have been various discussions about raising it, and it'll probably get bumped, but increasing the timeout doesn't actually help the problem (which is almost always a read operation on a bad block that the drive is unable to recover). -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message