From owner-freebsd-current  Tue Dec  7 12:11:11 1999
Delivered-To: freebsd-current@freebsd.org
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
	by hub.freebsd.org (Postfix) with ESMTP id BFA9014C29
	for <current@FreeBSD.ORG>; Tue,  7 Dec 1999 12:11:09 -0800 (PST)
	(envelope-from ambrisko@whistle.com)
Received: from whistle.com (ibmpc.whistle.com [207.76.205.196])
	by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id MAA24827
	for <current@FreeBSD.ORG>; Tue, 7 Dec 1999 12:11:09 -0800 (PST)
Received: (from ambrisko@localhost)
	by whistle.com (8.9.3/8.9.1) id LAA31946
	for current@FreeBSD.ORG; Tue, 7 Dec 1999 11:57:31 -0800 (PST)
	(envelope-from ambrisko)
From: Doug Ambrisko <ambrisko@whistle.com>
Message-Id: <199912071957.LAA31946@whistle.com>
Subject: Re: ATA driver as the default
In-Reply-To: <384D53E8.27ABF47D@dead-end.net> from "D. Rock" at "Dec 7, 1999
 07:37:28 pm"
To: current@FreeBSD.ORG
Date: Tue, 7 Dec 1999 11:57:31 -0800 (PST)
X-Mailer: ELM [version 2.4ME+ PL61 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

D. Rock writes:
| I just re-enabled the ATA driver again after reading the change log
| of better error handling and automatic falldown DMA->PIO under specific
| circumstances.
| But a few days later, while making world (with the ata driver), the
| system
| crashed quite heavily. The file system was totally screwed up afterwards
| (I found my /usr/local after some heavy searching: It magically
| moved to /usr/obj/usr/src/tmp/usr/share/zoneinfo (!) and got tons of
| fsck
| messages). The file system had softupdates enabled. I don't know the
| last kernel messages before the crash (was running X at that time).

You might want to look at ata-disk.c and the timeout value around line
438:

        /* start timeout for this transfer */
        if (panicstr)
            request->timeout_handle.callout = NULL;
        else
            request->timeout_handle =
                timeout((timeout_t*)ad_timeout, request, 5*hz);

Originally it was 3s and recently increased to 5s.  Personally
I switched it to 30s after it trashed my filesystem when it was 3s.
The issue was that 3s, is that it is to short to wait for my laptop's 
drive to spin back up.  Sometimes I would get a corrupted read sometimes on
a write it would trash things.  I noticed in the old wd driver that
it tried 10s first then a couple 3s timeouts.  After making this
change my system has been rock solid when the drive spins down.
Note I haven't tried to tune this value since trashing a 14G filesystem
is pain full.

Doug A.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message