Distributed storage network for modification of a data object

• US 9,304,759 B2
• Filed: 07/07/2015
• Issued: 04/05/2016
• Est. Priority Date: 10/30/2009
• Status: Active Grant

• Current Assignee: Pure Storage, Inc.
• Original Assignee: Cleversafe Incorporated (International Business Machines Corporation)
• Inventors: Resch, Jason K.
• Primary Examiner(s): Merant, Guerrier
• Application Number:
  US14/792,846
• Publication Number:
  US 20150309786A1
• Time in Patent Office: 273 Days
• US Class Current: 1/1
• 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/1096 Parity calculation or recalculation after configuration or reconfiguration of the system
• CPC Class Codes: G06F 2211/1028 Distributed, i.e. distributed RAID systems with parity
• CPC Class Codes: G06F 3/0619 in relation to data integrity, e.g. data losses, bit errors
• CPC Class Codes: G06F 3/0665 at area level, e.g. provisioning of virtual or logical volumes
• CPC Class Codes: G06F 3/0689 Disk arrays, e.g. RAID, JBOD
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• 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/14 Multichannel or multilink protocols

Abstract

A method for updating software in storage units of a dispersed storage network includes determining a software updating sequence pattern, which insures that, for each set of encoded data slices, a decode threshold number of encoded data slices is accessible. The method includes taking a set of the storage units off-line for software updating in accordance with the software updating sequence pattern. The method includes, when the software has been successfully updated in the set of storage units, putting the set of storage units back on-line and taking another set of the storage units off-line in accordance with the software updating sequence pattern. The method includes, when the software has been successfully updated in the other set of storage units, putting the other set of storage units back on-line and taking yet another set of the storage units off-line for software updating in accordance with the software updating sequence pattern.

Claims

1. A method for updating software in storage units of a dispersed storage network (DSN), wherein the storage units stores pluralities of sets of encoded data slices, wherein a data object is dispersed storage error encoded to produce a plurality of sets of encoded data slices, the method is executed by a computing device and comprises:

determining a software updating sequence pattern for the storage units, wherein the software updating sequence pattern insures that, for each set of encoded data slices of the pluralities of sets of encoded data slices, a decode threshold number of encoded data slices is accessible, wherein the decode threshold number of encoded data slices is a minimum number of encoded data slices of the set of encoded data slices needed to recover a data segment of the data object;

taking a set of the storage units off-line for software updating in accordance with the software updating sequence pattern for updating software;

when the software has been successfully updated in the set of the storage units, putting the set of the storage units back on-line and taking another set of the storage units off-line for software updating in accordance with the software updating sequence pattern for updating the software; and

when the software has been successfully updated in the other set of the storage units, putting the other set of the storage units back on-line and taking yet another set of the storage units off-line for software updating in accordance with the software updating sequence pattern for updating the software.

2. The method of claim 1, wherein the set of the storage units includes one or more storage units.

3. The method of claim 1, wherein the determining the software updating sequence pattern comprises:

determining vaults supported by the storage units and corresponding dispersed storage error encoding parameters of the vaults;

for each vault, selecting an acceptable storage unit off-line rate to be in a range from one to a pillar width number minus the decode threshold number; and

establishing the set, the other set, and the yet another set of the storage units based on the supported vaults per storage unit and the acceptable storage unit off-line rate per vault.

4. The method of claim 1, wherein the software comprises one or more of:

a new application;

a new version of an existing application;

a new version of a portion of an existing application;

address information regarding new physical memory;

updated address information regarding existing physical memory;

operational information regarding a new processing module;

updated operational information regarding an existing processing module;

an updated interface protocol; and

a new interface protocol.

5. A non-transitory computer readable memory device comprises:

a first memory section that stores operational instructions that, when read by a computing device, causes the computing device to;

determine a software updating sequence pattern for updating software in storage units of a dispersed storage network (DSN), wherein the storage units stores a pluralities of sets of encoded data slices, wherein a data object is dispersed storage error encoded to produce a plurality of sets of encoded data slices, wherein the software updating sequence pattern insures that, for each set of encoded data slices of the pluralities of sets of encoded data slices, a decode threshold number of encoded data slices is accessible, wherein the decode threshold number of encoded data slices is a minimum number of encoded data slices of the set of encoded data slices needed to recover a data segment of the data object;

a second memory section that stores operational instructions that, when read by the computing device, causes the computing device to;

take a set of the storage units off-line for software updating in accordance with the software updating sequence pattern for updating software;

when the software has been successfully updated in the set of the storage units, put the set of the storage units back on-line and take another set of the storage units off-line for software updating in accordance with the software updating sequence pattern for updating the software; and

when the software has been successfully updated in the other set of the storage units, putt the other set of the storage units back on-line and take yet another set of the storage units off-line for software updating in accordance with the software updating sequence pattern for updating the software.

6. The non-transitory computer readable memory device of claim 5, wherein the set of the storage units includes one or more storage units.

7. The non-transitory computer readable memory device of claim 5, wherein the first memory section further stores operational instructions that, when read by the computing device, causes the computing device to determine the software updating sequence pattern by:

determining vaults supported by the storage units and corresponding dispersed storage error encoding parameters of the vaults;

for each vault, selecting an acceptable storage unit off-line rate to be in a range from one to a pillar width number minus the decode threshold number; and

establishing the set, the other set, and the yet another set of the storage units based on the supported vaults per storage unit and the acceptable storage unit off-line rate per vault.

8. The non-transitory computer readable memory device of claim 5, wherein the software comprises one or more of:

a new application;

a new version of an existing application;

a new version of a portion of an existing application;

address information regarding new physical memory;

updated address information regarding existing physical memory;

operational information regarding a new processing module;

updated operational information regarding an existing processing module;

an updated interface protocol; and

a new interface protocol.