public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Clark <michael@metaparadigm.com>
To: "Martin K. Petersen" <mkp@mkp.net>
Cc: Matt_Domsch@Dell.com, mjacob@feral.com, linux-scsi@vger.kernel.org
Subject: Re: ANNOUNCE: saftemon - SCSI Enclosure monitor for linux
Date: Thu, 18 Apr 2002 12:43:55 +0800	[thread overview]
Message-ID: <3CBE4F0B.2010108@metaparadigm.com> (raw)
In-Reply-To: yq1elhdwt3i.fsf@austin.mkp.net

Martin K. Petersen wrote:

>>>>>>"Michael" == Michael Clark <michael@metaparadigm.com> writes:
>>>>>>
>
>Michael> The SES command set is supposedly documented in the SFF-8067
>Michael> specification developed by an X3 committee. I assume is
>Michael> different to SAF-TE and have removed the reference to it in
>Michael> the readme.
>
>Yes.  SES is the successor to SAF-TE.
>
>It's different in the sense that there's no SAF-TE processor device
>visible on the bus.  Instead devices on an SES-capable bus will have
>EnvServ set in the inquiry page.
>
>I have some sample code kicking around, if you're interested.  Also,
>the SES specs are official T10 ones (unlike SAF-TE).  You can download
>them off t10.org.
>

Thanks. Okay, i just had a quick look at the spec and yes, it's quite 
different to SAF-TE.

I don't have any SES devices to test on but I may think about 
abstracting saftemon to handle
more than one protocol for inquiring enclosures. The SES attributes 
match pretty closely although
SES is s superset of SAF-TE.

It probably makes sense to include SMART, SAF-TE and SES monitoring into 
s single
consistent package. I'm not using SMART as with most RAID controllers, 
you only see logical
devices and have no contact directly with the drives (unless you use 
SCSI passthrough APIs
althoug these are different from one RAID controller driver to the next).

~mc


  reply	other threads:[~2002-04-18  4:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-17 16:00 ANNOUNCE: saftemon - SCSI Enclosure monitor for linux Matt_Domsch
2002-04-18  1:11 ` Michael Clark
2002-04-18  3:19   ` Michael Clark
2002-04-18  4:04     ` Martin K. Petersen
2002-04-18  4:43       ` Michael Clark [this message]
2002-04-18  4:26   ` Matthew Jacob
2002-04-18  5:18     ` Michael Clark
  -- strict thread matches above, loose matches on Subject: below --
2002-04-25 11:20 Thomas Tonino
2002-04-17 16:21 Les Niles
2002-04-17 14:42 Matt_Domsch
2002-04-17 15:05 ` Mathieu Chouquet-Stringer
2002-04-17 15:23   ` Mathieu Chouquet-Stringer
2002-04-17 15:16 ` Michael Clark
2002-04-17 15:51 ` Matthew Jacob
2002-04-17 11:01 Michael Clark

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=3CBE4F0B.2010108@metaparadigm.com \
    --to=michael@metaparadigm.com \
    --cc=Matt_Domsch@Dell.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mjacob@feral.com \
    --cc=mkp@mkp.net \
    /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