Patent Application
20130103902
The present invention relates to the field of communications technologies, and in particular, to a method and an apparatus for implementing protection of a redundant array of independent disks (RAID) in a file system.
A file system is a file management system for managing and storing file information. The file system is capable of reading and writing data from and into a RAID module by using a virtual block device of a logic unit (LUN). The RAID module may include one or more data storage blocks (marked as RAIDn). Each data storage block includes multiple hard disk drives. The data is stored in the hard disk drives, and carries additional redundant information.
At the time of reading and writing data, upon receiving a data read/write request, that is, an input/output (I/O) request, the file system resolves the data read/write request, and then stores the request into a corresponding location in the LUN virtual block device; the RAID module reads the data read/write request in the LUN virtual block device, resolves the data read/write request, and then processes the requested data by using a RAID data protection method, for example, stores the data into the hard disk drive, or reads the data from the hard disk drive. The RAID data protection method is the method used when the RAID module reads or writes data, and comes in many types, that is, a data protection method of RAIDn (n=1, 2 . . . ).
In the prior art, when processing file data, the RAID module reads/writes data in the hard disk drive randomly, and therefore, the reliability of data storage is low.
Embodiments of the present invention provide a method and an apparatus for implementing protection of RAID in a file system, thereby improving reliability of data storage and simplifying the file processing process.
An embodiment of the present invention provides a method for implementing protection of RAID in a file system, including:
receiving a file operation request, and determining the type of a file to be operated as requested by the file operation request, where the type of the file includes file metadata and/or file data;
selecting a corresponding file operation method according to the determined file type, where the file operation method is a RAID data protection method; and
performing file operations in a hard disk drive according to the selected file operation method.
An embodiment of the present invention provides an apparatus for implementing protection of RAID in a file system. The apparatus includes a type determining module and an operating module.
The type determining module is configured to receive a file operation request, and determine the type of a file to be operated as requested by the file operation request, where the type of the file includes file metadata and/or file data.
The operating module is configured to: select a corresponding file operation method according to the file type determined by the type determining module, where the file operation method is a RAID data protection method; and perform file operations in a hard disk drive according to the selected file operation method.
In this embodiment, after receiving the file operation request, the file system needs to determine the type of the file to be operated as requested by the file operation request, and perform file operations in the hard disk drive of the file system directly according to the file operation method corresponding to the determined file type, that is, a RAID data protection method. Therefore, file operations may be performed in a proper operation method according to each different file type, and data of an important file type is primarily protected. For example, important data may be written into each hard disk drive of the file system, thereby improving reliability of data storage.
Moreover, the method provided in the embodiments of the present invention avoids the following operations: The file system and the RAID module resolve the file operation request respectively, and then the RAID module performs file operations in the hard disk drive. Instead, the file system uses a RAID data protection method to access the system hard disk drive directly, thereby simplifying the file processing process and improving the system reliability.
To illustrate the technical solutions in the embodiments of the present invention or in the prior art more clearly, the following briefly describes the accompanying drawings required for describing the embodiments or the prior art. Apparently, the accompanying drawings in the following description merely show some embodiments of the present invention, and persons of ordinary skill in the art may derive other drawings from these drawings without creative efforts.
The following clearly and completely describes the technical solutions according to the embodiments of the present invention with reference to the accompanying drawings in the embodiments of the present invention. Apparently, the embodiments in the following description are merely a part rather than all of the embodiments of the present invention. All other embodiments obtained by persons of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the protection scope of the present invention.
An embodiment of the present invention provides a method for implementing protection of RAID in a file system. The file operation method in the embodiment of the present invention is a method performed by the file system. As shown in
101. Receive a file operation request, and determine the type of a file to be operated as requested by the file operation request, where the type of the file includes file metadata and/or file data.
Here, the file operation request may be a file read/write request, for example, an I/O request. The file metadata refers to attribute data in the file system, such as file format and file size; and the file data refers to content data of the file.
102. Select a corresponding file operation method according to the determined file type.
The file operation method refers to a method used for performing file operations, and may be any type of traditional protection method for RAID data, and different methods may be applied to different file types. For example, for data of an important file type, a multi-mirroring redundant algorithm of RAID 1 may be selected; for data of certain types, the protection method such as RAID1, RAID5, or RAID6 may be selected as required by the application scenario.
RAIDn (n=0, 1, 10, 5, 50, 6, 60) identifies the type of a data protection method. Each data protection method varies in type. For example, RAID1 is a multi-mirroring redundancy protection method for data, RAID5 stores data into data strips, any data fragment in each data strip may be calculated by using a check block and other data fragments in the data strip. The data fragments in a data strip are stored in different hard disk drives.
Here, the file system uses, according to the obtained file type, a different RAID data protection method to access one or more hard disk drives directly, and performs file operations, thereby improving reliability of data storage.
103. Perform file operations on hard disk drives of the file system according to the file operation method selected in step 102.
In this embodiment, the data in the file system is stored in multiple hard disk drives. Such hard disk drives will not constitute a redundant array of an independent disk.
The file system may perform file operations on these hard disk drives directly, for example, write data or read data into or from the hard disk drive directly. The hard disk drive here may be any non-volatile storage medium, such as a traditional hard disk drive, a solid-state hard disk drive, a magnetic tape, or a compact disc erasable.
For example, if the file operation method is a multi-mirroring redundancy protection method of RAID1, when writing a file, the file system needs to back up the file in multiplies copies, and store them in multiple hard disk drives respectively; if the file operation method is a RAID5 data protection method, when writing a file, the file system stores the file into the data strips of the hard disk drive according to the RAID5 data protection method.
In this embodiment, after receiving the file operation request, the file system needs to determine the type of the file to be operated as requested by the file operation request, and perform file operations in the hard disk drives of the file system directly according to the file operation method corresponding to the determined file type, that is, a RAID data protection method. Therefore, corresponding file operations may be performed by using a proper operation method according to each different file type, and data of an important file type is primarily protected. For example, important data may be written into each hard disk drive of the file system, thereby improving reliability of data storage.
Moreover, the method provided in the embodiments of the present invention avoids the following operations: The file system and the RAID module resolve the file operation request respectively, and then the RAID module performs file operations on hard disk drives. Instead, the file system uses a RAID data protection method to access the hard disk drives of the system directly, thereby simplifying the file processing process and improving the system reliability.
In a specific embodiment, if the file operation request received in step 101 is a file write request, and the determined file type includes file metadata, the file operation method selected in step 102 is a multi-mirroring redundant algorithm, and when performing file operations in the hard disk drive in step 103, the following method may be applied: backing up the file metadata into multiple copies and storing them in at least two hard disk drives according to the multi-mirroring redundant algorithm.
The multi-mirroring redundant algorithm is an algorithm of backing up metadata into multiple copies. Understandably, because file metadata is important and is the data that enables basic running of the file system, the file metadata needs to be written into multiple copies and respectively stored into multiple hard disk drives.
If the determined file type includes file data, the file operation performed on hard disk drives in step 103 may be implemented by using the following steps:
A1. Determine a data strip location of the file data in the file system according to an offset location of the file data in the file write request.
A data strip is a unit of storing data in the data protection method of certain RAID types. Each file write request includes the offset location of the file data relative to the initially stored data; according to the offset location, the file system may determine the data strip on which the file data is to be stored, determine the location of the file data in the data strip, and further determine the hard disk drive on which the file data is to be stored.
Supposing that the file data is stored according to a RAID5 data protection method, as shown in
P=D1 x or D2 x or D3 . . x or Dn (1)
In the formula above, D1, D2, D3 . . . Dn represent the data fragments in a data strip, P is a check block, and x or represents an Exclusive-OR operation.
Supposing that the offset location of the file data in the file write request is 11, and the location of the initially stored data is data fragment D1 in a hard disk drive 2, the file data is to be stored in the D12 location on data strip 1, and therefore it is determined that the file data is to be stored in a hard disk drive 4.
A2. Write the file data into a corresponding hard disk drive according to the determined location.
It is understandable that each hard disk drive has a single-disk file system for managing the fragment files in a single disk. At least two fragment files are created on the single-disk file system. When performing the write operation for a file in step 103, the file metadata and/or the file data may be distributed into these fragment files. In this way, the files corresponding to a file operation request can be distributed into the fragment files of a single-disk file system on at least two hard disk drives to form a RAID data protection relationship.
In another specific embodiment, if the file operation request received in step 101 is a file read request, and the determined file type includes file metadata, when performing file operations on hard disk drives in step 103, the following method may be applied: reading the file metadata from any hard disk drive that stores the file metadata.
When performing the write operation for the file metadata, the file metadata is backed up into multiple copies and stored onto at least two hard disk drives according to a multi-mirroring redundant algorithm. Therefore, the file metadata in the at least two hard disk drives makes up a RAID data protection method, and at the time of reading the file metadata, the file metadata may be read from any one of the at least two hard disk drives.
If the determined file type includes file data, the file operation performed on hard disk drives in step 103 may be implemented by using the following steps:
B1. Determine the data strip location of the file data in the file system according to the offset location of the file data in the file read request.
Similarly, each file read request includes the offset location of the file data relative to the initially stored data; according to the offset location, the file system may determine the data strip on which the file data is to be stored, determine the location of the file data in the data strip, and further determine a hard disk drive on which the file data is to be stored.
B2. Read file data from the corresponding hard disk drive in the file system.
If reading the file data fails, lost file data may be calculated according to other data fragments and the check block in the data strip that includes the file data.
Supposing that the file data is stored according to a RAID5 data protection method, as shown in
In other specific embodiments, the method in this embodiment further includes: detecting a state of the data strip in the file system, and reconstructing lost data when the data of a data strip is lost. The method of reconstructing the lost data is the same as the existing method for the RAID module to reconstruct data in the prior art, and is not repeated here any further.
An embodiment of the present invention provides an apparatus for implementing protection of RAID in a file system. The schematic structural diagram of the apparatus is shown in
The type determining module 10 is configured to receive a file operation request, and determine the type of a file to be operated as requested by the file operation request, where the type of the file includes file metadata and/or file data.
The operating module 20 is configured to: select a corresponding file operation method according to the file type determined by the type determining module 10, where the file operation method is a RAID data protection method; and perform corresponding file operations on hard disk drives according to the selected file operation method.
As shown in
In the apparatus for implementing protection of RAID in a file system in this embodiment, after receiving the file operation request, the type determining module 10 needs to determine the type of the file to be operated as requested by the file operation request, and the operating module 20 performs file operations in a hard disk drive 30 directly according to the file operation method corresponding to the determined file type, that is, a RAID data protection method. Therefore, when the file system performs file operations, corresponding file operations may be performed by using a proper operation method according to each different file type, and data of an important file type can be primarily protected. For example, important data may be written into each hard disk drive 30, thereby improving reliability of data storage.
Moreover, the method provided in the embodiments of the present invention avoids the following operations: The file system and the RAID module resolve the file operation request respectively, and then the RAID module performs file operations in the hard disk drive. Instead, the file system uses a RAID data protection method to access the system hard disk drive directly, thereby simplifying the file processing process and improving the system reliability.
As shown in
The metadata processing module 201 is configured to: if the file operation request is a file read/write request and the type determining module 10 determines that the file type includes file metadata, back up the file metadata into multiple copies and store the file metadata into at least two hard disk drives 30 according to a multi-mirroring redundant algorithm; or if the file operation request is a file read request, read file metadata from any hard disk drive 30 that stores the file metadata.
The file data processing module 202 is configured to: if the file operation request is a file read/write request and the type determining module 10 determines that the file type includes file data, select a RAID algorithm as a file operation method, where the selected RAID algorithm is used to calculate the lost fragment data by using the check block in the data strip; determine a data strip location of the file data in the file system according to an offset location of the file data in the file read/write request; and read/write file data in the corresponding hard disk drive 30 in the file system.
Further, the file data processing module 202 can be further configured to: when any file data is lost, calculate the lost file data according to other data fragments and the check block in the data strip that includes the file data.
The reconstructing module 40 is configured to detect a state of the data strip in the file system, and reconstruct lost data when the data of the data strip is lost.
The hard disk drive detecting module 50 is configured to detect the state of one or more hard disk drives 30 in the file system, and report the state of the hard disk drive to the reconstructing module 40 when the hard disk drive is faulty or a new hard disk drive is inserted.
Understandably, if the file operation request received by the type determining module 10 of the file system in this embodiment is a file read/write request, and the determined file type includes file metadata, the metadata processing module 201 performs corresponding operations for the metadata; if the determined file type includes file data, the file data processing module 202 performs corresponding operations for the file data. Moreover, the reconstructing module 40 detects the state of the data strip in the hard disk drive 30 in the file system, where the data strip stores data; when detecting that a data strip loses data, the reconstructing module reconstructs the lost data; the hard disk drive detecting module 50 detects the state of the hard disk drive 30 and reports the state of the hard disk drive to the reconstructing module 40, and the reconstructing module 40 reconstructs and/or copies back the files according to the state of the hard disk drive. For example, when a hard disk drive is faulty, the reconstructing module reconstructs the data on the faulty hard disk drive; when the hard disk drive recovers from the fault, the reconstructing module copies the data on the hot backup disk back to the recovered hard disk drive.
Persons of ordinary skill in the art should understand that all or part of the steps of the method in the embodiments of the present invention may be implemented by a program instructing relevant hardware. The program may be stored in computer readable storage media. The storage media may be a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.
Detailed above are a method and an apparatus for implementing protection of RAID in a file system according to the embodiments of the present invention. In this specification, specific examples are used for illustrating principles and implementation manners of the present invention. The foregoing descriptions of the embodiments are merely used to help understand the methods and core ideas of the present invention. Meanwhile, persons of ordinary skill in the art may make modifications to the specific implementation manners and application scopes according to the idea of the present invention. In conclusion, the content of the specification shall not be construed as a limitation to the present invention. It is apparent that those skilled in the art may make modifications and variations to the invention without departing from the spirit and scope of the invention. The invention is intended to cover the modifications and variations provided that they fall in the scope of protection defined by the following claims or their equivalents.
| Number | Date | Country | Kind |
|---|---|---|---|
| 201010619961.2 | Dec 2010 | CN | national |
This application is a continuation of International Patent Application No. PCT/CN2011/084984, filed Dec. 30, 2011, which claim claims priority to Chinese Patent Application No. 201010619961.2, filed on Dec. 31, 2010, both of which is hereby incorporated by reference in its entirety.
| Number | Date | Country | |
|---|---|---|---|
| Parent | PCT/CN2011/084984 | Dec 2011 | US |
| Child | 13718814 | US |
