Read-write request processing method and device, equipment, medium and product

Abstract

The invention relates to the technical field of I / O data processing, and discloses a read-write request processing method and device, equipment, a medium and a product, and the method comprises the steps: monitoring a currently reconstructed physical address range of a target hard disk; based on the currently reconstructed physical address range, distinguishing a reconstructed region and an unreconstructed region in the target hard disk; when the I / O request hits the reconstructed region, allowing the I / O request to directly read and write; and suspending the I / O request when the I / O request hits the uncompleted reconstruction area. According to the method, the number of write amplification I / O in the hard disk reconstruction process of the RAID system can be reduced, and the read-write I / O performance is improved.

Description

Technical Field

[0001] The present invention relates to the technical field of I / O data processing, and in particular to a read / write request processing method, device, equipment, medium and product. Background Art

[0002] RAID (Redundant Array of Independent Disks) technology is a method to improve data storage performance, reliability, and fault tolerance by distributing data across multiple hard disk drives. When a hard disk fails in a RAID1 / 5 / 6 disk group (DG) and there is a redundant disk, the data of the failed disk can be recovered through hard disk reconstruction. During the hard disk reconstruction process, business I / O transmission is allowed at the same time. When the business I / O hits the failed disk, the hard disk control system "believes" that the failed disk cannot be read or written, and business I / O transmission is achieved through write amplification. There are two typical scenarios for write amplification: write I / O and read I / O. When writing I / O, read the data of non-faulty disks, recalculate the check disk data and write it to the disk array together with the business I / O. When reading I / O, read the data of non-faulty disks and calculate the required I / O data. When rebuilding the hard disk, restore the data of the failed disk through the check disk data.

[0003] In the traditional hard disk reconstruction implementation method, when I / O hits the hard disk reconstruction disk, the system will consider that the hard disk cannot be read or written, and can only update the verification data (write I / O) or restore the data (read I / O). This usually introduces write amplification behavior, which not only increases hard disk wear, but also reduces the effective I / O bandwidth. Summary of the invention

[0004] In view of this, the present invention provides a read / write request processing method, device, equipment, medium and product to reduce the number of write amplification I / Os during hard disk reconstruction in a RAID system and improve read / write I / O performance.

[0005] In a first aspect, the present invention provides a method for processing read and write requests, the method comprising: monitoring the physical address range of the target hard disk currently being reconstructed; distinguishing between a completed reconstruction area and an uncompleted reconstruction area in the target hard disk based on the current reconstructed physical address range; when an I / O request hits a completed reconstruction area, allowing the I / O request to directly read and write operations; when an I / O request hits an uncompleted reconstruction area, suspending the I / O request.

[0006] In an optional implementation, when an I / O request hits an unfinished reconstruction area, suspending the I / O request includes: the unfinished reconstruction area includes an area being rebuilt and an area that has not started reconstruction; when the I / O request hits an area being rebuilt, suspending the I / O request; when the I / O request hits an unfinished reconstruction area, determining whether to perform a write amplification operation based on the system status.

[0007] In an optional embodiment, when an I / O request hits an area being rebuilt, suspending the I / O request includes: establishing a mutual exclusion information table; the mutual exclusion information table includes an information validity indicator, a virtual hard disk ID number, a sub-group ID number, a data shard ID number and the number of data shards; when the I / O request hits the mutual exclusion information table, suspending the I / O request; the mutual exclusion information table indicates that the area is being rebuilt.

[0008] In an optional implementation, when an I / O request hits the mutual exclusion information table and suspends the I / O request, the following steps are performed: after the target hard disk is rebuilt, the mutual exclusion information table is released; and the suspended I / O request is released and executed.

[0009] In an optional embodiment, the method also includes: if the minimum physical address of the I / O request is smaller than the current reconstructed physical address, the I / O request hits the reconstructed area; if the minimum physical address of the I / O request is greater than or equal to the current reconstructed physical address, the I / O request hits the unreconstructed area.

