[8557] in linux-scsi channel archive
Re: SCSI Enclosure Services support?
daemon@ATHENA.MIT.EDU (Jakub Jelinek)
Thu Apr 6 11:36:13 2000
Date: Thu, 6 Apr 2000 17:30:19 +0200
From: Jakub Jelinek <jakub@redhat.com>
To: sjbuller@us.ibm.com
Cc: mjacob@feral.com, linux-scsi@vger.rutgers.edu
Message-ID: <20000406173019.B9897@sunsite.ms.mff.cuni.cz>
Reply-To: Jakub Jelinek <jakub@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <872568B9.0053ABCC.00@d53mta04h.boulder.ibm.com>; from sjbuller@us.ibm.com on Thu, Apr 06, 2000 at 09:13:59AM -0600
On Thu, Apr 06, 2000 at 09:13:59AM -0600, sjbuller@us.ibm.com wrote:
>
>
>
> >What you're seeing there is SAF-TE, not SES. X'ing out the vendor is
> amusing-
> >given the ID it's set at: it looks like the 2nd GEM chip on a Sun D1000.
>
> Actually, it was an IBM Netfinity 7000M10.
>
> >If there's any interest here in this, I'll finish the ioctl version and
> put it
> >out there for you to play with. I did some toy management tools for
> reporting
> >this information- it's in the FreeBSD 4.0 release in /usr/share/examples.
>
> Looks like a circular argument. No SES/SAF-TE Linux support means
> the enclosures don't need to implement it. If no enclosures implement it
> there is no reason for Linux to support it.
>
> In the implementations I'm famailiar with, each enclosure would be
> represented
> by a /dev/sesX (x=0,1,2...) device for the monitoring software to play
> with.
Can't it be done completely in userland, using /dev/sg* and SCSI generic
ioctls?
When writing fc4 SCSI driver for Sun A5000 and Enterprise servers I played
with that for a while but as SES is only available in the A5000 array which
I don't have currently, I haven't done anything besides initial playing with
it.
Jakub
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
