public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@suse.de>
To: John Hughes <john@Calva.COM>
Cc: linux-scsi@vger.kernel.org
Subject: Re: ses enclosure stuff not working with Promise Vtrak J610S JBOD
Date: Wed, 04 Nov 2009 10:20:54 -0600	[thread overview]
Message-ID: <1257351654.2697.55.camel@mulgrave.site> (raw)
In-Reply-To: <4AF1A7E7.7070307@Calva.COM>

On Wed, 2009-11-04 at 17:12 +0100, John Hughes wrote:
> James Bottomley wrote:
> > Could you tell me what the enclosure page 0 (supported diagnostic pages)
> > and page 10 (additional information page that allows us to do the
> > matching) say?  I suspect the enclosure either doesn't support the page
> > needed for the matching or there's some problem with the way the
> > information is encoded.
> >   
> Ok, here we go.   (I wonder whether the "<<<additional: response too 
> short>>>" at the end of page 10 has something to do with the problem).

Possibly ... that tends to indicate the enclosure data returned stopped
in the middle of the actual specification ... although looking at the
output this doesn't seem to be the case.  The zeros at the end
definitely indicate we have enough data, just that the expected
termination doesn't seem to be present.

> # sg_ses -p 0 /dev/sg17
>   PROMISE   3U-SAS-16-D BP    0107
>     enclosure services device
> Supported diagnostic pages:
>   Supported diagnostic pages [0x0]
>   Configuration (SES) [0x1]
>   Enclosure status/control (SES) [0x2]
>   Threshold In/Out (SES) [0x5]
>   Enclosure busy (SES-2) [0x9]
>   Additional (device) element status (SES-2) [0xa]

This may also be a problem.  My enclosure returns page 7 as well.  The
traversal routine has special code to try to parse page 10 without a
page 7 ... I don't think I actually ever tested that ...

James



  reply	other threads:[~2009-11-04 16:20 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-04 13:00 ses enclosure stuff not working with Promise Vtrak J610S JBOD John Hughes
2009-11-04 15:17 ` John Hughes
2009-11-04 15:22 ` James Bottomley
2009-11-04 15:53   ` John Hughes
2009-11-04 16:07     ` James Bottomley
2009-11-04 16:12       ` John Hughes
2009-11-04 16:20         ` James Bottomley [this message]
2009-11-04 18:01           ` John Hughes
2009-11-04 18:05             ` James Bottomley
2009-11-04 18:10               ` John Hughes
2009-11-05  9:41             ` John Hughes
2009-11-05 15:30               ` John Hughes
2009-11-05 15:44                 ` James Bottomley
2009-11-04 15:51 ` John Hughes
2009-11-04 16:54   ` John Hughes
2009-11-04 16:55   ` John Hughes

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=1257351654.2697.55.camel@mulgrave.site \
    --to=james.bottomley@suse.de \
    --cc=john@Calva.COM \
    --cc=linux-scsi@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