[0010] In a second aspect, the present invention provides a read-write request processing device, the device comprising: a hard disk monitoring module, used to monitor the physical address range of the target hard disk currently being reconstructed; an area differentiation module, used to distinguish between the completed reconstruction area and the uncompleted reconstruction area in the target hard disk based on the current reconstructed physical address range; an I / O read-write module, used to allow the I / O request to directly read and write when the I / O request hits the completed reconstruction area; and an I / O suspension module, used to suspend the I / O request when the I / O request hits the uncompleted reconstruction area.

[0011] In an optional embodiment, the I / O suspension module is also used for: the unfinished reconstruction area includes the reconstruction area and the reconstruction area that has not started; when the I / O request hits the reconstruction area, the I / O request is suspended; when the I / O request hits the reconstruction area that has not started, whether to perform a write amplification operation is determined according to the system status.

[0012] In a third aspect, the present invention provides a computer device, comprising: a memory and a processor, the memory and the processor being communicatively connected to each other, the memory storing computer instructions, and the processor executing the computer instructions to execute a read / write request processing method of the first aspect or any corresponding embodiment thereof.

[0013] In a fourth aspect, the present invention provides a computer-readable storage medium having computer instructions stored thereon, the computer instructions being used to enable a computer to execute a read / write request processing method according to the first aspect or any corresponding embodiment thereof.

[0014] In a fifth aspect, the present invention provides a computer program product, including computer instructions, which are used to enable a computer to execute a read / write request processing method according to the first aspect or any corresponding embodiment thereof.

[0015] The technical solution provided by this application may have the following beneficial effects:

[0016] By monitoring the physical address range of the target hard disk currently being rebuilt, the specific physical address range of the hard disk currently undergoing reconstruction can be obtained in real time, providing data support for the subsequent area division; based on the physical address range of the current reconstruction, the target hard disk is distinguished from the area that has been rebuilt and the area that has not been rebuilt, and different processing measures are taken for different areas; when the I / O request hits the area that has been rebuilt, the I / O request is allowed to directly read and write operations to avoid write amplification; when the I / O request hits the area that has not been rebuilt, the I / O request is suspended to avoid direct read and write operations. The above scheme, by distinguishing hard disk areas and using different strategies for different areas, reduces the number of write amplification I / Os, increases the effective I / O bandwidth of the hard disk, and improves the read and write I / O performance. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order to more clearly illustrate the specific implementation methods of the present invention or the technical solutions in the prior art, the drawings required for use in the specific implementation methods or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some implementation methods of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0018] Figure 1 is a flowchart of a method for processing a read / write request according to an embodiment of the present invention;

[0019] Figure 2 is a flow chart of an I / O request suspension release method according to an embodiment of the present invention;

[0020] Figure 3 is a flow chart of a current reconstruction physical address update method according to an embodiment of the present invention;

[0021] Figure 4 is a structural block diagram of a read / write request processing device according to an embodiment of the present invention;

[0022] Figure 5 It is a schematic diagram of the hardware structure of a computer device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0023] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present invention.

[0024] According to an embodiment of the present invention, an embodiment of a read and write request processing method is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0025] In this embodiment, a method for processing a read / write request is provided. Figure 1 is a flow chart of a method for processing a read / write request according to an embodiment of the present invention. Figure 1 As shown, the process includes the following steps:

[0026] Step S101, monitoring the physical address range of the target hard disk currently being reconstructed.

[0027] Real-time monitoring of the physical address range of the target hard disk that needs to be rebuilt, which is currently undergoing a reconstruction operation. The physical address range refers to a continuous address space from a certain starting physical address to a certain ending physical address on the hard disk. This space contains multiple physical blocks (such as sectors, blocks, etc.), each of which has a unique physical address corresponding to it, which is used in the present invention to subsequently distinguish the read and write areas of the hard disk. Optionally, the physical address range of the current reconstruction operation is recorded, and when the hard disk reconstruction progress changes, the recorded physical address range is updated.

