Dispersed storage unit and method for configuration thereof

• US 9,043,574 B2
• Filed: 12/28/2012
• Issued: 05/26/2015
• Est. Priority Date: 03/12/2010
• Status: Expired due to Fees

• Current Assignee: Pure Storage, Inc.
• Original Assignee: Cleversafe Incorporated (International Business Machines Corporation)
• Inventors: Motwani, Manish, Leggette, Wesley
• Primary Examiner(s): BATAILLE, PIERRE MICHE
• Application Number:
  US13/730,223
• Publication Number:
  US 20130117529A1
• Time in Patent Office: 879 Days
• Field of Search: 711/154, 711/170, 711/173, 711/203, 711/114, 711/E12.002, 714/6.2
• US Class Current: 711/173
• CPC Class Codes: G06F 11/1076 Parity data used in redundant arrays of independent storages, e.g. in RAID systems
• CPC Class Codes: G06F 11/2094 Redundant storage or storage space G06F11/2056 takes precedence
• CPC Class Codes: G06F 12/0646 Configuration or reconfiguration
• CPC Class Codes: G06F 16/113 Details of archiving lifecycle management in storage systems G06F3/0649; backup systems G06F11/1446
• CPC Class Codes: G06F 16/122 using management policies backup systems G06F11/1446; file migration policies for HSM systems G06F16/185
• CPC Class Codes: G06F 16/125 characterised by the use of retention policies retention policies for HSM systems G06F16/185
• CPC Class Codes: G06F 16/162 Delete operations erasing in storage systems G06F3/0652
• CPC Class Codes: G06F 3/0629 Configuration or reconfiguration of storage systems
• CPC Class Codes: G06F 3/064 Management of blocks
• 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]

Abstract

A dispersed storage (DS) unit for use within a dispersed storage network is capable of self-configuring using registry information provided to the DS unit. The registry information includes a slice name assignment indicating a range of slice names corresponding to a plurality of potential data slices of potential data objects to be stored in the DS unit. Based on the registry information, the DS unit allocates a portion of physical memory to store the potential data slices.

Claims

1. A method for configuring a dispersed storage unit within a dispersed storage network, the dispersed storage unit including physical memory, comprising:

receiving, at the dispersed storage unit, registry information including a slice name assignment, the slice name assignment indicating a range of slice names corresponding a plurality of potential data slices, one of the potential data slices forming a portion of one of a plurality of potential data segments of one of a plurality of potential data objects that may be produced in the future; and

allocating a portion of the physical memory to store the potential data slices based on the registry information;

wherein;

a number of the potential data slices within one of the potential data segments indicates a number of pillars for one of the potential data objects; and

the range of slice names identifies the potential data slices associated with only one of the pillars.

2. The method of claim 1, further comprising:

receiving an actual data slice of an actual data segment of an actual data object to be stored within the dispersed storage unit, the slice name of the actual data slice including a virtual memory address of a virtual memory associated with the dispersed storage network; and

generating a mapping of the virtual memory address of the actual data slice to a physical memory address of the physical memory storing the actual data slice.

3. The method of claim 2, further comprising:

performing a comparison of the range of slice names of the registry information to a previous range of slice names of previous registry information stored within the dispersed storage unit; and

when the comparison indicates the range of slice names of the registry information is different than the previous range of slice names of the previous registry information, updating the table.

4. The method of claim 3, further comprising:

determining whether an existing range of slice names is to be deleted based on the comparison; and

when the existing range of slice names is to be deleted, deleting the existing range of slice names.

5. The method of claim 4, further comprising:

determining whether actual data slices corresponding to at least a portion of the existing range of slice names to be deleted are stored in the physical memory; and

deleting the actual data slices from the physical memory.

6. The method of claim 5, further comprising:

determining whether the actual data slices of the existing range of slice names are to be moved to an additional dispersed storage unit prior to deletion; and

transmitting the actual data slices of the existing range of slice names to the additional dispersed storage unit via an interface prior to deleting the actual data slices from the physical memory.

7. The method of claim 1, wherein the registry information further includes a rebuild assignment indicating a lost or corrupt data slice of an actual data object to be rebuilt from one or more related data slices stored in the physical memory or in other dispersed storage units.

8. A dispersed storage unit for use within a dispersed storage network, comprising:

a physical memory;

an interface; and

a processing module operable to;

receive, via the interface, registry information including a slice name assignment, the slice name assignment indicating a range of slice names corresponding to a plurality of potential data slices, one of the potential data slices forming a portion of one of a plurality of potential data segments of one of a plurality of potential data objects that may be produced in the future; and

allocate a portion of the physical memory to store the potential data slices based on the registry information;

wherein;

a number of the potential data slices within one of the potential data segments indicates a number of pillars for one of the potential data objects; and

the range of slice names identifies the potential data slices associated with only one of the pillars.

9. The dispersed storage unit of claim 8, wherein the processing module is further operable to:

receive, via the interface, an actual data slice of an actual data segment of an actual data object to be stored within the dispersed storage unit, the slice name of the actual data slice including a virtual memory address of a virtual memory associated with the dispersed storage network; and

generate a mapping of the virtual memory address of the actual data slice to a physical memory address of the physical memory storing the actual data slice.

10. The dispersed storage unit of claim 8, wherein the processing module is further operable to:

perform a comparison of the range of slice names of the registry information to a previous range of slice names of previous registry information stored within the dispersed storage unit; and

when the comparison indicates the range of slice names of the registry information is different than the previous range of slice names of the previous registry information, update a table.

11. The dispersed storage unit of claim 10, wherein the processing module is further operable to determine whether an existing range of slice names is to be deleted based on the comparison, and to delete the existing range of slice names.

12. The dispersed storage unit of claim 11, wherein the processing module is further operable to determine whether actual data slices corresponding to at least a portion of the existing range of slice names to be deleted are stored in the physical memory, and to delete the actual data slices from the physical memory.

13. The dispersed storage unit of claim 12, wherein the processing module is further operable to determine whether the actual data slices are to be moved to an additional dispersed storage unit prior to deletion, and to transmit the actual data slices to the additional dispersed storage unit via the interface prior to deleting the actual data slices from the physical memory.

14. The dispersed storage unit of claim 8, wherein the number of pillars per data segment is constant for a particular vault associated with at least one user of the dispersed storage network.

15. The dispersed storage unit of claim 14, wherein:

the dispersed storage network includes multiple vaults, each associated with at least one user,

the pillars within the vaults having respective pillar numbers, and

the slice name assignment includes ranges of slice names associated with the same pillar numbers for at least two of the vaults.

16. The dispersed storage unit of claim 8, wherein the physical memory includes two or more physical memory devices.

17. The dispersed storage unit of claim 8, wherein the registry information further includes a rebuild assignment indicating a lost or corrupt data slice of an actual data object to be rebuilt from one or more related data slices stored in the physical memory or in other dispersed storage units.

18. The dispersed storage unit of claim 8, wherein the processing module is further operable to transmit, via the interface, a query to the dispersed storage network requesting the registry information.

19. The dispersed storage unit of claim 8, wherein the processing module is further operable to:

determine an initial configuration of the dispersed storage unit;

acquire security credentials for the dispersed storage unit from the dispersed storage network via the interface;

determine whether software modules are needed; and

download the software modules from the dispersed storage network.