public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Ankit Jain <jankit@suse.de>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: linux-scsi <linux-scsi@vger.kernel.org>, Hannes Reinecke <hare@suse.de>
Subject: Re: [PATCH] ses: Handle non-unique element descriptors
Date: Mon, 11 Jul 2011 15:54:14 +0530	[thread overview]
Message-ID: <4E1ACF4E.2010307@suse.de> (raw)
In-Reply-To: <1309820435.2606.43.camel@mulgrave>

On 07/05/2011 04:30 AM, James Bottomley wrote:
> On Tue, 2011-07-05 at 04:29 +0530, Ankit Jain wrote:
>> On 07/04/2011 09:05 PM, James Bottomley wrote:
>>> On Mon, 2011-07-04 at 20:46 +0530, Ankit Jain wrote:
>>>> Some SES devices give non-unique Element Descriptors as part of the
>>>> Element Descriptor diag page. Since we use these for creating sysfs
>>>> entries, they need to be unique.
>>>>
>>>> Eg:
>>>> $ sg_ses -p 7 /dev/sg0
>>>>   FTS CORP  TXS6_SAS20BPX12   0500
>>>>     enclosure services device
>>>> Element descriptor In diagnostic page:
>>>>   generation code: 0x0
>>>>   element descriptor by type list
>>>>     Element type: Array device, subenclosure id: 0
>>>>       Overall descriptor: ArrayDevicesInSubEnclsr0
>>>>       Element 1 descriptor: ArrayDevice00
>>>>       Element 2 descriptor: ArrayDevice01
>>>>       Element 3 descriptor: ArrayDevice02
>>>>       Element 4 descriptor: ArrayDevice03
>>>>       Element 5 descriptor: ArrayDevice03
>>>>       Element 6 descriptor: ArrayDevice03
>>>>       Element 7 descriptor: ArrayDevice03
>>>>       Element 8 descriptor: ArrayDevice03
>>>>       Element 9 descriptor: ArrayDevice03
>>>>       Element 10 descriptor: ArrayDevice03
>>>>       Element 11 descriptor: ArrayDevice03
>>>>       Element 12 descriptor: ArrayDevice03
>>>
>>> What is the external visible labelling of this topology?  It's
>>> completely weird that the enclosure would burn in non-unique names
>>> unless there's some reason for it.
>>
>> I'm not sure what you mean by "external visible labelling". The system has a
>> SAS expanded backplane. I don't have access to the hardware now, but p7 looked
>> like this:
> 
> The element descriptors usually correspond with labelling on the case of
> whatever it is the enclosure is embedded in. Their job is to describe
> the location of the device, so they usually get burned in with whatever
> the default labelling scheme for the physical device is.  So what I want
> to know is what is the labelling scheme in this case?

I don't have direct access to the box, so I asked the person who does,
and he says: "the labelling is just 1-12 unless I'm mistaken.".

The duplicate descriptors is a firmware bug, but since the specification
doesn't say that these have to be unique, we should handle these, IMHO.

-- 
Ankit Jain
SUSE Labs

      reply	other threads:[~2011-07-11 10:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-04 15:16 [PATCH] ses: Handle non-unique element descriptors Ankit Jain
2011-07-04 15:35 ` James Bottomley
2011-07-04 22:59   ` Ankit Jain
2011-07-04 23:00     ` James Bottomley
2011-07-11 10:24       ` Ankit Jain [this message]

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=4E1ACF4E.2010307@suse.de \
    --to=jankit@suse.de \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=hare@suse.de \
    --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