[0028] Step S102: based on the currently reconstructed physical address range, distinguish between the reconstructed area and the unreconstructed area in the target hard disk.

[0029] The data space of the hard disk is divided into different areas using the physical address as the basis for division. By comparing the physical address of the I / O request with the physical address range of the ongoing reconstruction operation, it is determined whether the I / O request hits the completed reconstruction area or the uncompleted reconstruction area. The completed reconstruction area refers to the physical address range on the hard disk where the data has been successfully recovered and is available during the hard disk reconstruction process. The uncompleted reconstruction area refers to the physical address range on the hard disk where the data recovery operation has not yet been completed during the hard disk reconstruction process.

[0030] Optionally, as the hard disk reconstruction process proceeds, the boundaries of the address ranges of the completed and uncompleted areas are dynamically updated to ensure the accuracy of the partitioning results.

[0031] Step S103: When the I / O request hits the rebuilt area, the I / O request is allowed to directly read and write.

[0032] If the physical address of the I / O request is within the completed reconstruction area, indicating that the hard disk reconstruction process has been completed for this part of the I / O request, the I / O request is allowed to directly read and write to the hard disk, thus reducing unnecessary write amplification operations.

[0033] Step S104: When the I / O request hits the unfinished reconstruction area, the I / O request is suspended.

[0034] If the physical address of an I / O request is located in an area that has not been rebuilt, this part of the I / O request may be incomplete or unavailable, and direct read and write operations may cause data corruption or loss. In this case, the I / O request will be suspended and processed after the reconstruction of the area is completed.

[0035] In summary, the read and write request processing method provided in this embodiment effectively reduces the number of write amplification I / Os through area division and I / O request processing strategy, thereby increasing the effective I / O bandwidth of the hard disk and improving the read and write I / O performance.

[0036] Furthermore, the above step S104 includes:

[0037] Step S1041: The unfinished reconstruction area includes the area being reconstructed and the area not yet started to be reconstructed.

[0038] The unfinished reconstruction area refers to the data space in the RAID hard disk that has not yet completed the reconstruction process. According to the different reconstruction progress of the hard disk, it is further divided into the reconstruction area and the reconstruction area that has not started. The reconstruction area refers to the physical address range where the reconstruction operation is in progress, while the reconstruction area that has not started refers to the physical address range where the reconstruction operation has not yet started.

[0039] Step S1042: When the I / O request hits the area being rebuilt, the I / O request is suspended.

[0040] When the physical address of an I / O request falls within the rebuilding area, the data in the area is being rebuilt and the data is inconsistent or unavailable, so the hard disk cannot read or write. To avoid introducing write amplification behavior, the I / O request is suspended, that is, temporarily stored in the I / O suspension device and waits. I / O suspension refers to implementing I / O suspension in the RAID controller or I / O scheduler to temporarily store and process I / O requests that hit the rebuilding area.

[0041] Step S1043: When the I / O request hits the area that has not started to be rebuilt, it is determined whether to perform a write amplification operation according to the system state.

[0042] When the physical address of an I / O request falls within an area that has not started to be rebuilt, the system needs to determine whether to perform a write amplification operation based on the current system status. The data in the area that has not started to be rebuilt has not yet been rebuilt, so directly reading and writing data may cause data inconsistency or corruption. However, in some cases, in order to ensure business continuity and data availability, a write amplification operation will be performed, that is, the I / O request is satisfied by reading data from non-faulty disks and recalculating the check data. Optionally, when the I / O load is low and the reconstruction progress is fast, choose not to perform the write amplification operation to reduce hard disk wear and improve performance; when the I / O load is high and the reconstruction progress is slow, perform the write amplification operation to ensure business continuity.

[0043] Furthermore, the above step S1042 includes:

[0044] Step a11, establishing a mutually exclusive information table; the mutually exclusive information table includes information validity indicators, virtual hard disk ID number, subgroup ID number, data slice ID number and data slice quantity.

