From: James Bottomley <James.Bottomley@steeleye.com>
To: "tester7 A." <benew666@hotmail.com>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>, tech@storageone.co.kr
Subject: Re: QLA2300, Infortrand and LBD?
Date: 21 Jun 2004 09:09:44 -0500 [thread overview]
Message-ID: <1087826985.1797.14.camel@mulgrave> (raw)
In-Reply-To: <BAY22-F23Fi1dJRdjd8000a113d@hotmail.com>
On Sun, 2004-06-20 at 03:43, tester7 A. wrote:
> SCSI device sdc: 3022966784 512-byte hdwr sectors (1547759 MB)
> SCSI device sdc: drive cache: write through
> sdc: sdc1
> Attached scsi disk sdc at scsi3, channel 0, id 0, lun 0
The drive itself replied with that capacity, which is incorrect. It's
supposed to reply with the largest possible capacity (0xffffffff) and we
use that as a signal to retry with READ_CAPACITY_16.
Could you contact the support line of the array and make sure of two
things:
1) It does actually support single LUNs with a capacity of >2TB (lots of
arrays don't)
2) And if 1) is true, why is it not responding correctly to the READ
CAPACITY(10)? The spec (spc-2 Rev 8, 5.2.11) says "If the number of
logical blocks exceeds the maximum value[...]the device server shall
transfer FFFFFFFFh in the RETURNED LOGICAL BLOCK ADDRESS field"
James
next prev parent reply other threads:[~2004-06-21 14:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-20 8:43 QLA2300, Infortrand and LBD? tester7 A.
2004-06-21 14:09 ` James Bottomley [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-21 1:24 tester7 A.
2004-06-21 13:41 Frank Borich
2004-06-21 14:28 Frank Borich
2004-06-21 14:32 ` James Bottomley
2004-06-22 0:31 tester7 A.
2004-07-28 13:46 Frank Borich
2004-07-28 14:17 ` James Bottomley
2004-07-29 13:17 Frank Borich
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=1087826985.1797.14.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=benew666@hotmail.com \
--cc=linux-scsi@vger.kernel.org \
--cc=tech@storageone.co.kr \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.