Date: Sat, 18 Dec 1999 20:44:42 +0100 (CET) From: Soren Schmidt <sos@freebsd.dk> To: dick@tar.com (Richard Seaman, Jr.) Cc: djb@Wit389306.student.utwente.nl, freebsd-current@FreeBSD.ORG Subject: Re: ATA driver problem?? (lost disk contact) Message-ID: <199912181944.UAA27989@freebsd.dk> In-Reply-To: <19991217152300.C320@tar.com> from "Richard Seaman, Jr." at "Dec 17, 1999 03:23:00 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
It seems Richard Seaman, Jr. wrote: > On Fri, Dec 17, 1999 at 02:28:29PM +0100, Soren Schmidt wrote: > > > Because the wd driver has a 10 secs timeout, and ata has 5 secs. > > I think the easiest way to "solve" this is to increase the > > timeout to 10-15 secs, as little as I want to do that... > > I don't really understand disk drivers, so if I'm off base, > I apologize. I'm under the impression that you can query the > disk to see if its in idle mode, or if not, if its in standby > mode. If you leave the timeout at 5 secs, and you actually > timeout, perhaps you can check the disk to see if its in > standby mode, or in the process of spinning up. If so, for > just this case, perhaps you can adjust the timeout to a greater > value before retrying the command? Also, perhaps you want to > skip printing the diagnostic if the timeout was due to > standby/spinup, unless it also fails on retry? There is no way to see if the disk was in suspend mode, you can give it a command and se how long it takes before it comes back :) The problem here is that it takes the command and OK's it, but it takes the spinuptime + overhead before the answer comes, and then the driver already timed out. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199912181944.UAA27989>