[0045] The mutual exclusion information table is a data structure used to represent the mutual exclusion space, that is, the hard disk data space that is undergoing reconstruction in the RAID system. The mutual exclusion information table uses the data stripe as the basic unit and includes:

[0046] Information validity index (Valid, VLD): characterizes whether the mutually exclusive space information is valid.

[0047] Virtual Disk ID (VID): In a RAID system, each virtual hard disk has a unique ID number to identify its identity and location.

[0048] Span ID: In some RAID implementations, the virtual hard disk is further divided into multiple spans to better manage data and optimize performance. The span ID is used to identify the span.

[0049] Stripe ID: Stripe is the basic unit of data organization in a RAID system. It usually represents a segment of data stored continuously on a physical hard disk. Stripe ID is used to uniquely identify these data stripes.

[0050] Number of data shards (StripeNum): represents the number of Stripe sizes contained in the mutually exclusive space.

[0051] The mutual exclusion information table can indicate which data blocks in the RAID system are being rebuilt, providing a basis for subsequent I / O request processing.

[0052] Step a12: When the I / O request hits the mutual exclusion information table, the I / O request is suspended; the mutual exclusion information table indicates that the area is being rebuilt.

[0053] In a RAID system, if an I / O request hits a mutex information table, the I / O request is suspended, that is, temporarily stored in an I / O suspension device and waits until the reconstruction process is completed and the mutex information is released before continuing to perform read and write operations.

[0054] Furthermore, after the above step a12, the method further includes:

[0055] Step b11: After the target hard disk is rebuilt, the mutex information table is released.

[0056] When the target hard disk in the RAID system is rebuilt, the system needs to release the mutex information table to reclaim the occupied memory or resources. Releasing the mutex information table can delete the table from the memory or mark it as invalid, ensuring that the subsequent judgment of the hit area of ​​the I / O request will not refer to the processed hard disk reconstruction area. The system can accurately judge the hit area of ​​the I / O request and ensure the consistency and integrity of the data.

[0057] Step b12, release the suspended I / O request and execute it.

[0058] After the target hard disk completes the reconstruction process and releases the mutual exclusion information table, the I / O request that hits the mutual exclusion information table and is suspended can start to execute. Traverse the waiting queue in the I / O suspension device, release the suspended I / O request, and send it to the corresponding device for read and write operations. Optionally, the execution order of the request is determined based on the priority, waiting time and other factors of the I / O request, ensuring that high-priority or long-waiting requests can be processed first, thereby improving system efficiency.

[0059] In an embodiment of the present invention, Figure 2 As shown in the figure, the virtual disk (Virtual Disk, VD) includes multiple hard disks (Physical Disk, PD), Stripe is a subgroup, and Span is a data slice. In the hard disk, a mutex information table is created for the I / O inaccessible mutex space. IO A and IO C hit the mutex information table and are suspended for control; IO B does not hit the mutex information table and is directly issued. After the target hard disk is rebuilt, the mutex information table is released, and the suspended IO A and IO C continue to be issued.

[0060] In an optional implementation, a read / write request processing method further includes:

[0061] Step S201A: If the minimum physical address of the I / O request is smaller than the currently reconstructed physical address, the I / O request hits the reconstructed area.

[0062] Determine the relationship between the minimum physical address (Min_PBA) of the I / O request and the current rebuilt physical address (Rebuild PBA). If the minimum physical address of the I / O request is smaller than the current rebuilt physical address, it indicates that the target data of the I / O request is located in the area that has been rebuilt. In this case, the RAID system can allow the I / O request to directly perform read and write operations.

[0063] Step S201B: if the minimum physical address of the I / O request is greater than or equal to the currently reconstructed physical address, the I / O request hits the unfinished reconstruction area.

[0064] If the minimum physical address of the I / O request is greater than or equal to the currently rebuilt physical address, it indicates that the target data of the I / O request is located at a location where the reconstruction has not started. In this case, it is necessary to decide whether to perform the write amplification operation based on the system status.

