From: Mark Lord <kernel@teksavvy.com>
To: Tejun Heo <tj@kernel.org>
Cc: Tobias Karnat <tobias.karnat@googlemail.com>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: sata_sil24: external raid storage mistaken as port multiplier
Date: Fri, 26 Nov 2010 15:13:44 -0500 [thread overview]
Message-ID: <4CF014F8.9000700@teksavvy.com> (raw)
In-Reply-To: <4CEFEC17.6060503@kernel.org>
On 10-11-26 12:19 PM, Tejun Heo wrote:
> On 11/24/2010 05:23 AM, Tobias Karnat wrote:
>> Hi,
>>
>> I got it fixed by removing ATA_FLAG_PMP from the SIL24_COMMON_FLAGS.
>>
>> Could someone turn this into a module option?
>>
>> The external raid case might in fact has a built-in port multiplier,
>> but the case can only be configured as raid0 and raid1.
>>
>> I suspect that Linux tries to to access the drives separately, which fails.
>
> Hmmm... well, libata is just sending SRST w/ the port number set to 15
> and the device is reporting that it is a port multipler to that.
> Depending on configuration these devices don't work too well when
> commanded as a PMP device. If you put it into JBOD mode, it will
> probably work fine. I have no idea why it still reports as a PMP
> device when configured as a virtual device.
>
> That said, yeah, it probably would be a good idea to add a
> libata.force param.
How about some form of auto-detection instead?
-ml
next prev parent reply other threads:[~2010-11-26 20:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-22 21:24 sata_sil24: external raid storage mistaken as port multiplier Tobias Karnat
2010-11-23 12:08 ` Tobias Karnat
2010-11-24 4:23 ` Tobias Karnat
2010-11-26 17:19 ` Tejun Heo
2010-11-26 20:13 ` Mark Lord [this message]
2010-11-26 20:16 ` Tejun Heo
2010-11-27 2:57 ` Mark Lord
2010-11-28 10:51 ` Tobias Karnat
2010-12-03 12:45 ` Tobias Karnat
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=4CF014F8.9000700@teksavvy.com \
--to=kernel@teksavvy.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.org \
--cc=tobias.karnat@googlemail.com \
/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).