Incompatibility between SES-2 r11 and r10?

Fore, Chris Chris_Fore at adaptec.com
Wed Apr 13 14:37:33 PDT 2005


* From the T10 Reflector (t10 at t10.org), posted by:
* "Fore, Chris" <Chris_Fore at adaptec.com>
*
Rob's suggestion would solve our concern with this change. 

:: R. Chris Fore
:: Principal Engineer - Core Storage Services 
:: Adaptec, Research Triangle Park, NC 
:: chris_fore at adaptec.com 


-----Original Message-----
From: Elliott, Robert (Server Storage) [mailto:elliott at hp.com] 
Sent: Wednesday, April 13, 2005 4:18 PM
To: dougg at torque.net; t10 at t10.org
Cc: Fore, Chris
Subject: RE: Incompatibility between SES-2 r11 and r10? 

We could define bit 4 byte 0 set to one means the structure follows the
r11+ format.

---
Rob Elliott, HP Server Storage
elliott at hp.com  

> -----Original Message-----
> From: owner-t10 at t10.org [mailto:owner-t10 at t10.org] On Behalf 
> Of Douglas Gilbert
> Sent: Tuesday, April 12, 2005 4:01 PM
> To: t10 at t10.org
> Cc: Chris_Fore at adaptec.com
> Subject: Re: Incompatibility between SES-2 r11 and r10? 
> 
> * From the T10 Reflector (t10 at t10.org), posted by:
> * Douglas Gilbert <dougg at torque.net>
> *
> Yes, I also noticed major differences in the SES-2
> Additional Element Status diagnostic page between
> r11 and r10.
> 
> Currently there is only one SES-2 version descriptor:
> 3e0h "SES-2 (no version claimed)" [ref: spc3r22a.pdf
> Table D.14]. Perhaps more SES-2 version descriptors
> could be added. of course, version descriptors are futile
> unless target firmware supports them (in the response
> of a standard INQUIRY).
> 
> Another approach would be to use a version field like MMC
> features.
> 
> Doug Gilbert
> 
> 
> *
> * For T10 Reflector information, send a message with
> * 'info t10' (no quotes) in the message body to majordomo at t10.org
> 
*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org





More information about the T10 mailing list