IP Library Granted Patent US 12,164,379
Granted Patent B2
US 12,164,379 · App. 17/931,159 · Granted Dec 10, 2024

Recovering a data segment using locally decodable code segments

Inventors: Thomas D. Cocagne (Elk Grove Village, IL); Jason K. Resch (Warwick, RI); Ilya Volvovski (Chicago, IL)
Assignee: Pure Storage, Inc.
G06F11/1092G06F3/0619G06F3/0659G06F3/0689G06F11/0772G06F11/3034
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,164,379
App. No.
17/931,159
Granted
Dec 10, 2024
Kind
B2
Abstract

A storage network operates by: storing at least one data object in the storage network as encoded data slices that are dispersed error encoded, the encoded data slices including locally decodable code segments; detecting at least one storage error associated with storage of at least one of the encoded data slices in the storage network; and recovering and at least one of the encoded data slices utilizing the locally decodable code segments.

Claims (36)

1. A method for execution by a storage network that includes a processor, the method comprising:

storing at least one data object in the storage network as encoded data slices that are dispersed error encoded, the encoded data slices including locally decodable code segments;

detecting at least one storage error associated with storage of at least one of the encoded data slices in the storage network; and

recovering and at least one of the encoded data slices utilizing the locally decodable code segments.

2. The method of claim 1 , further comprising:

rebuilding the at least one of the encoded data slices associated with the storage error utilizing the at least one data object recovered based on the locally decodable code segments.

3. The method of claim 2 , wherein the rebuilding includes re-encoding the at least one data object via dispersed error encoding.

4. The method of claim 2 , further comprising:

issuing a rebuilding request to a rebuilding module.

5. The method of claim 4 , wherein issuing the rebuilding request includes:

identifying a storage unit of the storage network associated with the storage error.

6. The method of claim 5 , wherein issuing the rebuilding request further includes:

sending the rebuilding request to the rebuilding module that is associated with the storage unit.

7. The method of claim 1 , wherein the encoded data slices are stored in a set of storage units of the storage network.

8. The method of claim 1 , wherein a read threshold number of the encoded data slices are required to decode the at least one data object.

9. The method of claim 1 , wherein the at least one storage error is determined to exist in response to detecting that less than a write threshold number of encoded data slices are available.

10. The method of claim 1 , wherein the at least one storage error is determined to exist in response to detecting a device failure or in response to detecting that a storage network storage utilization level is greater than a maximum storage utilization threshold level.

11. A processing system of a storage network comprises:

at least one processor;

a memory that stores operational instructions, that when executed by the at least one processor cause the processing system to perform operations that include:

storing at least one data object in the storage network as encoded data slices that are dispersed error encoded, the encoded data slices including locally decodable code segments;

detecting at least one storage error associated with storage of at least one of the encoded data slices in the storage network; and

recovering and at least one of the encoded data slices utilizing the locally decodable code segments.

12. The processing system of claim 11 , wherein the operations further include:

rebuilding the at least one of the encoded data slices associated with the storage error utilizing the at least one data object recovered based on the locally decodable code segments.

13. The processing system of claim 12 , wherein the rebuilding includes re-encoding the at least one data object via dispersed error encoding.

14. The processing system of claim 12 , wherein the operations further include:

issuing a rebuilding request to a rebuilding module.

15. The processing system of claim 14 , wherein issuing the rebuilding request includes:

identifying a storage unit of the storage network associated with the storage error.

16. The processing system of claim 15 , wherein issuing the rebuilding request further includes:

sending the rebuilding request to the rebuilding module that is associated with the storage unit.

17. The processing system of claim 11 , wherein the encoded data slices are stored in a set of storage units of the storage network.

18. The processing system of claim 11 , wherein a read threshold number of the encoded data slices are required to decode the at least one data object.

19. The processing system of claim 11 , wherein the at least one storage error is determined to exist in response to detecting that less than a write threshold number of encoded data slices are available.

20. The processing system of claim 11 , wherein the at least one storage error is determined to exist in response to detecting a device failure or in response to detecting that a storage network storage utilization level is greater than a maximum storage utilization threshold level.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 13, 2022
From: COCAGNE, THOMAS D.; RESCH, JASON K.; VOLVOVSKI, ILYA
To: PURE STORAGE, INC.
Reel/Frame 061071/0163 →
Continuity (28)
Continuation 16951253 · Nov 18, 2020
Continuation In Part 16920948 · Jul 6, 2020
Continuation In Part 16390530 · Apr 22, 2019
Continuation 16188942 · Nov 13, 2018
Continuation In Part 15845126 · Dec 18, 2017
Continuation In Part 15843143 · Dec 15, 2017
Continuation 15347132 · Nov 9, 2016
Continuation In Part 15006845 · Jan 26, 2016
Continuation 14447890 · Jul 31, 2014
Continuation In Part 13866457 · Apr 19, 2013
Continuation 13154725 · Jun 7, 2011
Continuation 12749592 · Mar 30, 2010
Continuation In Part 12218594 · Jul 16, 2008
Continuation In Part 12218200 · Jul 14, 2008
Continuation In Part 12080042 · Mar 31, 2008
Continuation In Part 11973542 · Oct 9, 2007
Continuation In Part 11973613 · Oct 9, 2007
Continuation In Part 11973621 · Oct 9, 2007
Continuation In Part 11973622 · Oct 9, 2007
Continuation In Part 11403684 · Apr 13, 2006
Continuation In Part 11403391 · Apr 13, 2006
Continuation In Part 11404071 · Apr 13, 2006
Continuation In Part 11241555 · Sep 30, 2005
Provisional Application 62141034 · Mar 31, 2015
Provisional Application 61655753 · Jun 5, 2012
Provisional Application 61357430 · Jun 22, 2010
Provisional Application 61237624 · Aug 27, 2009
Related Publication 20230081087A1 · Mar 16, 2023