[0065] Through steps S201A and S201B, the RAID system can more accurately determine the location of the I / O request and adopt a corresponding processing strategy, thereby optimizing the read and write I / O performance during the hard disk reconstruction process.

[0066] Optionally, after the current data space is reconstructed, the physical address of the current reconstruction is updated, and then the mutual exclusion information of the next data space is updated. Figure 3 As shown, the physical addresses in the hard disk are numbered from PBA0 to PBAn, and the current rebuild physical address (Rebuild PBA) is PBAx. At this time, the area from PBA0 to PBAx is the data space that has been rebuilt (Rebuilt), and the data area starting from PBAx is the data space that is being rebuilt, and the remaining space is the data space that has not started to be rebuilt. When the reconstruction of this data space is completed, the Rebuild PBA is updated to PBAy, and the data space that is being rebuilt is updated accordingly.

[0067] In the embodiment of the present invention, when the I / O hits the Rebuild data space, the comparison of the I / O quantity between the method of the present invention and the traditional method is as follows:

[0068]

[0069] In summary, the use of full stripes reduces the common write amplification phenomenon, reduces the write operation burden of the hard disk, and extends the service life of the hard disk. By reducing the number of write amplification I / Os, the effective I / O bandwidth of the hard disk is increased, thereby improving the performance of the system when processing concurrent I / O operations. The method reduces penalty data storage, improves resource utilization, and reduces resource consumption caused by data recovery. It is suitable for various environments using RAID 1 / 5 / 6 systems, whether it is a data center, enterprise storage or personal high-performance storage solution, it can benefit from it. The method can dynamically adjust according to the mutex table resources and the Rebuild process to adapt to changing workloads and environmental conditions.

[0070] In this embodiment, a read / write request processing device is also provided, which is used to implement the above-mentioned embodiments and preferred implementation modes, and the descriptions that have been made will not be repeated. As used below, the term "module" can implement a combination of software and / or hardware of a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceivable.

[0071] This embodiment provides a read / write request processing device, such as Figure 4 As shown, including:

[0072] The hard disk monitoring module 401 is used to monitor the physical address range of the target hard disk currently being rebuilt;

[0073] The area distinguishing module 402 is used to distinguish between the area that has been rebuilt and the area that has not been rebuilt in the target hard disk based on the physical address range of the current reconstruction;

[0074] The I / O read / write module 403 is used to allow the I / O request to directly read and write when the I / O request hits the rebuilt area;

[0075] The I / O suspension module 404 is used to suspend the I / O request when the I / O request hits the unfinished reconstruction area.

[0076] In an optional implementation, the I / O suspension module 404 is further configured to:

[0077] The first I / O suspension unit is used for the unfinished reconstruction area including the reconstruction area and the reconstruction area that has not started.

[0078] The second I / O suspension unit is used to suspend the I / O request when the I / O request hits the area being rebuilt.

[0079] The third I / O suspension unit is used to determine whether to perform a write amplification operation according to a system state when an I / O request hits a region that has not started to be rebuilt.

[0080] In an optional implementation, the second I / O suspension unit includes:

[0081] The first mutually exclusive information table unit is used to establish a mutually exclusive information table; the mutually exclusive information table includes an information validity indicator, a virtual hard disk ID number, a subgroup ID number, a data slice ID number, and the number of data slices.

[0082] The second mutual exclusion information table unit is used to suspend the I / O request when the I / O request hits the mutual exclusion information table; the mutual exclusion information table indicates that the area is being rebuilt.

[0083] In an optional embodiment, the device further comprises:

[0084] The first suspension release unit is used to release the mutex information table after the target hard disk is rebuilt.

[0085] The second suspension release unit is used to release the suspended I / O request and execute it.

[0086] In an optional embodiment, the device further comprises:

[0087] The first area judgment unit is used to determine that the I / O request hits the area that has been rebuilt if the minimum physical address of the I / O request is smaller than the currently rebuilt physical address.

