DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:cc:subject
         :references:in-reply-to:content-type:content-transfer-encoding;
        b=LPQfL5hXemBzhjoTmk+J32dNMm4OBNTz6zu9aEkfkAqaMqbpB2/wXngGWXu3hFlvfJ
         6b5P754yOWYRHQVgQerwSqWIFdZcz3p5mHZzrkWOrucQYd73MOmV7X+KIzQGQqDZOzvY
         09pzlLZiswiKckxldA9gesbGB9CDsm+fm0E+8=
Message-ID: <4A25F7B6.4080904@gmail.com>
Date: Tue, 02 Jun 2009 22:10:30 -0600
From: Robert Hancock <hancockrwd@gmail.com>
User-Agent: Thunderbird 2.0.0.21 (X11/20090320)
MIME-Version: 1.0
To: Markus <M4rkusXXL@web.de>
CC: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Seagate Barracuda 7200.11 ST31500341AS fw SD17
References: <200906021258.20346.M4rkusXXL@web.de>
In-Reply-To: <200906021258.20346.M4rkusXXL@web.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1549
Lines: 41

Markus wrote:
> Hello!
> 
> I have some Seagate Barracuda 7200.11 ST31500341AS 1.5TB drives. They 
> use the firmware SD17.
> They time out at the flush write cache and sometimes on the identify 
> command.
> I know that sounds suspicious so I wrote to seagate but they told me my 
> drives are ok. (Although I dont think so.)
> 
> This drive+fw is blacklisted in the kernel, but there is no firmware 
> upgrade for these drives. (Only very few serial numbers are able to 
> upgrade.)
> 
> Now I want to know after what period of the time the kernel timeouts at 
> these commands!? And if this timeout can be increased (manually, small 
> patch for the kernel) and the min/max/avg time could somehow be 
> messured. Every timeout kicks the drives off the raid, so I disabled 
> the write cache (hdparm -W0 /dev/sdx) but thats no solution, just a bad 
> workaround.

I believe the timeout for commands like these is usually 30 seconds. 
Normally if it doesn't respond after that length of time, it never will. 
Even if it eventually did, I don't think you'd be happy with disk access 
delays of over 30 seconds..

> 
> Its a amd64 system with the 2.6.29.4 on an AM3 board with AMDs 790GX + 
> SB750 Chipsets running in ahci mode.
> 
> Thanks for your time and support!
> 
> Markus
> 
> PS: Please CC me!

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/