Check operation dispersed storage network frame

• US 9,749,419 B2
• Filed: 11/10/2016
• Issued: 08/29/2017
• Est. Priority Date: 04/26/2010
• Status: Active Grant

• Current Assignee: Pure Storage, Inc.
• Original Assignee: International Business Machines Corporation
• Inventors: Baptist, Andrew, Leggette, Wesley, Resch, Jason K., Mark, Zachary J., Volvovski, Ilya, Dhuse, Greg
• Primary Examiner(s): KAMARA, MOHAMED A
• Application Number:
  US15/348,099
• Publication Number:
  US 20170063993A1
• Time in Patent Office: 292 Days
• 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 includes sending a set of check request messages to a set of storage units. A first check request message of the set of check request messages includes a first group of slice names that includes a first slice name from each of a plurality of sets of slice names, and the plurality of sets of slices names corresponds to a plurality of sets of encoded data slices. The method further includes receiving, by a first storage unit, the first check request message, determining a first group of slice information, and sending first check response message, where the first check response message includes the first group of slice information. The method further includes interpreting the first check response message in light of the first group of slice names to identify one or more encoded data slices of the plurality of sets of encoded data slices in need of rebuilding.

Claims

1. A method comprises:

sending, by a computing device of a dispersed storage network (DSN), a set of check request messages to a set of storage units of the DSN, wherein a first check request message of the set of check request messages includes a first group of slice names that includes a first slice name from each of a plurality of sets of slice names, wherein a plurality of data segments are dispersed storage error encoded into a plurality of sets of encoded data slices, and wherein the plurality of sets of slice names corresponds to the plurality of sets of encoded data slices;

receiving, by a first storage unit of the set of storage units, the first check request message;

determining, by the first storage unit, a first group of slice information in response to the first check request message;

sending, by the first storage unit, a first check response message to the computing device, wherein the first check response message includes the first group of slice information; and

interpreting, by the computing device, the first check response message in light of the first group of slice names to identify one or more encoded data slices of the plurality of sets of encoded data slices in need of rebuilding.

2. The method of claim 1 further comprises:

generating, by the computing device, the first check request message to include a header section and a payload section;

the payload section includes;

a plurality of slice name fields for containing the first group of slice names; and

a common transaction number field for containing a common transaction number corresponding to a check request operation; and

the protocol header includes one or more of;

a payload length field for containing a payload length that represents a length of the payload section;

an operation code field for containing an indicate the check request operation;

a protocol class field for containing a protocol class for the check request operation; and

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

3. The method of claim 1 further comprises:

generating, by the first storage unit, the first check response message to include a header section and a payload section;

the payload section includes a plurality of slice information sections corresponding to the first group of slice information, wherein a first slice information section of the plurality of slice information sections corresponds to a first slice name of the first group of slice names and includes one or more of;

a slice revision count;

a slice revision numbering; and

a slice length; and

the protocol header includes one or more of;

a payload length field for containing a payload length that represents a length of the payload section;

an operation code field for containing an indicate the check request operation;

a protocol class field for containing a protocol class for the check request operation; and

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

4. The method of claim 1, wherein the interpreting the first check response message comprises:

for a first slice name of the first group of slice names, comparing a slice revision number of a first slice information section of a plurality of slice information sections of the first check response message with a known revision level;

when the comparing of the slice revision number compares unfavorably with the known revision level, identifying an encoded data slice associated with the first slice name is in need of rebuilding.

5. The method of claim 1, wherein the interpreting the first check response message comprises:

for a first slice name of the first group of slice names, comparing a slice length of a first slice information section of a plurality of slice information sections of the first check response message with a known slice length; and

when the comparing of the slice length compares unfavorably with the known slice length, identifying an encoded data slice associated with the first slice name is in need of rebuilding.

6. The method of claim 1 further comprises:

receiving, by a second storage unit of the set of storage units, a second check request message;