[0088] The second area judgment unit is used to determine that the I / O request hits the unfinished reconstruction area if the minimum physical address of the I / O request is greater than or equal to the currently reconstructed physical address.

[0089] The further functional description of each of the above modules and units is the same as that of the above corresponding embodiments and will not be repeated here.

[0090] A read / write request processing device in this embodiment is presented in the form of a functional unit, where the unit refers to an ASIC (Application I / On Specific Integrated Circuit) circuit, a processor and memory that executes one or more software or fixed programs, and / or other devices that can provide the above functions.

[0091] The embodiment of the present invention also provides a computer device having the above Figure 4 A read-write request processing device is shown.

[0092] See also Figure 5 , Figure 5 is a schematic diagram of the structure of a computer device provided by an optional embodiment of the present invention, such as Figure 5As shown, the computer device includes: one or more processors 10, a memory 20, and interfaces for connecting various components, including high-speed interfaces and low-speed interfaces. Various components are connected to each other using different buses for communication, and can be installed on a common mainboard or installed in other ways as needed. The processor can process the instructions executed in the computer device, including instructions stored in or on the memory to display the graphical information of the GUI on an external input / output device (such as, a display device coupled to the interface). In some optional embodiments, if necessary, multiple processors and / or multiple buses can be used together with multiple memories and multiple memories. Similarly, multiple computer devices can be connected, and each device provides some necessary operations (for example, as a server array, a group of blade servers, or a multi-processor system). Figure 5 A processor 10 is taken as an example.

[0093] The processor 10 may be a central processing unit, a network processor or a combination thereof. The processor 10 may further include a hardware chip. The hardware chip may be a dedicated integrated circuit, a programmable logic device or a combination thereof. The programmable logic device may be a complex programmable logic device, a field programmable gate array, a general purpose array logic or any combination thereof.

[0094] The memory 20 stores instructions executable by at least one processor 10, so that at least one processor 10 executes the method shown in the above embodiment.

[0095] The memory 20 may include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function; the data storage area may store data created according to the use of the computer device, etc. In addition, the memory 20 may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some optional embodiments, the memory 20 may optionally include a memory remotely arranged relative to the processor 10, and these remote memories may be connected to the computer device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0096] The memory 20 may include a volatile memory, such as a random access memory; the memory may also include a non-volatile memory, such as a flash memory, a hard disk or a solid state drive; the memory 20 may also include a combination of the above types of memory.

[0097] The computer device also includes an input device 30 and an output device 40. The processor 10, the memory 20, the input device 30 and the output device 40 may be connected via a bus or other means. Figure 5 The example of connecting through bus is taken in the following.

[0098] The input device 30 can receive input digital or character information, and generate key signal input related to the user settings and function control of the computer device, such as a touch screen, a keypad, a mouse, a track pad, a touch pad, an indicator bar, one or more mouse buttons, a trackball, a joystick, etc. The output device 40 may include a display device, an auxiliary lighting device (e.g., an LED) and a tactile feedback device (e.g., a vibration motor), etc. The above-mentioned display device includes but is not limited to a liquid crystal display, a light emitting diode, a display and a plasma display. In some optional embodiments, the display device can be a touch screen.

[0099] The embodiment of the present invention also provides a computer-readable storage medium. The method according to the embodiment of the present invention can be implemented in hardware, firmware, or can be implemented as a computer code that can be recorded in a storage medium, or can be implemented as a computer code that is originally stored in a remote storage medium or a non-temporary machine-readable storage medium and will be stored in a local storage medium through a network download, so that the method described herein can be stored in such software processing on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. Among them, the storage medium can be a magnetic disk, an optical disk, a read-only storage memory, a random access memory, a flash memory, a hard disk or a solid-state hard disk, etc.; further, the storage medium can also include a combination of the above types of memories. It can be understood that a computer, a processor, a microprocessor controller, or programmable hardware includes a storage component that can store or receive software or computer code. When the software or computer code is accessed and executed by a computer, a processor, or hardware, the method shown in the above embodiment is implemented.

