SSC-2: Resolution for undecompressable data

Dave Peterson dap at cisco.com
Wed Jul 24 11:30:00 PDT 2002


* From the T10 Reflector (t10 at t10.org), posted by:
* "Dave Peterson" <dap at cisco.com>
*
Howdy Dennis,

Thanks, comments below...dap

> -----Original Message-----
> From: owner-t10 at t10.org [mailto:owner-t10 at t10.org]On Behalf Of
> Dennis.W.Painter at seagate.com
> Sent: Wednesday, July 24, 2002 11:10 AM
> To: T10 Reflector
> Subject: Re: SSC-2: Resolution for undecompressable data
>
>
> * From the T10 Reflector (t10 at t10.org), posted by:
> * Dennis.W.Painter at seagate.com
> *
>
> Hello,
>
> A minor point but "logical block" has a specific definition in SSC-2 and I
> would change
>
> ...Undecompressed data may be returned to the application client as a
> single variable length logical block with the ILI bit and INFORMATION
> fields set accordingly...
>
> to read:
>
> ...Undecompressed data may be returned to the application client as a
> single variable length block with the ILI bit and INFORMATION fields set
> accordingly....
>

Agreed.

>
> In the note I think the SSC-2 definitions would be better followed by
> changing:
>
>  ...more than one logical block, filemark, or setmark...
>
> to:
>
>  ... more than one logical element...
>

Ok with this. FYI, due to some letter ballot comments relating to the
various terms
used in SSC-2, the term element may (or may not) be changed in the near
future.

> and lastly, in the note, the reason the host should issue READ POSITION is
> because  "...the logical position is vendor specific following this
> condition...", not because of the logical element(s) that may be in the
> block returned.
>
Agreed, the last sentence in the note should be at the end of the preceding
paragraph.

>
> Cheers
> Dennis
>
>
>
>
>                     "Dave
>
>                     Peterson"            To:     "T10 Reflector"
> <t10 at t10.org>
>                     <dap at cisco.co        cc:
>
>                     m>                   Subject:     SSC-2:
> Resolution for undecompressable data
>                     Sent by:
>
>                     owner-t10 at t10
>
>                     .org
>
>
>
>
>
>                     07/22/02
>
>                     11:59 AM
>
>
>
>
>
>
>
>
>
> * From the T10 Reflector (t10 at t10.org), posted by:
> * "Dave Peterson" <dap at cisco.com>
> *
> Howdy All,
>
> Below is the working group proposed text:
>
> When compressed data is encountered on the medium that the device
> server is
> unable to decompress, the device server shall return CHECK CONDITION
> status.
> The sense key shall be set to MEDIUM ERROR, and the additional sense code
> shall be set to CANNOT DECOMPRESS USING DECLARED ALGORITHM. Undecompressed
> data may be returned to the application client as a single variable length
> logical block with the ILI bit and INFORMATION fields set accordingly. The
> logical position is vendor specific following this condition.
> Note XX: the undecompressed data may contain more than one logical block,
> filemark, or setmark. As such, the application client should issue a READ
> POSITION command following this condition to re-establish positioning.
>
> Let me know if there are any issues.
> Thanks...dap
>
> *
> * 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

*
* 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