Conclusive write operation dispersed storage network frame

Patent metadata

Field	Value
Publication number	US-9514090-B2
Application number	US-201414148380-A
Country	US
Kind code	B2
Filing date	Jan 6, 2014
Priority date	Apr 26, 2010
Publication date	Dec 6, 2016
Grant date	Dec 6, 2016

Abstract

A method begins by a processing module generating a payload of a dispersed storage network frame regarding a conclusive write request operation by generating one or more slice name fields of a payload to include one or more slice names corresponding to one or more write commit responses of a write request operation, wherein the conclusive write request operation is a conclusive phase of the write request operation. The method continues with the processing module generating one or more slice revision numbering fields of the payload, wherein each slice revision numbering field includes a slice revision number corresponding to an associated slice name of the one or more slice names. The method continues with the processing module generating a protocol header of the DSN frame by generating a payload length field of the protocol header to include a payload length and generating remaining fields of the protocol header.

First claim

What is claimed is:

1. One or more memory devices comprises:
a first memory section storing operational instructions that, when executed by a computing device, causes the computing device to:
generating a payload of a dispersed storage network (DSN) frame regarding a conclusive write request operation by:
generating one or more slice name fields of the payload to include one or more slice names corresponding to one or more write commit responses of a write request operation, wherein the conclusive write request operation is a conclusive phase of the write request operation; and
generating one or more slice revision numbering fields of the payload, wherein each slice revision numbering field includes a slice revision number corresponding to an associated slice name of the one or more slice names;

a second memory section storing operational instructions that, when executed by the computing device, causes the computing device to:
generate a protocol header of the DSN frame by:
generating a payload length field of the protocol header to include a payload length that represents length of the one or more slice name fields and length the one or more slice revision numbering fields; and
generating remaining fields of the protocol header; and

a third memory section storing operational instructions that, when executed by the computing device, causes the computing device to:
output, to a storage unit of the DSN, the DSN frame in order of the protocol header and one or more slice field pairs, wherein each of the one or more slice field pairs includes, in order, a slice name field of the one or more slice name fields and a slice revision numbering field of the one or more slice revision numbering fields, wherein the slice revision numbering field is associated with the slice name field.

2. The one or more memory devices of claim 1 , wherein the second memory section further stores operational instructions that, when executed by the computing device, causes the computing device to generate remaining fields of the protocol header by at least one of:
generating an operation code field to indicate a finalize write request operation when a threshold number of the one or more write commit responses have been received;
generating a protocol class field to indicate a protocol class for the finalize write request operation when the threshold number of the one or more write commit responses have been received; and
generating a protocol class version field to indicate a protocol class version for the finalize write request operation when the threshold number of the one or more write commit responses have been received.

3. The one or more memory devices of claim 1 , wherein the second memory section further stores operational instructions that, when executed by the computing device, causes the computing device to generate remaining fields of the protocol header by at least one of:
generating an operation code field to indicate an undo write request operation when a threshold number of the one or more write commit responses have not been received;
generating a protocol class field to indicate a protocol class for the undo write request operation when the threshold number of the one or more write commit responses have not been received; and
generating a protocol class version field to indicate a protocol class version for the undo write request operation when the threshold number of the one or more write commit responses have not been received.

4. The one or more memory devices of claim 1 , wherein the first memory section further stores operational instructions that, when executed by the computing device, causes the computing device to generate the one or more slice names by at least one of:
receiving the one or more slice names; and
selecting the one or more slice names from a slice names list.

Assignees

• Cleversafe Inc
• IBM

Inventors

• Baptist Andrew
• Leggette Wesley
• Resch Jason K
• Mark Zachary J
• Volvovski Ilya

Classifications

• G06F11/1076

  Parity data used in redundant arrays of independent storages, e.g. in RAID systems · CPC title

• G06F3/0619

  in relation to data integrity, e.g. data losses, bit errors · CPC title

• G06F3/064

  Management of blocks · CPC title

• G06F3/065

  Replication mechanisms · CPC title

• G06F3/067

  Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS] · CPC title