Storage media data structure system and method

• US 20050223156A1
• Filed: 04/02/2004
• Published: 10/06/2005
• Est. Priority Date: 04/02/2004
• Status: Active Grant

• Current Assignee: Seagate Technology LLC (Seagate Technology Holdings Plc)
• Original Assignee: Seagate Technology LLC (Seagate Technology Holdings Plc)
• Inventors: Roberson, Randy L., Lubbers, Clark E.
• Granted Patent: US 7,237,062 B2
• Time in Patent Office: Days
• US Class Current: 711/100
• 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/0638 Organizing or formatting or addressing of data
• CPC Class Codes: G06F 3/0683 Plurality of storage devices

Abstract

Disclosed is a data storage architecture employing a plurality of data grids each comprising an array of equal capacity data storage blocks organized into a plurality of rows and a plurality of columns such that each column corresponds to a storage domain in a data storage system and each row of the plurality of rows corresponds to a plurality of data storage blocks, one data storage block from each column of the plurality of columns at the same physical address, with the plurality of rows each having a plurality of contiguous data storage blocks in each domain. Capacity grids are produce by applying one of a plurality of sparing versions that designate at least one data storage block in each row of the grid is designated as spare, Defined within each capacity grid are one or more data storage units. Each data storage unit reflects a storage format, such as a RAID level, and defines data storage blocks, mirror data blocks, and parity data blocks depending upon storage the format and can provide fault tolerance in the event of a domain failure. User data is stored exclusively in a first portion of the grid and parity data, if any, is exclusively stored in a second portion of the grid, providing optimized performance. Data access employs metadata that may comprise grid and storage unit descriptors, data storage unit format, and a sparing table.

Claims

1. A method of storing data in a grid-based data storage system comprising:

defining an array of equal capacity data storage units, each defined in terms of a plurality of separate storage domains against a plurality of data storage blocks; and

allocating each of the data storage units for entirely storing either user data or fault tolerance data.

2. The method of claim 1 further comprising aligning a base address of each data storage unit allocated for storing user data with an address defined by a multiple of a size of the storage blocks.

3. The method of claim 1 further comprising defining a pointer that identifies a selected data storage unit.

4. The method of claim 1 wherein the fault tolerance data is characterized as either mirror data or parity data.

8. The method of claim 1 further comprising defining a sparing table that designates at least one data block in each row of said array as a spare data block.

9. The method of claim 8 further comprising defining said sparing table to contain a plurality of sparing versions that each specify a different storage domain as containing said at least one spare data block in each row.

13. The method of claim 1 further comprising creating a metadata entry that identifies each data storage unit and the array of a plurality of arrays in which said at least one data storage unit exists.

14. The method of claim 13 wherein said metadata entry further comprises an entry indicating a storage format of each data storage unit.

5. (canceled)

6. (canceled)

7. (canceled)

10. (canceled)

11. (canceled)

12. (canceled)

15. (canceled)

16. A grid-based data storage system comprising an array of equal capacity data storage units, each defined in terms of a plurality of separate storage domains against a plurality of data storage blocks, wherein each data storage unit is individually allocated for entirely storing either user data or fault tolerance data.

17. The data storage system of claim 16 further comprising a plurality of spare storage blocks that are allocatable for storing data in the respective data storage units.

27. The data storage system of claim 16 wherein the data storage blocks are of equal capacity.

28. The data storage system of claim 16 wherein within a particular row, a data storage block in a first domain has the same physical address as a data storage block in a second domain.

29. The data storage system of claim 16 wherein the array is adapted for storing data in the data storage blocks in a selected storage format by predetermined arrangements of user data, mirror data, and parity data associated with each of a plurality of selectable storage formats.

30. The data storage system of claim 29 wherein the predetermined arrangement defines at least one row in the array that contains no mirror or parity data in the data storage blocks.

31. The data storage system of claim 30 wherein the array is adapted for storing data in a RAID 5 or RAID 6 storage format.

32. The data storage system of claim 16 further comprising metadata defining a pointer for identifying a selected data storage unit.

33. The data storage system of claim 16 wherein a base address of each data storage unit allocated for storing user data is aligned with an address defined by a multiple of a size of the storage blocks.

34. The data storage system of claim 16 wherein the fault tolerance data comprises either mirror data or parity data.

18. A method of storing data in a grid-based data storage system comprising:

defining an array of equal capacity data storage units, each defined in terms of a plurality separate storage domains against a plurality of data storage blocks;

allocating each of the data storage units for entirely storing either user data or fault tolerance data in accordance with a selected first storage format; and

reallocating the data storage units for entirely storing either user data or fault tolerance data in accordance with a selected second storage format if the number of data storage units in the first storage format is less than or equal to the number of data storage units in the second storage format.

19. The method of claim 18 further comprising:

defining a second array of equal capacity data storage units, each defined in terms of a plurality of separate storage domains against a plurality of data storage blocks; and

allocating additional data storage units in the second array if the number of data storage units in the first storage format is greater than the number of data storage units in the second storage format.

20. The method of claim 18 comprising:

determining the data storage format of said array;

identifying an inaccessible storage domain;

accessing a sparing table that specifies at least one spare data block in each row of said array;

accessing metadata corresponding to said data storage format that specifies the location and content of each data block in said array; and

regenerating or copying data corresponding to each non-accessible data storage block to the respective spare data block.

21. A data structure having an array of equal capacity data storage units, each defined in terms of a plurality of separate storage domains against a plurality of data storage blocks, the data structure comprising a pointer that when multiplied by a storage capacity of said data storage blocks and by the number of rows of data storage units allocated for storing user data, and to which an offset, if any, is added, produces the base address in each storage domain at which said data storage grid begins.

22. (canceled)

23. (canceled)

24. (canceled)

25. A method of accessing data in a data storage system comprising:

defining an array of equal capacity data storage units, each defined in terms of a plurality of separate storage domains against a plurality of data storage blocks;

determining a domain and a physical address for at least one data storage block by applying an array pointer value to determine a base address of said array, applying a data storage unit pointer value to determine at least one domain to be accessed, and to determine a row such that the row number minus one is multiplied by a capacity of said storage blocks and added to a base address to produce a physical address; and

issuing an access command to said at least one domain that includes said physical address.

26. (canceled)