[0100] A part of the present invention may be applied as a computer program product, such as a computer program instruction, which, when executed by a computer, can call or provide the method and / or technical solution according to the present invention through the operation of the computer. Those skilled in the art should understand that the existence of the computer program instruction in a computer-readable medium includes, but is not limited to, a source file, an executable file, an installation package file, etc., and accordingly, the way in which the computer program instruction is executed by the computer includes, but is not limited to: the computer directly executes the instruction, or the computer compiles the instruction and then executes the corresponding compiled program, or the computer reads and executes the instruction, or the computer reads and installs the instruction and then executes the corresponding installed program. Here, the computer-readable medium may be any available computer-readable storage medium or communication medium accessible to the computer.

[0101] Although the embodiments of the present invention have been described in conjunction with the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present invention, and such modifications and variations are all within the scope defined by the appended claims.

Claims

1. A method for processing a read / write request, characterized in that: The method comprises: Monitor the physical address range of the target hard disk currently being rebuilt; Based on the currently reconstructed physical address range, distinguish between a reconstructed area and an unreconstructed area in the target hard disk; When an I / O request hits the rebuilt area, allowing the I / O request to directly read and write operations; When the I / O request hits the unfinished reconstruction area, the I / O request is suspended.

2. The method according to claim 1, characterized in that: When the I / O request hits the unfinished reconstruction area, suspending the I / O request includes: The unfinished reconstruction area includes the area being rebuilt and the area where reconstruction has not started; When the I / O request hits the rebuilding area, suspending the I / O request; When the I / O request hits the area where reconstruction has not started, it is determined whether to perform a write amplification operation according to a system state.

3. The method according to claim 2, characterized in that When the I / O request hits the rebuilding area, suspending the I / O request includes: Establishing a mutually exclusive information table; the mutually exclusive information table includes information validity indicators, virtual hard disk ID numbers, subgroup ID numbers, data shard ID numbers, and data shard quantity; When an I / O request hits the mutual exclusion information table, the I / O request is suspended; the mutual exclusion information table represents the area being rebuilt.

4. The method according to claim 3, characterized in that When the I / O request hits the mutual exclusion information table, after the I / O request is suspended, the method includes: After the target hard disk is rebuilt, the mutex information table is released; The suspended I / O request is released and executed.

5. The method according to claim 1, characterized in that: The method further comprises: If the minimum physical address of the I / O request is smaller than the currently reconstructed physical address, the I / O request hits the reconstructed area; If the minimum physical address of the I / O request is greater than or equal to the currently reconstructed physical address, the I / O request hits the unfinished reconstruction area.

6. A read / write request processing device, characterized in that: The device comprises: A hard disk monitoring module is used to monitor the physical address range of the target hard disk currently being rebuilt; A region distinguishing module, used for distinguishing between a region in the target hard disk that has been rebuilt and a region in the target hard disk that has not been rebuilt, based on the currently rebuilt physical address range; An I / O read / write module, used for allowing the I / O request to directly read and write when the I / O request hits the rebuilt area; The I / O suspension module is used to suspend the I / O request when the I / O request hits the unfinished reconstruction area.

7. The device according to claim 6, characterized in that The I / O suspension module is also used for: The unfinished reconstruction area includes the area being rebuilt and the area where reconstruction has not started; When the I / O request hits the rebuilding area, suspending the I / O request; When the I / O request hits the area where reconstruction has not started, it is determined whether to perform a write amplification operation according to a system state.

8. A computer device, characterized in that: include: A memory and a processor, wherein the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the method according to any one of claims 1 to 5 by executing the computer instructions.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a computer to execute the method according to any one of claims 1 to 5.

10. A computer program product, characterized in that The method comprises computer instructions for causing a computer to execute the method according to any one of claims 1 to 5.

Images