From: Sven Riedel <sr@gimp.org>
Cc: linux-ide@vger.kernel.org
Subject: Re: SATA command timeouts
Date: Mon, 10 Jul 2006 13:25:51 +0200 [thread overview]
Message-ID: <20060710112551.GB14003@localnet> (raw)
In-Reply-To: <20060708130037.GA22725@localnet>
On Sat, Jul 08, 2006 at 03:00:37PM +0200, Sven Riedel wrote:
> Hi,
> I hooked up new SATA disks to a machine yesterday and set up a software raid.
> After copying roughly 25 GB of data onto the array all attached drives
> reported command timeouts and wouldn't recover. Only a reboot would help.
> I tried the same again, this time the drives would timeout after 60 GB of data
> written. I exchanged the CPU, but the same thing occurs.
Well, seems the second CPU was defunct. After switching back to the first CPU
the hard system crashes stopped occurring.
> My
> next test will be doing write-heavy operations on all four drives
> simulaneously, but without gathering them into a raid array.
Well, it looks like the problem can be reproduced most reliably only when all
four drives are under load. It happens even sooner when they are gathered into
a raid array (I only tested level 5 - could be that the background "rebuild"
after creation is adding additional load which triggers the problem sooner).
Just to rule out an insufficient power supply, I hooked the drives up to a
completely independent PSU and the drives still all suddenly trigger a
command-timeout after a while.
Regs,
Sven
--
Sven Riedel sr@gimp.org
prev parent reply other threads:[~2006-07-10 11:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-08 13:00 SATA command timeouts Sven Riedel
2006-07-10 11:25 ` Sven Riedel [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=20060710112551.GB14003@localnet \
--to=sr@gimp.org \
--cc=linux-ide@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).