All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ming Zhang <mingz@ele.uri.edu>
To: "Salyzyn, Mark" <mark_salyzyn@adaptec.com>
Cc: Linux SCSI <linux-scsi@vger.kernel.org>
Subject: RE: SAI_READ_CAPACITY_16?
Date: Wed, 06 Apr 2005 14:32:49 -0400	[thread overview]
Message-ID: <1112812369.2883.73.camel@localhost.localdomain> (raw)
In-Reply-To: <60807403EABEB443939A5A7AA8A7458BFF22BD@otce2k01.adaptec.com>

welcome. let us know if works. thx.

ming

On Wed, 2005-04-06 at 14:30, Salyzyn, Mark wrote:
> Thanks, needed to set shost->max_cmd_len to 16 in the driver.
> 
> Sincerely -- Mark Salyzyn
> 
> -----Original Message-----
> From: Ming Zhang [mailto:mingz@ele.uri.edu] 
> Sent: Wednesday, April 06, 2005 12:12 PM
> To: Salyzyn, Mark
> Cc: Linux SCSI
> Subject: Re: SAI_READ_CAPACITY_16?
> 
> we tested several iSCSI initiator/target combinations that work with
> >2TB devices in current 2.6.11.x kernel.
> 
> our experience is that some code only support cdb len 10 or 12. you need
> 16.
> 
> Ming
> 
> 
> On Wed, 2005-04-06 at 12:00, Salyzyn, Mark wrote:
> > Troubled spoofing back >2TB support in the aacraid driver.
> > 
> > For some reason, sd_read_capacity (in sd.c) in the 2.6.9-5.EL (RHEL4)
> > kernel is not issuing the SERVICE_REQUEST_IN+SAI_READ_CAPACITY_16
> > command to the queuecommand handler (the handler is not even called),
> > even though it instruments up that the command is issued (and returns
> > not supported). The READ_CAPACITY call makes it through successfully
> > indicating 0xFFFFFFFF capacity to trigger the SAI_READ_CAPACITY_16
> > request fine. Could there be a bug in the scsi layers reissuing
> commands
> > reusing the request structure misdirecting the requests?
> > 
> > The only changes to the current tree appear to be in the handling of
> the
> > request sense information, so I expect the same behavior from
> > latest/greatest.
> > 
> > Any successes in the current tree with >2TB support being reported by
> > the SAI_READ_CAPACITY_16 call?
> > 
> > Sincerely -- Mark Salyzyn
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-scsi"
> in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 


  reply	other threads:[~2005-04-06 18:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-06 18:30 SAI_READ_CAPACITY_16? Salyzyn, Mark
2005-04-06 18:32 ` Ming Zhang [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-04-06 16:00 SAI_READ_CAPACITY_16? Salyzyn, Mark
2005-04-06 16:11 ` SAI_READ_CAPACITY_16? Ming Zhang
2005-04-06 18:27 ` SAI_READ_CAPACITY_16? James Bottomley

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=1112812369.2883.73.camel@localhost.localdomain \
    --to=mingz@ele.uri.edu \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mark_salyzyn@adaptec.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 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.