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 [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
