From: Jarrod Johnson <jarrod.b.johnson@gmail.com>
To: linux-ide@vger.kernel.org
Subject: Re: Problems w/ RAID-5/sata_promise/PDC20579
Date: Thu, 21 Jul 2005 21:23:54 -0400 [thread overview]
Message-ID: <fab4e42a0507211823236da64b@mail.gmail.com> (raw)
In-Reply-To: <fab4e42a050718215857958bc4@mail.gmail.com>
Has anyone had success with any SATAII sata_promise card doing large
amounts of I/O to multiple drives attached to a controller? If can
resync ~20 GB arrays with relatively low risk, but if trying to
sustain a resync/restore over 200 GB or so, I rarely complete,
especially if booted and doing typical multi-user stuff. During
normal operation of a synced raid-5 array, the controller hoses up
every few days in the same manner by simple matter of probablity I
suppose.
Is there anything I can do to help get this fixed? Or is the solution
possibly elsewhere? Is there libata work done recently for SATAII in
general?
On 7/19/05, Jarrod Johnson <jarrod.b.johnson@gmail.com> wrote:
> I have a Soltek planar with this controller providing two ports.
>
> As I try to use those ports together with two non-pdc attached sata
> drives for software raid, the devices hanging off of the PDC
> controller frequently become unresponive, throwing I/O errors on every
> attempt to read a sector after a timeout.
>
> Don't have the exact error in front of me, but essentially, it gets
> command timeout,
> then every command to the controller seems to give the same, status of
> 0xff busy, but not much more informative output.
>
> The situation seems very similar to Jim Ramsays:
> http://www.opensubscriber.com/message/linux-ide@vger.kernel.org/1671725.html
>
> Output seems to line up pretty much exactly, except specific sector
> numbers, of course.
>
prev parent reply other threads:[~2005-07-22 1:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-19 4:58 Problems w/ RAID-5/sata_promise/PDC20579 Jarrod Johnson
2005-07-22 1:23 ` Jarrod Johnson [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=fab4e42a0507211823236da64b@mail.gmail.com \
--to=jarrod.b.johnson@gmail.com \
--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).