From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Anne Mulhern <amulhern@redhat.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: /sys/.../enclosure_device:<something> ?
Date: Wed, 13 Jan 2016 12:30:07 -0800 [thread overview]
Message-ID: <1452717007.2363.22.camel@HansenPartnership.com> (raw)
In-Reply-To: <1033193682.7255311.1452716104867.JavaMail.zimbra@redhat.com>
On Wed, 2016-01-13 at 15:15 -0500, Anne Mulhern wrote:
>
>
>
> ----- Original Message -----
> > From: "James Bottomley" <James.Bottomley@HansenPartnership.com>
> > To: "Anne Mulhern" <amulhern@redhat.com>,
> > linux-scsi@vger.kernel.org
> > Sent: Wednesday, January 13, 2016 2:15:05 PM
> > Subject: Re: /sys/.../enclosure_device:<something> ?
> >
> > On Wed, 2016-01-13 at 11:28 -0500, Anne Mulhern wrote:
> > > Hi!
> > >
> > > I'm looking for the most precise information available about the
> > > meaning of <something>
> > > and from what it is derived. I'm also interested in what the
> > > values
> > > in the files in that directory
> > > may mean. Could somebody point me there?
> >
> > It's in drivers/misc/enclosure.c:enclosure_link_name()
> >
>
> Thanks. I will do my best with that.
>
> > > Also, how can there be more than one enclosure_device
> > > subdirectory
> > > for the same device,
> > > or, alternatively, why isn't <something> stored in a file in the
> > > more
> > > regularly named directory
> > > /sys/.../enclosure_device?
> >
> > I'm not sure I parse the question, but if you're asking how can a
> > single enclosure bay appear to have more than one device, that's
> > when
> > there are multiple paths to the device.
>
> I'm afraid the word path is so overloaded...I'm assuming that you
> are talking about a multipathed environment, where two device nodes,
> say /dev/sdb, /dev/sdc correspond to the same disk, and are hence
> multipathed. Of course, in that case, it makes sense that both
> devices should share a bay. And that's what I observe.
Yes, that's what I meant.
> If I understand you correctly, then my question is actually the
> opposite. Why does it look as if the directories are set up so that
> there can be multiple bays for a single device...i.e., the directory
> naming scheme allows me to specify an arbitrary number of bays for
> /dev/sdb. It seems like there should never be more than one?
There is only one bay per device since a physical disk can't be in more
than one bay at once. Why do you think it was set up to allow >1?
James
> - mulhern
>
> > James
> >
> > > (It would be nice to be able to obtain the value of <something>
> > > using
> > > libudev's attribute
> > > lookup facilities, but making that value a part of the specially
> > > named directory enclosure_device:<something>
> > > makes such a process especially difficult.)
> > >
> > > Thanks,
> > >
> > > - mulhern
> > > --
> > > 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
> > >
> >
> > --
> > 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
> >
> --
> 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
>
next prev parent reply other threads:[~2016-01-13 20:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1790412140.7137014.1452701936079.JavaMail.zimbra@redhat.com>
2016-01-13 16:28 ` /sys/.../enclosure_device:<something> ? Anne Mulhern
2016-01-13 19:15 ` James Bottomley
2016-01-13 20:15 ` Anne Mulhern
2016-01-13 20:30 ` James Bottomley [this message]
2016-01-15 19:32 ` Anne Mulhern
2016-01-15 19:38 ` James Bottomley
2016-01-18 18:24 ` Anne Mulhern
2016-01-18 20:08 ` 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=1452717007.2363.22.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=amulhern@redhat.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