From: Robert Hancock <hancockrwd@gmail.com>
To: Markus <M4rkusXXL@web.de>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Seagate Barracuda 7200.11 ST31500341AS fw SD17
Date: Tue, 02 Jun 2009 22:10:30 -0600 [thread overview]
Message-ID: <4A25F7B6.4080904@gmail.com> (raw)
In-Reply-To: <200906021258.20346.M4rkusXXL@web.de>
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!
next prev parent reply other threads:[~2009-06-03 4:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-02 10:58 Seagate Barracuda 7200.11 ST31500341AS fw SD17 Markus
[not found] ` <4A250B6A.6030904@grupopie.com>
2009-06-02 11:37 ` Markus
2009-06-02 12:14 ` Kay Diederichs
2009-06-02 12:38 ` Markus
2009-06-02 14:03 ` Krzysztof Halasa
2009-06-03 10:14 ` Markus
2009-06-03 15:38 ` Krzysztof Halasa
2009-06-03 4:10 ` Robert Hancock [this message]
2009-06-03 10:16 ` Markus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A25F7B6.4080904@gmail.com \
--to=hancockrwd@gmail.com \
--cc=M4rkusXXL@web.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.