From: Mark Lord <liml@rtr.ca>
To: Tejun Heo <tj@kernel.org>
Cc: "Bruno Prémont" <bonbons@linux-vserver.org>,
"Linux Kernel" <linux-kernel@vger.kernel.org>,
linux-ide@vger.kernel.org, "Jeff Garzik" <jgarzik@pobox.com>
Subject: Re: XFS shutting down due to IO timeout on SATA disk (pata_via for CX700)
Date: Mon, 15 Sep 2008 23:49:19 -0400 [thread overview]
Message-ID: <48CF2CBF.2050406@rtr.ca> (raw)
In-Reply-To: <48CEC76E.7020101@kernel.org>
Tejun Heo wrote:
>..
> Hmm.. most of FLUSH timeouts I've seen are either a dying drive or bad
> PSU. There just isn't much which can go wrong from the driver side.
> IIRC, there was a problem when the unused part of TF is not cleared
> but that was the only one.
>
>> Smartctl output is clean (no logged errors), and the drives themselves
>> are fine after a reboot -- necessary since libata/scsi kicked the drive out
>> of the RAID array.
>>
>> Something strange is going on here.
>
> Any chance you can trick the client to hook up the drive to a separate PSU?
..
No, the failures happen randomly at customer sites, and only since they
"upgraded" to SLES10 with libata. I think the PSUs are probably just fine.
Time to hack the drivers to give proper status on the timeouts, too;
otherwise we won't ever have any clue as to what is really happening.
Cheers
prev parent reply other threads:[~2008-09-16 3:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-11 17:35 XFS shutting down due to IO timeout on SATA disk (pata_via for CX700) Bruno Prémont
2008-09-15 8:55 ` Tejun Heo
2008-09-15 17:02 ` Bruno Prémont
2008-09-15 20:43 ` Tejun Heo
2008-09-16 8:21 ` Bruno Prémont
2008-09-16 17:35 ` Tejun Heo
2008-09-21 19:51 ` Bruno Prémont
2008-09-16 15:07 ` Grant Grundler
2008-09-15 20:30 ` Mark Lord
2008-09-15 20:37 ` Tejun Heo
2008-09-16 3:49 ` Mark Lord [this message]
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=48CF2CBF.2050406@rtr.ca \
--to=liml@rtr.ca \
--cc=bonbons@linux-vserver.org \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@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.