public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Lars Täuber" <taeuber@bbaw.de>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: MPTSAS: ("activate status led" | "find disc") in external enclosure
Date: Tue, 22 Apr 2008 09:18:37 +0200	[thread overview]
Message-ID: <20080422091837.12790125.taeuber@bbaw.de> (raw)
In-Reply-To: <1208791005.3640.10.camel@localhost.localdomain>

James Bottomley <James.Bottomley@HansenPartnership.com> schrieb:
> On Mon, 2008-04-21 at 11:01 +0200, Lars Täuber wrote:
> > # ls /sys/class/enclosure/*/
> > /sys/class/enclosure/6:0:16:0/:
> > 0  10  12  14  2  4  6  8  components  subsystem
> > 1  11  13  15  3  5  7  9  device      uevent
> > 
> > /sys/class/enclosure/6:0:33:0/:
> > 0  10  12  14  2  4  6  8  components  subsystem
> > 1  11  13  15  3  5  7  9  device      uevent
> > 
> > This is two times the same enclosure.
> 
> That's unusual .. to have two devices managing the same enclosure, but
> if you only have 16 slots and not 32, I suppose it must be so.

I use both external connections to both expanderboards of the enclosure just for redundancy.


> > monosan:/sys/class/enclosure/6:0:16:0/0 # ls -l
> > insgesamt 0
> > -rw-r--r-- 1 root root 4096 21. Apr 10:48 active
> > -rw-r--r-- 1 root root 4096 21. Apr 10:48 fault
> > -rw-r--r-- 1 root root 4096 21. Apr 10:48 locate
> > -rw-r--r-- 1 root root 4096 21. Apr 10:48 status
> > lrwxrwxrwx 1 root root    0 21. Apr 10:46 subsystem -> ../../../enclosure_component
> > -r--r--r-- 1 root root 4096 21. Apr 10:48 type
> > --w------- 1 root root 4096 21. Apr 10:48 uevent
> > 
> > There seems to be no device link if I understood you correctly.
> > Is the subdirctory numbering somehow in relation to the SCSI ID?
> 
> If the slot is populated a device link should appear (this
> is the tricky bit because the ses driver uses VPD inquiries to match up
> the reported disk, assuming the enclosure reports it, to the actual one.
> These work for SAS disks, but not for SATA ones).

So this will never work for the SATA discs in our enclosure, right? Or is there a chance with asking LSI to do something in their firmware?

Seems I have no chance to get to know which slot contains the failed drive without a shutdown. Bad luck.

But thanks alot anyway.
Best regards
Lars
--
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:[~2008-04-22  7:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-18 10:41 MPTSAS: ("activate status led" | "find disc") in external enclosure Lars Täuber
2008-04-18 14:29 ` James Bottomley
2008-04-21  9:01   ` Lars Täuber
2008-04-21 15:16     ` James Bottomley
2008-04-22  7:18       ` Lars Täuber [this message]
2008-04-22 15:44         ` Moore, Eric
2008-04-23  8:11           ` Lars Täuber
2008-04-23 15:39             ` Moore, Eric
2008-04-22 16:12         ` James Bottomley
2008-04-23  7:55           ` Lars Täuber

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=20080422091837.12790125.taeuber@bbaw.de \
    --to=taeuber@bbaw.de \
    --cc=James.Bottomley@HansenPartnership.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