US20180181467A1 - Hard disk array and method for reconstructing thereof - Google Patents

Hard disk array and method for reconstructing thereof Download PDF

Info

Publication number
US20180181467A1
US20180181467A1 US15/391,272 US201615391272A US2018181467A1 US 20180181467 A1 US20180181467 A1 US 20180181467A1 US 201615391272 A US201615391272 A US 201615391272A US 2018181467 A1 US2018181467 A1 US 2018181467A1
Authority
US
United States
Prior art keywords
hard disk
data
sector
hard
access record
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US15/391,272
Other languages
English (en)
Inventor
Wei-Ru LI
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Industrial Technology Research Institute ITRI
Original Assignee
Industrial Technology Research Institute ITRI
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Industrial Technology Research Institute ITRI filed Critical Industrial Technology Research Institute ITRI
Assigned to INDUSTRIAL TECHNOLOGY RESEARCH INSTITUTE reassignment INDUSTRIAL TECHNOLOGY RESEARCH INSTITUTE ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: LI, WEI-RU
Publication of US20180181467A1 publication Critical patent/US20180181467A1/en
Priority to US16/529,595 priority Critical patent/US10831601B2/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/08—Error detection or correction by redundancy in data representation, e.g. by using checking codes
    • G06F11/10—Adding special bits or symbols to the coded information, e.g. parity check, casting out 9's or 11's
    • G06F11/1076—Parity data used in redundant arrays of independent storages, e.g. in RAID systems
    • G06F11/1088—Reconstruction on already foreseen single or plurality of spare disks
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
    • G06F3/0614—Improving the reliability of storage systems
    • G06F3/0619—Improving the reliability of storage systems in relation to data integrity, e.g. data losses, bit errors
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14—Error detection or correction of the data by redundancy in operation
    • G06F11/1402—Saving, restoring, recovering or retrying
    • G06F11/1446—Point-in-time backing up or restoration of persistent data
    • G06F11/1448—Management of the data involved in backup or backup restore
    • G06F11/1451—Management of the data involved in backup or backup restore by selection of backup contents
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
    • G06F3/0646—Horizontal data movement in storage systems, i.e. moving data in between storage devices or systems
    • G06F3/065—Replication mechanisms
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
    • G06F3/0655—Vertical data movement, i.e. input-output transfer; data movement between one or more hosts and one or more storage devices
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
    • G06F3/0671—In-line storage system
    • G06F3/0683—Plurality of storage devices
    • G06F3/0689—Disk arrays, e.g. RAID, JBOD
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/16—Error detection or correction of the data by redundancy in hardware
    • G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
    • G06F11/2053—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where persistent mass storage functionality or persistent mass storage control functionality is redundant
    • G06F11/2056—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where persistent mass storage functionality or persistent mass storage control functionality is redundant by mirroring
    • G06F11/2058—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where persistent mass storage functionality or persistent mass storage control functionality is redundant by mirroring using more than 2 mirrored copies
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/16—Error detection or correction of the data by redundancy in hardware
    • G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
    • G06F11/2053—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where persistent mass storage functionality or persistent mass storage control functionality is redundant
    • G06F11/2056—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where persistent mass storage functionality or persistent mass storage control functionality is redundant by mirroring
    • G06F11/2084—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where persistent mass storage functionality or persistent mass storage control functionality is redundant by mirroring on the same storage unit
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
    • G06F2201/835—Timestamp
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
    • G06F2201/84—Using snapshots, i.e. a logical point-in-time copy of the data