determining, by the second storage unit, a second group of slice information in response to the second check request message;

sending, by the second storage unit, a second check response message to the computing device, wherein the second check response message includes the second group of slice information; and

interpreting, by the computing device, the second check response message in light of the second group of slice names to identify one or more other encoded data slices of the plurality of sets of encoded data slices in need of rebuilding.

7. A computer readable memory comprises:

a first memory element that stores operational instructions that, when executed by a computing device of a dispersed storage network (DSN), cause the computing device to;

send a set of check request messages to a set of storage units of the DSN, wherein a first check request message of the set of check request messages includes a first group of slice names that includes a first slice name from each of a plurality of sets of slice names, wherein a plurality of data segments are dispersed storage error encoded into a plurality of sets of encoded data slices, and wherein the plurality of sets of slice names corresponds to the plurality of sets of encoded data slices;

a second memory element that stores operational instructions that, when executed by a first storage unit of the set of storage units, cause the first storage unit to;

receive the first check request message;

determine a first group of slice information in response to the first check request message;

send a first check response message to the computing device, wherein the first check response message includes the first group of slice information; and

a third memory element that stores operational instructions that, when executed by the computing device, cause the computing device to;

interpret the first check response message in light of the first group of slice names to identify one or more encoded data slices of the plurality of sets of encoded data slices in need of rebuilding.

8. The computer readable memory of claim 7 further comprises:

a fourth memory element that stores operational instructions that, when executed by the computing device, cause the computing device to;

generate the first check request message to include a header section and a payload section;

the payload section includes;

a plurality of slice name fields for containing the first group of slice names; and

a common transaction number field for containing a common transaction number corresponding to a check request operation; and

the protocol header includes one or more of;

a payload length field for containing a payload length that represents a length of the payload section;

an operation code field for containing an indicate the check request operation;

a protocol class field for containing a protocol class for the check request operation; and

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

9. The computer readable memory of claim 7 further comprises:

a fifth memory element that stores operational instructions that, when executed by the first storage unit, cause the first storage unit to;

generate the first check response message to include a header section and a payload section;

the payload section includes a plurality of slice information sections corresponding to the first group of slice information, wherein a first slice information section of the plurality of slice information sections corresponds to a first slice name of the first group of slice names and includes one or more of;

a slice revision count;

a slice revision numbering; and

a slice length; and

the protocol header includes one or more of;

a payload length field for containing a payload length that represents a length of the payload section;

an operation code field for containing an indicate the check request operation;

a protocol class field for containing a protocol class for the check request operation; and

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

10. The computer readable memory of claim 7, wherein the third memory element stores further operational instructions that, when executed by the computing device, cause the computing device to interpret the first check response message by:

for a first slice name of the first group of slice names, compare a slice revision number of a first slice information section of a plurality of slice information sections of the first check response message with a known revision level;

when the comparing of the slice revision number compares unfavorably with the known revision level, identify an encoded data slice associated with the first slice name is in need of rebuilding.

11. The computer readable memory of claim 7, wherein the third memory element stores further operational instructions that, when executed by the computing device, cause the computing device to interpret the first check response message by:

for a first slice name of the first group of slice names, compare a slice length of a first slice information section of a plurality of slice information sections of the first check response message with a known slice length; and

when the comparing of the slice length compares unfavorably with the known slice length, identify an encoded data slice associated with the first slice name is in need of rebuilding.

12. The computer readable memory of claim 7 further comprises:

a sixth memory element that stores operational instructions that, when executed by a second storage unit of the set of storage units, cause the second storage unit to;

receive a second check request message;

determine a second group of slice information in response to the second check request message;

send a second check response message to the computing device, wherein the second check response message includes the second group of slice information; and

a seventh memory element that stores operational instructions that, when executed by the computing device, cause the computing device to;

interpret the second check response message in light of the second group of slice names to identify one or more other encoded data slices of the plurality of sets of encoded data slices in need of rebuilding.