From owner-freebsd-current Sat Dec 18 13:13:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id E7E9B14BDE for ; Sat, 18 Dec 1999 13:13:26 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id WAA49245; Sat, 18 Dec 1999 22:13:20 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912182113.WAA49245@freebsd.dk> Subject: Re: ATA driver problem?? (lost disk contact) In-Reply-To: <19991218220258.B35095@relativity.student.utwente.nl> from "Dave J. Boers" at "Dec 18, 1999 10:02:58 pm" To: djb@Wit389306.student.utwente.nl Date: Sat, 18 Dec 1999 22:13:20 +0100 (CET) Cc: dick@tar.com (Richard Seaman Jr.), freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Dave J. Boers wrote: > On Sat, Dec 18, 1999 at 08:44:42PM +0100, Soren Schmidt wrote: > > 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. > > I am under the impression that the drive does not need to do ADM if it is > shutdown once every six days. So can't we go with phk's solution: make a > cron job that shuts down and powers up the drive once every six days? I'd rather just up the timeout to 10s like the old wd driver, that way it apparently isn't a problem anymore, we just wait for the sucker to spin up if needed. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message