Definitions

  • the disclosure relates to a hard disk array and a method for reconstructing thereof.
  • RAID redundant array of independent disks
  • multiple hard disks are combined to become a logical block.
  • the entire hard disk array would be treated a hard disk with great capacity, which implies augmenting the equivalent disk capacity connected to a channel.
  • the hard disk array can be categorized into many types, and each type has its own theoretical pros and cons. Different types of hard disk array balance between increasing the authenticity of data and increasing the memory to increase read-write efficiency by different measurements.
  • hard disk array By different types of hard disk array, certain types of hard disk array may be able to handle the situation when one single hard disk breaks down. However, due to the structure of hard disk array and the allocation of data, the hard disk array fails when multiple hard disks among the hard disks fail. If users have already back their data up and try to restore the hard disk array, at the time when renewing the broken hard disk with a new hard disk, the data in the unspoiled hard disk should be renewed as well. In such progress, lots of time is consumed for re-writing data that is correct originally. The progress, in which plenty of time and energy are taken up, is also inefficient.
  • a method for reconstructing a hard disk array comprises determining at least one to-be-fixed hard disks among a plurality of hard disks of the hard disk array; and writing into the at least one to-be-fixed hard disks a data of the at least one to-be-fixed hard disks according to a mapping table and an information of the at least one to-be-fixed hard disks, the data corresponding to a backup data of the plurality of hard disks.
  • a hard disk array comprises: a first hard disk; a second hard disk; a third hard disk; and a controller, electrically connected to the first hard disk, the second hard disk and the third hard disk, and configured to determine at least one to-be-fixed hard disks among the first hard disk, the second hard disk and the third hard disk, and to write into the at least one to-be-fixed hard disks a data of the at least one to-be-fixed hard disks according to a mapping table and an information of the at least one to-be-fixed hard disks, the data corresponding to a backup data of the plurality of hard disks.
  • FIG. 1 is a functional block diagram of the hard disk array according to an embodiment of the present disclosure
  • FIG. 2 is a functional block diagram of the distributed storage system according to an embodiment of the present disclosure
  • FIG. 3 is a functional block diagram of the backup hard disk array according to an embodiment of the present disclosure.
  • FIG. 4A is a schematic view illustrating the logical block of the hard disk array according to an embodiment of the present disclosure when running normally;
  • FIG. 4B is a schematic view illustrating the physical block of the hard disk array according to an embodiment of the present disclosure when running normally;
  • FIG. 5A is a schematic view illustrating the logical block of the hard disk array according to an embodiment of the present disclosure when multiple hard disks break down;
  • FIG. 5B is a schematic view illustrating the physical block of the hard disk array according to an embodiment of the present disclosure when multiple hard disks break down;
  • FIG. 6A is a schematic view illustrating the logical block of the hard disk array according to an embodiment of the present disclosure after broken hard disk is replaced;
  • FIG. 6B is a schematic view illustrating the physical block of the hard disk array according to an embodiment of the present disclosure after broken hard disk is replaced;
  • FIG. 7A is a schematic view illustrating the logical block of the hard disk array according to an embodiment of the present disclosure after one of the sectors is reconstructed;
  • FIG. 7B is a schematic view illustrating the physical block of the hard disk array according to an embodiment of the present disclosure after one of the sectors is reconstructed;
  • FIG. 8A is a schematic view illustrating the logical block of the hard disk array according to an embodiment of the present disclosure after another one of the sectors is reconstructed;
  • FIG. 8B is a schematic view illustrating the physical block of the hard disk array according to an embodiment of the present disclosure after another one of the sectors is reconstructed;
  • FIG. 9A is a schematic view illustrating the logical block of the hard disk array according to an embodiment of the present disclosure after one another of the sectors is reconstructed;
  • FIG. 9B is a schematic view illustrating the physical block of the hard disk array according to an embodiment of the present disclosure after one another of the sectors is reconstructed;
  • FIG. 10A is a schematic view illustrating the logical block of the hard disk array according to an embodiment of the present disclosure after yet another one of the sectors is reconstructed;
  • FIG. 10B is a schematic view illustrating the physical block of the hard disk array according to an embodiment of the present disclosure after yet another one of the sectors is reconstructed;
  • FIG. 11A is a schematic view illustrating the logical block of the hard disk array according to an embodiment of the present disclosure after multiple of the sectors is reconstructed;
  • FIG. 11B is a schematic view illustrating the physical block of the hard disk array according to an embodiment of the present disclosure after multiple of the sectors is reconstructed;
  • FIG. 12A is a schematic view illustrating the logical block of the hard disk array according to an embodiment of the present disclosure after one after another one of the sectors is reconstructed;
  • FIG. 12B is a schematic view illustrating the physical block of the hard disk array according to an embodiment of the present disclosure after one after another one of the sectors is reconstructed;
  • FIG. 13 is a flowchart illustrating the method for reconstructing hard disk array according to an embodiment of the present disclosure
  • FIG. 14A is a schematic view illustrating the logical block of the hard disk array according to another embodiment of the present disclosure when running normally;
  • FIG. 14B is a schematic view illustrating the physical block of the hard disk array according to another embodiment of the present disclosure when running normally;
  • FIG. 15A is a schematic view illustrating the logical block of the hard disk array according to another embodiment of the present disclosure when multiple hard disks break down;
  • FIG. 15B is a schematic view illustrating the physical block of the hard disk array according to another embodiment of the present disclosure when multiple hard disks break down;
  • FIG. 16A is a schematic view illustrating the logical block of the hard disk array according to another embodiment of the present disclosure after broken hard disk is replaced;
  • FIG. 16B is a schematic view illustrating the physical block of the hard disk array according to another embodiment of the present disclosure after broken hard disk is replaced;
  • FIG. 17A is a schematic view illustrating the logical block of the hard disk array according to another embodiment of the present disclosure after one of the sectors is reconstructed;
  • FIG. 17B is a schematic view illustrating the physical block of the hard disk array according to another embodiment of the present disclosure after one of the sectors is reconstructed;
  • FIG. 18A is a schematic view illustrating the logical block of the hard disk array according to another embodiment of the present disclosure after another one of the sectors is reconstructed.
  • FIG. 18B is a schematic view illustrating the physical block of the hard disk array according to another embodiment of the present disclosure after another one of the sectors is reconstructed.
  • FIG. 1 is a functional block diagram of the hard disk array according to an embodiment of the present disclosure.
  • the hard disk array 10 comprises a first hard disk 110 , a second hard disk 130 , the third hard disk 150 , a fourth hard disk 170 and a controller 190 .
  • the controller 190 is electrically connected with the first hard disk 110 , the second hard disk 130 , the third hard disk 150 and the fourth hard disk 170 .
  • the number of hard disks the hard disk array 10 have could be N, where N is an integer no less than 3. In the present embodiment, N is 4; however, the number should not be limiting the scope of the present disclosure.
  • the controller 190 may be composed of, among one or more integrated circuit (IC), one or more micro control unit (MCU), one or more application-specific integrated circuit (ASIC), at least one among the group.
  • IC integrated circuit
  • MCU micro control unit
  • ASIC application-specific integrated circuit
  • FIG. 2 is a functional block diagram of the distributed storage system according to an embodiment of the present disclosure.
  • FIG. 2 depicts a distributed storage system 1 .
  • the distributed storage system 1 comprises a hard disk array 10 , a backup hard disk array 30 and a distributed controller 20 .
  • the distributed controller 20 electrically connects with the hard disk array 10 and the backup hard disk array 30 .
  • the distributed controller 20 is configured to control the data transmission of the hard disk array 10 and the backup hard disk array 30 .
  • the hard disk array and the backup hard disk array share the same functions, and are a backup for each other.
  • the number for the hard disk array could be more than two.
  • the distributed controller 20 copies the data, and stores the data respectively in the hard disk array 10 and the backup hard disk array 30 .
  • FIG. 3 is a functional block diagram of the backup hard disk array according to an embodiment of the present disclosure.
  • the backup hard disk array 30 comprises a first backup hard disk 310 , a second backup hard disk 330 , a third backup hard disk 350 , a fourth backup hard disk 370 and a controller 390 .
  • the controller 390 electrically connects with the first backup hard disk 310 , the second backup hard disk 330 , the third backup hard disk 350 and the fourth backup hard disk 370 .
  • the backup hard disk array 30 and the hard disk array 10 have a similar architecture.
  • the first backup hard disk 310 is configured to store the backup data of the first hard disk 110
  • the second backup hard disk 330 is configured to store the backup data of the second hard disk 130
  • the third backup hard disk 350 is configured to store the backup data of the third hard disk 150
  • the fourth backup hard disk 370 is configured to store the backup data of the fourth hard disk 170 .
  • the above description is an exemplary; however, the backup data of each hard disk need not to be corresponded one by one to the backup hard disks in real practice.
  • the backup hard disk array 30 has N backup hard disks, where N is an integer no less than 3.
  • N is an integer no less than 3.
  • the present embodiment take N to be 4 as an exemplary, but the number of 4 should not be limiting the scope of the present disclosure.
  • the controller 190 is configured to monitor the status of the first hard disk 110 of the hard disk array 10 , the second hard disk 130 of the hard disk array 10 , the third hard disk 150 of the hard disk array 10 and the fourth hard disk 170 of the hard disk array 10 . After the controller determines there are at least one to-be-fixed hard disks among the first hard disk 110 , the second hard disk 130 , the third hard disk 150 and the fourth hard disk 170 , the controller 190 may retrieve the backup data from the backup hard disk array 30 by the previously-described architecture. The controller 190 may write into the at least one to-be-fixed hard disks into a data among a backup data and corresponding the at least one to-be-fixed hard disks according to a mapping table.
  • the mapping table may be, such as a corresponding model between the logical block of the hard disk array and the practically physical block.
  • the detail description about the mapping table would be omitted because it may be understood by a person with ordinary skill in the art after referring to the specification of the present disclosure.
  • the following description would delineate the modification of data in the sectors of the first hard disk 110 , the second hard disk 130 , the third hard disk 150 and the fourth hard disk 170 , when the first hard disk 110 and the second hard disk 130 failed.
  • FIG. 4A is a schematic view illustrating the logical block of the hard disk array according to an embodiment of the present disclosure when running normally
  • FIG. 4B is a schematic view illustrating the physical block of the hard disk array according to an embodiment of the present disclosure when running normally.
  • each sector is arranged in order as sector a 1 , sector a 2 , sector a 3 , sector b 1 , sector b 2 . . . to sector d 1 , sector d 2 and sector d 3 . That is to say, the data that is written into the hard disk would be arranged in the sectors by the above logical sequence.
  • FIG. 4A is a schematic view illustrating the logical block of the hard disk array according to an embodiment of the present disclosure when running normally
  • FIG. 4B is a schematic view illustrating the physical block of the hard disk array according to an embodiment of the present disclosure when running normally.
  • each sector is arranged in order as sector a 1 , sector a 2 , sector a 3 , sector b 1 ,
  • the physical blocks of the first hard disk 110 comprise sectors a 1 , b 1 , c 1 , Pb; the physical blocks of the second hard disk 130 comprise sectors a 2 , b 2 , Pc, d 1 ; the physical blocks of the third hard disk 150 comprise sectors a 3 , Pb, c 2 , d 2 ; and the physical blocks of the fourth hard disk 170 comprise Pa, b 3 , c 3 , d 3 .
  • the error correction codes are stored in sectors Pa, Pb, Pc, Pd.
  • the error correction code in sector Pa is generated according to values of sector a 1 , sector a 2 and sector a 3 ;
  • the error correction code in sector Pb is generated according to values of sectors b 1 , sector b 2 and sector b 3 ;
  • the error correction code in sector Pc is generated according to values of sectors c 1 , sector c 2 and sector c 3 ;
  • the error correction code in sector Pd is generated according to values of sectors d 1 , sector d 2 and sector d 3 .
  • the error correction codes are generated by, but not limited to, parity bit.
  • the error correction code in sector Pa is generated according to values of sector a 1 , sector a 2 and sector a 3 .
  • the corresponding data of sector a 1 , sector a 2 and sector a 3 are written into the hard disk array 10 , it is practically to write the corresponding data of sector a 1 , sector a 2 , sector a 3 and sector Pa into the first hard disk 110 , the second hard disk 130 the third hard disk 150 and the fourth hard disk 170 respectively.
  • FIG. 5A is a schematic view illustrating the logical block of the hard disk array according to an embodiment of the present disclosure when multiple hard disks break down
  • FIG. 5B is a schematic view illustrating the physical block of the hard disk array according to an embodiment of the present disclosure when multiple hard disks break down
  • FIG. 6A is a schematic view illustrating the logical block of the hard disk array according to an embodiment of the present disclosure after broken hard disk is replaced
  • FIG. 6B is a schematic view illustrating the physical block of the hard disk array according to an embodiment of the present disclosure after broken hard disk is replaced. As shown from FIG.
  • the first hard disk 110 and the second hard disk 130 are replaced because of damage.
  • the original sectors a 1 , b 1 , c 1 , Pd, a 2 , b 2 , Pc, d 1 are replaced by new sectors, so that the new sectors in FIG. 6A and FIG. 6B are not labeled with element number.
  • FIG. 7A is a schematic view illustrating the logical block of the hard disk array according to an embodiment of the present disclosure after one of the sectors is reconstructed
  • FIG. 7B is a schematic view illustrating the physical block of the hard disk array according to an embodiment of the present disclosure after one of the sectors is reconstructed.
  • sector a 1 has been reconstructed.
  • the controller 190 obtains the backup data of sector al from the first backup hard disk 310 , and writes the backup data into the corresponding sector of the first hard disk 110 according to the mapping table.
  • FIG. 8A is a schematic view illustrating the logical block of the hard disk array according to an embodiment of the present disclosure after another one of the sectors is reconstructed
  • FIG. 8B is a schematic view illustrating the physical block of the hard disk array according to an embodiment of the present disclosure after another one of the sectors is reconstructed.
  • the controller 190 reconstructs sector a 1 according to the data of sector a 1 , the data of sector a 3 and the error correction code of Pa.
  • FIG. 9A is a schematic view illustrating the logical block of the hard disk array according to an embodiment of the present disclosure after one another of the sectors is reconstructed
  • FIG. 9B is a schematic view illustrating the physical block of the hard disk array according to an embodiment of the present disclosure after one another of the sectors is reconstructed.
  • the controller 190 obtains the data of sector c 1 , and reconstructs sector c 1 in the corresponding sector of the first hard disk 110 according to the mapping table.
  • FIG. 10A is a schematic view illustrating the logical block of the hard disk array according to an embodiment of the present disclosure after yet another one of the sectors is reconstructed
  • FIG. 10B is a schematic view illustrating the physical block of the hard disk array according to an embodiment of the present disclosure after yet another one of the sectors is reconstructed.
  • the first hard disk 110 , the third hard disk 150 and the fourth hard disk 170 respectively have sector c 1 , sector c 2 and sector c 3 .
  • the controller 190 re-calculates and then gives out an error correction code according to the relative data of sector c 1 , sector c 2 and sector c 3 , and reconstructs sector Pc in the second hard disk 130 according to the error correction code.
  • the controller 190 may comprise, such as an access record.
  • the access record associates with a timestamp of the first hard disk 110 , the second hard disk 130 and the third hard disk 150 .
  • the controller 190 according to the access record, selectively repairs the second hard disk 130 according to the first hard disk 110 and the third hard disk 150 .
  • the controller 190 compares the backup data with the access record, to determine whether a data time of the data among the backup data and corresponding to the second hard disk corresponds to the access record. When the data time corresponds to the access record, the controller 190 repairs the second hard disk 130 according to the first hard disk 110 and the second hard disk 130 .
  • the access record may be, such as at what timings the first hard disk 110 , the second hard disk 130 and the third hard disk 150 are written into data, or may be such as at what timings the data stored in the first hard disk 110 , the second hard disk 130 and the third hard disk 150 are read.
  • the timestamp may be, such as the timing the first hard disk 110 , the second hard disk 130 and the third hard disk 150 are accessed.
  • the access timing of each data or the access timing of each sector are recorded in the access record.
  • the access record may be, such as stored respectively in the first hard disk 110 , the second hard disk 130 and the third hard disk 150 , or may be, such as stored in the controller 190 , and there is no limitation of where to be stored.
  • the controller 190 when one of hard disks (the first hard disk 110 , the second hard disk 130 and the third hard disk 150 ) is accessed, the controller 190 generates the corresponding access timestamp according the current timing, and adjusts the access record accordingly.
  • the form of the access record and the access timestamp should not be limited.
  • FIG. 11A is a schematic view illustrating the logical block of the hard disk array according to an embodiment of the present disclosure after multiple of the sectors is reconstructed
  • FIG. 11B is a schematic view illustrating the physical block of the hard disk array according to an embodiment of the present disclosure after multiple of the sectors is reconstructed.
  • the controller 190 obtains the data of sector b 1 ′ and the data of sector b 2 ′ form the backup hard disk array 30 .
  • Sector b 1 ′ corresponds to the location of sector b 1
  • sector b 2 ′ corresponds to the location of sector b 2 .
  • the controller 190 determines that the data of sector b 1 ′ is not the same as the data of sector b 1 and the data of sector b 2 ′ is not the same as the data of sector b 2 . Thus, the controller 190 writes into the corresponding location of the first hard disk 110 the data of sector b 1 ′ directly according to the mapping table. The controller 190 also writes into the corresponding location of the second hard disk 130 the data of sector b 2 ′ directly according to the mapping table.
  • FIG. 12A is a schematic view illustrating the logical block of the hard disk array according to an embodiment of the present disclosure after one after another one of the sectors is reconstructed
  • FIG. 12B is a schematic view illustrating the physical block of the hard disk array according to an embodiment of the present disclosure after one after another one of the sectors is reconstructed.
  • the above embodiments may be adapted for RAID 5 architecture.
  • RAID 0 architecture when one hard disk failed, the controller 190 may reconstruct the sector of a broken hard disk according to the mapping table and the corresponding backup hard disk.
  • RAID 6 architecture An embodiment in which RAID 6 architecture is utilized would be given in the following.
  • FIG. 14A is a schematic view illustrating the logical block of the hard disk array according to another embodiment of the present disclosure when running normally
  • FIG. 14B is a schematic view illustrating the physical block of the hard disk array according to another embodiment of the present disclosure when running normally.
  • each sector is arranged in order as sector a 1 , sector a 2 , sector a 3 , sector b 1 , sector b 2 . . . to sector d 1 , sector d 2 and sector d 3 . That is to say, the data that is written into the hard disk would be arranged in the sectors by the above logical sequence.
  • the hard disk array comprises a first hard disk, a second hard disk, a third hard disk, a fourth hard disk and a fifty hard disk.
  • FIG. 14B shows the physical allocation of each of the sectors corresponding to the first hard disk, the second hard disk, the third hard disk, the fourth hard disk and the fourth hard disk.
  • the physical blocks of he first hard disk comprise sectors a 1 , b 1 , c 1 , Pd; the physical blocks of the second hard disk comprise sectors a 2 , b 2 , Pc, Qd; the physical blocks of the third hard disk comprise sectors a 3 , Pb, Qc, d 1 ; the physical blocks of the fourth hard disk comprise Pa, Qb, c 2 , d 2 ; and the physical blocks of the fifty hard disk comprise Qa, b 3 , c 3 , d 3 .
  • the error correction codes are stored in sectors Pa, Pb, Pc, Pd, Qa, Qb, Qc, Qd.
  • the error correction code in sector Pa is generated according to values of sector a 1 , sector a 2 and sector a 3 ; the error correction code in sector Qa is generated according to values of sector a 1 , sector a 2 and sector a 3 ; the error correction code in sector Pb is generated according to values of sectors b 1 , sector b 2 and sector b 3 ; the error correction code in sector Qb is generated according to values of sectors b 1 , sector b 2 and sector b 3 ; the error correction code in sector Pc is generated according to values of sectors c 1 , sector c 2 and sector c 3 ; the error correction code in sector Qc is generated according to values of sectors c 1 , sector c 2 and sector c 3 ; the error correction code in sector Pd is generated according to values of sectors d 1 , sector d 2 and sector d 3 ; and the error correction code in sector Qd is generated according to values of sectors d 1 , sector d 2 and sector d 3 .
  • the error correction code of Pa and the error correction code of Qa are generated by, but not limited to, different types of parity bit; the error correction code of Pb and the error correction code of Qb are generated by, but not limited to, different types of parity bit; the error correction code of Pc and the error correction code of Qc are generated by, but not limited to, different types of parity bit; and the error correction code of Pd and the error correction code of Qd are generated by, but not limited to, different types of parity bit.
  • the detail description of parity bit is omitted for precise purpose.
  • the error correction codes in sector Pa and sector Qa are generated according to values of sector a 1 , sector a 2 and sector a 3 .
  • FIG. 15A is a schematic view illustrating the logical block of the hard disk array according to another embodiment of the present disclosure when multiple hard disks break down
  • FIG. 15B is a schematic view illustrating the physical block of the hard disk array according to another embodiment of the present disclosure when multiple hard disks break down
  • FIG. 16A is a schematic view illustrating the logical block of the hard disk array according to another embodiment of the present disclosure after broken hard disk is replaced
  • FIG. 16B is a schematic view illustrating the physical block of the hard disk array according to another embodiment of the present disclosure after broken hard disk is replaced. As shown from FIG.
  • the first hard disk, the second hard disk and the third hard disk are replaced because of damage.
  • the original sectors a 1 , b 1 , c 1 , Pd, a 2 , b 2 , Pc, Qd, a 3 , Pb, Qc, d 1 are replaced by new sectors, so that the new sectors in FIG. 16A and FIG. 16B are not labeled with element number.
  • FIG. 17A is a schematic view illustrating the logical block of the hard disk array according to another embodiment of the present disclosure after one of the sectors is reconstructed
  • FIG. 17B is a schematic view illustrating the physical block of the hard disk array according to another embodiment of the present disclosure after one of the sectors is reconstructed. Due to the fact the description here is similar with the previous description, several steps are discloses briefly in the embodiment shown in FIG. 17A and FIG. 17B .
  • the controller reconstructs sector a 1 , sector b 1 , sector c 1 and sector d 1 according to the backup data and the mapping table.
  • the reconstruction order of reconstructing sector a 1 , sector b 1 , sector c 1 and sector d 1 is not limited.
  • FIG. 18A is a schematic view illustrating the logical block of the hard disk array according to another embodiment of the present disclosure after another one of the sectors is reconstructed
  • FIG. 18B is a schematic view illustrating the physical block of the hard disk array according to another embodiment of the present disclosure after another one of the sectors is reconstructed.
  • the controller restores the data of sector a 2 and the data of sector a 3 according to the data of sector a 1 , the error correction code of Pa and the error correction code of Qa.
  • the controller restores the data of sector b 2 according to the data of sector b 1 , the error correction code of sector Qb and the data of sector b 3 , the controller then reconstructs sector b 2 according to the restored data and the mapping table.
  • the controller further re-calculates and then gives out an error correction code according to the data of sector b 1 , the data of the reconstructed sector b 2 and the data of sector b 3 , and reconstructs sector Pb according to the re-calculated error correction code and the mapping table.
  • the controller After sector c 1 is reconstructed, the controller re-calculates and then gives out an error correction code according to the data of sector c 1 , the data of sector c 2 and the data of sector c 3 , and reconstructs sector Pc and sector Qc according to the re-calculated error correction code and the mapping table.
  • the controller After sector d 1 is reconstructed, the controller re-calculates and then gives out an error correction code according to the data of sector d 1 , the data of sector d 2 and the data of sector d 3 , and reconstructs sector Pd and sector Qd according to the re-calculated error correction code and the mapping table.
  • FIG. 13 is a flowchart illustrating the method for reconstructing hard disk array according to an embodiment of the present disclosure.
  • step S 101 determine at least one to-be-fixed hard disks among a plurality of hard disks of the hard disk array.
  • step S 103 write into the at least one to-be-fixed hard disks a data of the at least one to-be-fixed hard disks according to a mapping model, the data corresponding to a backup data of the plurality of hard disks.
  • the hard disk array is capable of error correcting.
  • the hard disk array comprises a first hard disk, a second hard disk and a third disk, and the at least one to-be-fixed hard disks comprise the first hard disk and the second hard disk.
  • the step of writing into the at least one to-be-fixed hard disks a data among a backup data and corresponding the at least one to-be-fixed hard disks
  • the data among the backup data and corresponds to the first hard disk is firstly written into the first hard disk.
  • the data among the backup data and corresponding to the second hard disk selectively repairs the second hard disk according to the first hard disk and the third hard disk.
  • the backup data and the access record are compared to determine whether a data time of the data among the backup data and corresponding to the second hard disk corresponds to a timestamp of the access record, and repairing the second hard disk according to the first hard disk and the second hard disk when the data time corresponds to the access record. For example, when the data time is later than the timestamp, that means the backup data is backed up after the last time the second hard disk is accessed, which also means the data among the backup data corresponding to the second hard disk is the latest.
  • the data of the second hard disk may be obtained by computing the data of the error correction code of the first hard disk and the third hard disk. Otherwise, it means no latest data of the second hard disk is among the backup data. Under this scenario, the reconstruction of the second hard disk may be completed when the backup data is written into, and the error correction codes of the first hard disk and/or the third hard disk should be modified accordingly.
  • the data among the backup data and corresponding to the second hard disk is written into the second hard disk when the data time does not correspond to the access record.
  • the error correction code stored in the first hard disk, the second hard disk or the third hard disk are modified according to the data of the first hard disk, the second hard disk and the third hard disk.
  • the first hard disk and the second hard disk each has a plurality of sectors
  • the backup data and the access record are compared to determine whether a data time of the data of a first sector of the plurality of sectors among the backup data and corresponding to the second hard disk corresponds to the access record, and repairing the second hard disk according to the first hard disk and the second hard disk when the data time corresponds to the access record.
  • the data among the backup data and corresponding to the first sector is written into the first sector when the data time does not correspond to the access record.
  • the error correction code stored in the first hard disk, the second hard disk or the third hard disk are modified according to the data of the first hard disk, the first sector and the third hard disk.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Human Computer Interaction (AREA)
  • Quality & Reliability (AREA)
  • Computer Security & Cryptography (AREA)
  • Signal Processing For Digital Recording And Reproducing (AREA)
