From: Roger Heflin <rheflin@atipa.com>
To: Roger Heflin <rheflin@atipa.com>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: sata_mv issues with more than 1 disk in FC5 2.6.16-1.2096
Date: Thu, 20 Apr 2006 14:33:29 -0500 [thread overview]
Message-ID: <4447E209.4050802@atipa.com> (raw)
In-Reply-To: <4447C183.3040000@atipa.com>
Roger Heflin wrote:
> Hello,
>
> I know the FC5 2.6.16-1.2096 is based off of one of the 2.6.16
> stable releases. I am not sure exactly which one this is based
> on.
>
> I have several machines with this controller, the ones with a single
> disks all work correctly using the Marvell controller.
>
> An identical MB/controller/chassis fails when there are 2 disks
> using software mirroring. We have tested with 2 separate chassis,
> both exhibit the same failure.
>
> Moving the 2 disks to a different built-in sata controller
> (sata_nv) results in the disks and the mirror working
> correctly.
>
> The errors that it returns are:
> ata4: status=0xd0 { Busy }
> ata2: status=0xd0 { Busy }
> And the machine is terribly slow while this error is happening.
> The error appears to be happening when the disks are trying
> to be mounted.
>
> We have tested the disk on a couple of different combinations of
> ports and this does not seem to change anything.
>
> The single disk machines don't get this error like the 2 disk
> machines, though they do get this error, every 30 minutes
> or so (probably from smartd), but this error does not
> appear to be causing issues.
> Apr 19 16:26:19 lab229 kernel: ata1: status=0xd0 { Busy }
> Apr 19 16:26:19 lab229 kernel: ATA: abnormal status 0xD0 on
> port 0xFFFFC2001012211C
>
> Any thoughts?
>
> Roger
And at least one FC5 2.6.15 variant has the same behavior, so it
is not just on the 2.6.16.x variants.
Roger
prev parent reply other threads:[~2006-04-20 19:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-20 17:14 sata_mv issues with more than 1 disk in FC5 2.6.16-1.2096 Roger Heflin
2006-04-20 19:33 ` Roger Heflin [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=4447E209.4050802@atipa.com \
--to=rheflin@atipa.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox