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: Thu, 05 Nov 2009 09:44:15 -0600 [thread overview]
Message-ID: <1257435855.2753.43.camel@mulgrave.site> (raw)
In-Reply-To: <4AF2EFA4.4080004@Calva.COM>
On Thu, 2009-11-05 at 16:30 +0100, John Hughes wrote:
> John Hughes wrote:
> > One problem with the patch is that, since I don't have a page 7 (bay
> > names) it's using the "enclosure component index" as the name, and
> > that (at least for me) seems to be an index starting from zero, where
> > my bays are numbered from one.
> >
> > sg_ses shows a "bay number", I think I'll try to make the patch look
> > for the bay number and make the name something like "bay-nn" if there
> > is a bay number.
> Doesn't work because bays without a device don't show a bay number and
> hot-plugging a device doesn't make things change dynamically.
Let me dig around in the standards. My instinct from the implementation
notes was that page 7 was more likely to be present than page 10, so
that's how I coded it. There may still be a way to get the slot number
in a persistent fashion without the actual page telling you this.
> Buggeration.
Welcome to the wonderful world of SCSI standards implementation.
James
next prev parent reply other threads:[~2009-11-05 15:44 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
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 [this message]
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=1257435855.2753.43.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