US15/391,272 2016-12-22 2016-12-27 Hard disk array and method for reconstructing thereof Abandoned US20180181467A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US16/529,595 US10831601B2 (en) 2016-12-22 2019-08-01 Reconstruction hard disk array and reconstruction method for to-be-reconstructed hard disks therein including comparing backup data with an access timestamp of first, second and third hard disks

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201611196546.4 2016-12-22
CN201611196546.4A CN108228090B (zh) 2016-12-22 2016-12-22 硬盘阵列及其重建方法

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/529,595 Continuation US10831601B2 (en) 2016-12-22 2019-08-01 Reconstruction hard disk array and reconstruction method for to-be-reconstructed hard disks therein including comparing backup data with an access timestamp of first, second and third hard disks

Publications (1)

Publication Number Publication Date
US20180181467A1 true US20180181467A1 (en) 2018-06-28

Family

ID=62630296

Family Applications (2)

Application Number Title Priority Date Filing Date
US15/391,272 Abandoned US20180181467A1 (en) 2016-12-22 2016-12-27 Hard disk array and method for reconstructing thereof
US16/529,595 Active US10831601B2 (en) 2016-12-22 2019-08-01 Reconstruction hard disk array and reconstruction method for to-be-reconstructed hard disks therein including comparing backup data with an access timestamp of first, second and third hard disks

