Check operation dispersed storage network frame

• US 8,649,399 B2
• Filed: 04/05/2011
• Issued: 02/11/2014
• Est. Priority Date: 04/26/2010
• Status: Expired due to Fees

• Current Assignee: Pure Storage, Inc.
• Original Assignee: Cleversafe Incorporated (International Business Machines Corporation)
• Inventors: Baptist, Andrew, Leggette, Wesley, Resch, Jason K., Mark, Zachary J., Volvovski, Ilya, Dhuse, Greg
• Primary Examiner(s): Jiang, Charles C
• Application Number:
  US13/080,446
• Publication Number:
  US 20110264950A1
• Time in Patent Office: 1,043 Days
• Field of Search: 370241-252, 370464-472, 370/474, 707/1, 707/10, 709/201, 709208-219, 711100-173
• US Class Current: 370/474
• CPC Class Codes: G06F 11/1076 Parity data used in redundant arrays of independent storages, e.g. in RAID systems
• CPC Class Codes: G06F 15/167 using a common memory, e.g. mailbox
• CPC Class Codes: G06F 3/0619 in relation to data integrity, e.g. data losses, bit errors
• CPC Class Codes: G06F 3/064 Management of blocks
• CPC Class Codes: G06F 3/0644 Management of space entities, e.g. partitions, extents, pools
• CPC Class Codes: G06F 3/065 Replication mechanisms
• CPC Class Codes: G06F 3/067 Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
• CPC Class Codes: H04L 67/1097 for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
• CPC Class Codes: H04L 69/22 Parsing or analysis of headers
• CPC Class Codes: H04L 69/26 Special purpose or proprietary protocols or architectures network applications for proprietary or special purpose networking environments H04L67/12

Abstract

A method begins by a processing module generating a payload section of a dispersed storage network (DSN) frame regarding a check request operation by generating one or more slice name fields of the payload section to include one or more slice names corresponding to one or more encoded data slices and generating a transaction number field of the payload section to include a transaction number corresponding to the check request operation. 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 that represents a length of the payload section and generating remaining fields of the protocol header.

Claims

1. A method for executing by a computing device for a check request operation, the method comprises:

generating a payload section of a dispersed storage network (DSN) frame regarding the check request operation by;

generating one or more slice name fields of the payload section to include one or more slice names corresponding to one or more encoded data slices; and

generating a transaction number field of the payload section to include a transaction number corresponding to the check request operation; and

generating a protocol header of the DSN frame by;

generating a payload length field of the protocol header to include a payload length that represents a length of the payload section; and

generating remaining fields of the protocol header.

2. The method of claim 1 further comprises:

outputting the DSN frame in order of the protocol header, the transaction number field, and the one or more slice name fields.

3. The method of claim 1, wherein generating remaining fields of the protocol header comprises at least one of:

generating an operation code field to indicate the check request operation;

generating a protocol class field to indicate a protocol class for the check request operation; and

generating a protocol class version field for the check request operation.

4. The method of claim 1 further comprises:

generating the transaction number by;

obtaining a clock value;

multiplying the clock value by a predetermined multiplier to produce an expanded clock value; and

summing the expanded clock value and a random number to produce the value, wherein a number of digits of the random number is substantially the same as a number of digits of the predetermined multiplier.

5. The method of claim 1 further comprises:

determining a length of the transaction number;

determining a length for each of the one or more slices names;

determining a number of slice names of the one or more slices names; and

generating the payload length for the payload length field based on the length of the transaction number, the length for each of the one or more slices names, and the number of slice names of the one or more slices names.

6. The method of claim 1 further comprises:

generating a plurality of DSN frames regarding the check request operation, wherein the plurality of DSN frames includes the DSN frame.

7. A method for execution by a computing device for a check response operation, the method comprises:

generating a payload of a dispersed storage network (DSN) frame regarding one or more slice names of the check response operation to include one or more slice information sections,

wherein generating a slice information section of the one or more slice information sections includes;

generating a slice revision count field to indicate a number of revisions of the slice name included in the slice information section; and

generating a slice revision numbering field for each of the revisions of the slice name to include a revision number to produce one or more slice revision numbering fields; and

generating a protocol header of the DSN frame by;

generating a payload length field of the protocol header to include a payload length that represents a length of the one or more slice information sections; and

generating remaining fields of the protocol header.

8. The method of claim 7 further comprises:

outputting the DSN frame in order of the protocol header and the one or more slice information sections, and, within each of the one or more slice information sections, in an order of the slice revision count field and the one or more slice revision numbering fields.

9. The method of claim 7, wherein generating remaining fields of the protocol header comprises at least one of:

generating an operation code field to indicate the check response operation;

generating a protocol class field to indicate a protocol class for the check response operation; and

generating a protocol class version field for the check response operation.

10. The method of claim 7 further comprises:

establishing an error condition based on one or more of;

the one or more slice names being associated with a locked encoded data slice state, a transaction number error, the one or more slice names are associated with one or more encoded data slices that are not locally stored, and a check request message is not authorized; and

discarding the DSN frame when the error condition is established.

11. The method of claim 7, wherein generating the payload of the DSN frame further comprises:

generating a slice length field for each of the revisions of the slice name to include a length of a corresponding encoded data slice.

12. A computer comprises:

an interface;

a memory; and

a processor operably coupled to the interface and to the memory, wherein the processor is operable to;

generate a payload section of a dispersed storage network (DSN) frame regarding a check request operation by;

generating one or more slice name fields of the payload section to include one or more slice names corresponding to one or more encoded data slices; and

generating a transaction number field of the payload section to include a transaction number corresponding to the check request operation; and

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 a length of the payload section; and

generating remaining fields of the protocol header.

13. The computer of claim 12, wherein the processing module processor further functions to:

output, via the interface, the DSN frame in order of the protocol header, the transaction number field, and the one or more slice name fields.

14. The computer of claim 12, wherein the processor further functions to generate the remaining fields of the protocol header by at least one of:

generating an operation code field to indicate a check request operation;

generating a protocol class field to indicate a protocol class for the check request operation; and

generating a protocol class version field for the check request operation.

15. The computer of claim 12, wherein the processor further functions to:

generate the transaction number by;

obtaining a clock value;

multiplying the clock value by a predetermined multiplier to produce an expanded clock value; and

summing the expanded clock value and a random number to produce the value, wherein a number of digits of the random number is substantially the same as a number of digits of the predetermined multiplier.

16. The computer of claim 12, wherein the processor further functions to:

determine a length of the transaction number;

determine a length for each of the one or more slices names;

determine a number of slice names of the one or more slices names; and

generate the payload length for the payload length field based on the length of the transaction number, the length for each of the one or more slices names, and the number of slice names of the one or more slices names.

17. The computer of claim 12, wherein the processor further functions to:

generate a plurality of DSN frames regarding the check request operation, wherein the plurality of DSN frames includes the DSN frame.

18. A computer comprises:

an interface;

a memory; and

a processor operably coupled to the interface and to the memory, wherein the processor is operable to;

generate a payload of a dispersed storage network (DSN) frame regarding one or more slice names of the check response operation to include one or more slice information sections, wherein generating a slice information section of the one or more slice information sections includes;

generating a slice revision count field to indicate a number of revisions of the slice name included in the slice information section; and

generating a slice revision numbering field for each of the revisions of the slice name to include a revision number to produce one or more slice revision numbering fields; and

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 a length of the one or more slice information sections; and

generating remaining fields of the protocol header.

19. The computer of claim 18, wherein the processor further functions to:

output, via the interface, the DSN frame in order of the protocol header and the one or more slice information sections, and, within each of the one or more slice information sections, in an order of the slice revision count field and the one or more slice revision numbering fields.

20. The computer of claim 18, wherein the processor further functions to generate the remaining fields of the protocol header by at least one of:

generating an operation code field to indicate a check response operation;

generating a protocol class field to indicate a protocol class for the check response operation; and

generating a protocol class version field for the check response operation.

21. The computer of claim 18, wherein the processor further functions to:

establish an error condition based on one or more of;

the one or more slice names being associated with a locked encoded data slice state, a transaction number error, the one or more slice names are associated with one or more encoded data slices that are not locally stored, and a read request message is not authorized; and

discard the DSN frame when the error condition is established.