linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: Tomasz Torcz <tomek@pipebreaker.pl>
Cc: linux-scsi@vger.kernel.org
Subject: Re: can't access LUN >2TB with aic7xxx, Infortrend EonStor and 2.6.31-rc1
Date: Mon, 29 Jun 2009 07:34:31 -0600	[thread overview]
Message-ID: <20090629133431.GM5480@parisc-linux.org> (raw)
In-Reply-To: <20090629130835.GA3657@mother.pipebreaker.pl>

On Mon, Jun 29, 2009 at 03:08:35PM +0200, Tomasz Torcz wrote:
>   recently I've acquired Infortrend EonStor A16U-G2421 array
> with 16x 500GB SATA drives inside. It is connected via:
> 04:00.0 SCSI storage controller: Adaptec AHA-2940U2/U2W
> to host running Fedora 12 with following kernel:
> 2.6.31-0.33.rc1.git2.fc12.x86_64
> 
>   When I export LUN >2TB from array I got following errors:
> 
> scsi 5:0:0:1: Direct-Access     VW       VRU1610          347G PQ: 0 ANSI: 5
> scsi target5:0:0: FAST-40 WIDE SCSI 80.0 MB/s ST (25 ns, offset 127)
> scsi5:A:0:1: Tagged Queuing enabled.  Depth 4
> sd 5:0:0:1: Attached scsi generic sg3 type 0
> sd 5:0:0:1: [sdd] READ CAPACITY(16) failed
> sd 5:0:0:1: [sdd] Result: hostbyte=DID_ABORT driverbyte=DRIVER_OK
> sd 5:0:0:1: [sdd] Sense not available.
> 
>   According to manufacturer, this array supports LUNs up to 64TB, 
> although >2TB LUNs require enigmatic ,,support from OS side''.
> I was under impression that aic7xxx supports them, but it seems
> not true. What can I tweak on the Linux side to use 6TB volumes?

SCSI commands come in different sizes.  Drivers are assumed to support
commands up to 12 bytes long, unless they report otherwise by setting
their max_cmd_len parameter.  Unfortunately, the command that reports
the device capacity for devices over 2TB is a 16 byte command, and the
aic7xxx driver doesn't claim it supports 16 byte commands, so we refuse
to even send it to the driver.

It's possible the aic7xxx hardware does support 16 byte commands.  If so,
this is an easy fix.  If it doesn't, you could try replacing the card
with one that does (for example, the LSI 8xx and 10xx cards all support
16 byte commands).

You could also go for a configuration fix where you reconfigure the array
with LUNs below 2TB and then use MD or DM to stitch them back together
into a single device.

Let's hope someone who understands the aic7xxx hardware can tell us
whether it supports 16 byte commands or not.

-- 
Matthew Wilcox				Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours.  We can't possibly take such
a retrograde step."

  reply	other threads:[~2009-06-29 13:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-29 13:08 can't access LUN >2TB with aic7xxx, Infortrend EonStor and 2.6.31-rc1 Tomasz Torcz
2009-06-29 13:34 ` Matthew Wilcox [this message]
2009-06-29 13:40   ` Drew
2009-06-29 13:47     ` Matthew Wilcox
2009-06-29 14:54       ` Drew
2009-06-29 13:46   ` Matthew Wilcox
2009-06-29 16:13     ` Tomasz Torcz
2009-06-30  9:40     ` Tomasz Torcz
2009-06-30 14:45       ` James Bottomley
2009-06-30 15:48       ` James Bottomley
2009-07-01  6:10         ` Tomasz Torcz
2009-07-01 14:19           ` James Bottomley
2009-06-29 14:33 ` James Bottomley
2009-06-29 14:56   ` Matthew Wilcox

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=20090629133431.GM5480@parisc-linux.org \
    --to=matthew@wil.cx \
    --cc=linux-scsi@vger.kernel.org \
    --cc=tomek@pipebreaker.pl \
    /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).