Family Applications After (1)

Application Number Title Priority Date Filing Date
US16/529,595 Active US10831601B2 (en) 2016-12-22 2019-08-01 Reconstruction hard disk array and reconstruction method for to-be-reconstructed hard disks therein including comparing backup data with an access timestamp of first, second and third hard disks

Country Status (3)

Country Link
US (2) US20180181467A1 (zh)
CN (1) CN108228090B (zh)
TW (1) TWI620116B (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111601062B (zh) * 2020-05-28 2022-08-23 广州通达汽车电气股份有限公司 用于车载监控录像的存储安全容错方法及系统
CN113556404A (zh) * 2021-08-03 2021-10-26 广东九博科技股份有限公司 一种设备内部单盘间的通信方法及系统

Family Cites Families (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6195761B1 (en) * 1997-12-31 2001-02-27 Emc Corporation Method and apparatus for identifying and repairing mismatched data
TW589526B (en) * 2002-11-22 2004-06-01 Wistron Corp Hard disk data control method
US7028139B1 (en) * 2003-07-03 2006-04-11 Veritas Operating Corporation Application-assisted recovery from data corruption in parity RAID storage using successive re-reads
US7266716B2 (en) * 2003-10-23 2007-09-04 Hewlett-Packard Development Company, L.P. Method and recovery of data using erasure coded data from stripe blocks
TWI283349B (en) * 2005-05-12 2007-07-01 Inventec Corp Data protection method
CN100530125C (zh) * 2007-08-24 2009-08-19 成都索贝数码科技股份有限公司 一种数据的安全存储方法
JP2009151393A (ja) * 2007-12-18 2009-07-09 Nec Corp 記憶媒体制御装置、記憶媒体管理システム、記憶媒体の制御方法、及び記憶媒体の制御プログラム
JP5391712B2 (ja) * 2009-02-05 2014-01-15 富士通株式会社 ディスクアレイ装置
US9015431B2 (en) * 2009-10-29 2015-04-21 Cleversafe, Inc. Distributed storage revision rollbacks
CN102063348B (zh) * 2010-12-27 2012-10-03 成都市华为赛门铁克科技有限公司 分区表信息备份方法和装置以及存储系统
US9128973B1 (en) * 2011-09-29 2015-09-08 Emc Corporation Method and system for tracking re-sizing and re-creation of volumes using modification time
US20130179726A1 (en) * 2012-01-08 2013-07-11 Synology Incorporated Automatic remapping in redundant array of independent disks and related raid
US9558072B1 (en) * 2013-09-27 2017-01-31 EMC IP Holding Company LLC Block-level incremental recovery of a storage volume
JP2015225603A (ja) * 2014-05-29 2015-12-14 富士通株式会社 ストレージ制御装置、ストレージ制御方法およびストレージ制御プログラム
US9703645B2 (en) * 2014-10-24 2017-07-11 Netapp, Inc. Data recovery technique for recovering data from an object storage service
US9489260B1 (en) * 2015-05-26 2016-11-08 Seagate Technology Llc Flexible super block sizing for failed sector recovery
CN108089991A (zh) * 2016-11-23 2018-05-29 广明光电股份有限公司 固态硬盘重建对照表的方法

Also Published As

Publication number Publication date
US20190354439A1 (en) 2019-11-21
US10831601B2 (en) 2020-11-10
TW201823967A (zh) 2018-07-01
CN108228090A (zh) 2018-06-29
CN108228090B (zh) 2021-02-26
TWI620116B (zh) 2018-04-01

Similar Documents

Publication Publication Date Title
US8484522B2 (en) Apparatus, system, and method for bad block remapping
US8589724B2 (en) Rapid rebuild of a data set
CN101916173B (zh) 一种基于raid的数据读写方法及其系统
JP4815825B2 (ja) ディスクアレイ装置及びその再構築方法
US7721143B2 (en) Method for reducing rebuild time on a RAID device
US8307159B2 (en) System and method for providing performance-enhanced rebuild of a solid-state drive (SSD) in a solid-state drive hard disk drive (SSD HDD) redundant array of inexpensive disks 1 (RAID 1) pair
US20150371684A1 (en) Ultra high capacity ssd
US7640452B2 (en) Method for reconstructing data in case of two disk drives of RAID failure and system therefor
US6751136B2 (en) Drive failure recovery via capacity reconfiguration
US8356292B2 (en) Method for updating control program of physical storage device in storage virtualization system and storage virtualization controller and system thereof
US11531590B2 (en) Method and system for host-assisted data recovery assurance for data center storage device architectures
US20070088990A1 (en) System and method for reduction of rebuild time in raid systems through implementation of striped hot spare drives
EP0936534A2 (en) Recording device
US7363532B2 (en) System and method for recovering from a drive failure in a storage array
CN104035830A (zh) 一种数据恢复方法和装置
US20090132890A1 (en) Anamorphic Codes
US20130166991A1 (en) Non-Volatile Semiconductor Memory Device Using Mats with Error Detection and Correction and Methods of Managing the Same
US10831601B2 (en) Reconstruction hard disk array and reconstruction method for to-be-reconstructed hard disks therein including comparing backup data with an access timestamp of first, second and third hard disks
CN109032513B (zh) 基于ssd和hdd的raid架构及其备份、重建方法
US20060259812A1 (en) Data protection method
US7730370B2 (en) Apparatus and method for disk read checking
US7343519B2 (en) Disk drive power cycle screening method and apparatus for data storage system
CN115565598B (zh) Raid阵列磁盘暂时失效的数据存储与修复方法及系统
JP2005107676A (ja) アレイコントローラ及びディスクアレイ再構築方法
CN113495676B (zh) 读写方法及存储器装置

Legal Events

Date Code Title Description
AS Assignment

Owner name: INDUSTRIAL TECHNOLOGY RESEARCH INSTITUTE, TAIWAN

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:LI, WEI-RU;REEL/FRAME:040774/0884

Effective date: 20161220

STPP Information on status: patent application and granting procedure in general

Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER

STPP Information on status: patent application and granting procedure in general

Free format text: NON FINAL ACTION MAILED

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION