Information Synchronization Method, Device, Medium and Program Product

Abstract

The present invention provides an information synchronization method, device, medium and program product, which can be applied to the storage technology field. The information synchronization method is applied to a disk array, and the disk array includes a first disk controller and a second disk controller; the method includes: obtaining a to-be-marked bitmap and an initialization bitmap; in the case where it is determined that a first target stripe belongs to the first disk controller and is in an unused state, not performing a target operation on the first target stripe, and not sending to the second disk controller the execution status information of the target operation and the execution status information of the initialization operation for synchronously updating the first target stripe; in response to determining that each disk controller has executed the target operation, processing the marked bitmap and the initialization bitmap of each disk controller to generate a target initialization bitmap; and performing an initialization operation based on the target initialization bitmap to achieve information synchronization of each disk controller.

Description

Technical Field

[0001] The present invention relates to the field of storage technology, and particularly to an information synchronization method, apparatus, device, medium and program product. Background Art

[0002] With the development of storage technology, a centralized multi-controller system can be used to control and manage multiple disks. For example, by synchronizing the metadata in each controller to achieve data fault tolerance when a disk fails, or by synchronizing the metadata in each controller during the recovery process of dirty data to save system resources.

[0003] Since the communication frequency of metadata between controllers is high and the communication time-consuming is long, the communication transmission pressure between controllers is relatively large. Summary of the Invention

[0004] In view of the above problems, the present invention provides an information synchronization method, device, medium and program product.

[0005] According to a first aspect of the present invention, there is provided an information synchronization method, which is applied to a disk array including a first disk controller and a second disk controller. The method includes: obtaining a to-be-marked bitmap and an initialization bitmap, where the to-be-marked bitmap indicates the execution status of a target operation performed on data blocks stored in multiple stripes of the disk array, and the initialization bitmap indicates whether an initialization operation needs to be performed on the data blocks; in the case where it is determined that a first target stripe among the multiple stripes represents a stripe managed by the first disk controller and in a used state, performing the target operation on the data blocks stored in the first target stripe, and marking the execution status of the first target stripe in the to-be-marked bitmap as executed to generate a marked bitmap; sending information for synchronously updating the execution status of the first target stripe to the second disk controller; in the case where it is determined that the first target stripe is a stripe managed by the first disk controller and in an unused state, not performing the target operation on the first target stripe, and not sending information for synchronously updating the execution status of the target operation and the execution status of the initialization operation of the first target stripe to the second disk controller; in response to determining that each disk controller has performed the target operation, processing the marked bitmap and the initialization bitmap of each disk controller to generate a target initialization bitmap; and performing an initialization operation based on the target initialization bitmap to achieve information synchronization of each disk controller.

[0006] A second aspect of the present invention provides an electronic device, including: one or more processors; a memory for storing one or more computer programs, where the one or more processors execute the one or more computer programs to implement the steps of the above method.

[0007] The third aspect of the present invention further provides a computer-readable storage medium on which a computer program or instruction is stored. When the computer program or instruction is executed by a processor, the steps of the above method are implemented.

[0008] The fourth aspect of the present invention further provides a computer program product, comprising a computer program or instructions, which implement the steps of the above method when executed by a processor.

[0009] According to an embodiment of the present invention, the first disk controller only marks the execution status of the stripes in use, and only sends the execution status information for synchronously updating the stripes in use to the second disk controller used to back up the storage data of the first disk controller. This reduces the number of operations performed on the stripes in an unused state and the number of information synchronizations between the disk controllers, thereby reducing the communication transmission pressure between the disk controllers. In addition, after determining that each disk controller has completed the target operation, the initialization bitmap is updated at one time, so that during the execution of the target operation, the disk controllers do not need to synchronously update the initialization bitmap, and the verification consistency of each storage area in the disk array is still maintained. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] The above contents and other objects, features and advantages of the present invention will become more apparent through the following description of the embodiments of the present invention with reference to the accompanying drawings, in which:

[0011] Figure 1 An application scenario diagram of an information synchronization method, device, medium, and program product according to an embodiment of the present invention is shown;

[0012] Figure 2 A flowchart of an information synchronization method according to an embodiment of the present invention is shown;

[0013] Figure 3 An example diagram showing a valid area and an invalid area according to an embodiment of the present invention is shown;

[0014] Figure 4 An example diagram showing a bitmap to be marked and an initialization bitmap according to an embodiment of the present invention;

[0015] Figure 5 A schematic diagram showing changes in a to-be-marked bitmap and an initialization bitmap of a single disk controller during execution of a target operation task according to an embodiment of the present invention is shown;

[0016] Figure 6 A schematic diagram showing a target bitmap obtained by conversion based on a stripe identifier mapping relationship according to an embodiment of the present invention;

[0017] Figure 7AShows a schematic diagram of the changes in the bitmap to be marked and the initialization bitmap when the usage status of a single disk controller changes during the execution of a target operation task according to an embodiment of the present invention;

[0018] Figure 7B Shows a schematic diagram of the changes in the bitmap to be marked and the initialization bitmap when the ownership status of a single disk controller changes during the execution of a target operation task according to an embodiment of the present invention;

[0019] Figure 8 Shows a time quantization schematic diagram of asynchronously completing the information synchronization of each disk controller during the execution of a target operation task in related examples;

[0020] Figure 9 Shows a time quantization schematic diagram of asynchronously completing the information synchronization of each disk controller during the execution of a target operation task according to an embodiment of the present invention;

[0021] Figure 10 Shows a schematic diagram of the reorganization of the backup relationships of each disk controller according to an embodiment of the present invention;

[0022] Figure 11 Shows a block diagram of an electronic device suitable for implementing an information synchronization method according to an embodiment of the present invention. Detailed implementation manners

[0023] Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings. However, it should be understood that these descriptions are merely exemplary and are not intended to limit the scope of the present invention. In the following detailed description, for the sake of explanation, many specific details are set forth to provide a comprehensive understanding of the embodiments of the present invention. However, obviously, one or more embodiments can also be implemented without these specific details. In addition, in the following description, descriptions of well-known structures and technologies are omitted to avoid unnecessarily confusing the concepts of the present invention.

[0024] The terms used herein are merely for describing specific embodiments and are not intended to limit the present invention. The terms "including", "comprising", etc. used herein indicate the presence of the described features, steps, operations, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, or components.

[0025] All terms used herein (including technical and scientific terms) have the meanings commonly understood by those skilled in the art, unless otherwise defined. It should be noted that the terms used herein should be interpreted as having a meaning consistent with the context of this specification and should not be interpreted in an idealized or overly rigid manner.

[0026] In cases where expressions such as "at least one of A, B, and C" are used, generally, it should be interpreted according to the meaning that a person skilled in the art would usually understand such an expression (for example, "a system having at least one of A, B, and C" should include, but not be limited to, a system having only A, only B, only C, having A and B, having A and C, having B and C, and / or having A, B, and C, etc.).

[0027] In a centralized multi-disk controller storage system, for example: in a four-disk controller system, some data information being processed by nodes in the mirror pairs formed by every two disks can be circularly backed up, and the fault tolerance for real-time failures is achieved through pairwise synchronization and backup of nodes.

[0028] In terms of input / output processing logic, the storage system divides the areas on the disks and each disk controller independently manages reading and writing, enabling each disk controller within the four-disk controller to ensure the order of reading and writing without inter-disk controller locks, thereby achieving efficient and accurate reading and writing processing.

[0029] Meanwhile, in the process of implementing the real-time fault tolerance function, interactions between disk controllers are required. By dividing the areas of tasks being executed between nodes and sending the real-time execution status of the marker information on these areas to the peer nodes, the backup redundancy of metadata / write data information in the four-controller system during node failures is achieved. Metadata can be used to represent the execution status of each disk controller for performing target operations on the affiliated stripes. Target operations can include, for example, data reconstruction operations, dirty data recovery operations, etc.

[0030] To achieve data fault tolerance in the event of a hard disk failure for stored data, the operating system manages the disks by creating a RAID (Redundant Arrays of Independent Disks) on multiple disks; RAID generates parity data based on user data through an exclusive OR algorithm and stores the mapping rules generated by dividing these data into chunks according to a specific distribution strategy on the disks, thereby achieving data management and redundant recovery at the software level; after a failure occurs, RAID starts a reconstruction background task, and according to the corresponding decoding algorithm, for example: the exclusive OR algorithm restores the failed part / lost user data / parity data based on the parity data and user data information on the remaining non-failed chunks.

[0031] For data reconstruction tasks, the reconstruction time for reconstructing each TB of valid data is an important indicator that reflects the performance of the reconstruction task. After completing the data reconstruction, the metadata between the disk controllers needs to be synchronized to ensure the array consistency of the reconstructed storage area, also known as verification consistency. This avoids the scenario where after the valid storage area used by the user is expanded, there are inconsistencies in I / O reads and writes due to non-reconstruction or non-initialization. And after a disk controller fails, the disk controller that takes over the business of the failed disk controller misses reconstruction or initialization due to failure to synchronize metadata, which leads to data inconsistency between the disk controllers.

[0032] Therefore, an embodiment of the present invention provides an information synchronization method, in which the first disk controller only marks the execution status of the stripes in use, and only sends the execution status information for synchronously updating the stripes in use to the second disk controller used to back up the storage data of the first disk controller. This reduces the number of operations performed on the stripes in an unused state and the number of information synchronizations between the disk controllers, thereby reducing the communication transmission pressure between the disk controllers. In addition, after determining that each disk controller has completed the target operation, the initialization bitmap is updated at one time, so that during the execution of the target operation, the disk controllers do not need to synchronously update the initialization bitmap, and the verification consistency of each storage area in the disk array is still maintained.

[0033] Figure 1 An application scenario diagram of an information synchronization method, device, medium, and program product according to an embodiment of the present invention is shown.

[0034] like Figure 1 As shown, the information synchronization method is applied to a disk array 100, and the disk array 100 may include four disk controllers, namely: a disk controller Dc 0 101. Disk controller Dc 1 102. Disk Controller Dc 2 103 and disk controller Dc 3 104.

[0035] Disk Controller Dc 0 101 and disk controller Dc 1 102 can form a domain, in which the disk controller Dc 0 101 acts as the master node to perform input / output read and write operations, and the disk controller Dc 1102 is used as a backup node to back up the execution status of the fault tolerance tasks generated during the read and write operations of the primary node in input / output. For example: marking the location and content of the temporarily stored data that has not been successfully flushed; or the data information in the fault tolerance tasks, such as the bitmap information marking the execution status of the reconstruction task caused by disk errors. Similarly, the disk controller Dc 1 102 and the disk controller Dc 2 103 can also form a domain, the disk controller Dc 2 103 and the disk controller Dc 3 104 can also form a domain, the disk controller Dc 3 104 and the disk controller Dc 0 101 can also form a domain.

[0036] Since creating a disk array in the storage system is based on a storage disk group of a fixed size. During user usage, when the user creates a volume, usually only the created volume part is used for data read and write operations. Therefore, it is possible to only reconstruct the valid area that the user is using, and for the deleted and invalid unused areas, by marking the metadata of the initialization task, after the reconstruction task is completed, the initialization task is started again to maintain the parity consistency of each data block and parity block, thereby improving the execution speed of the reconstruction task.

[0037] However, this method of only reconstructing the valid area that the user is using only reduces the number of times the reconstruction operation is executed, and the number of times of metadata synchronization between each disk controller does not change. That is to say, the metadata communication between each disk controller still maintains the original frequency. During the actual simulation test process, it is found that the time-consuming of metadata communication between each disk controller accounts for a relatively large proportion in the overall reconstruction task.

[0038] Therefore, by using each disk controller to respectively execute the information synchronization method provided by the embodiments of the present invention, the metadata synchronization operation between each disk controller can be optimized, and the information transmission pressure between each disk controller can be reduced. Thereby reducing the fluctuation of the task execution time-consuming in the scenario where the asynchronous information is blocked by the data communication of the remaining disk controllers, and further improving the stability of the asynchronous communication between each disk controller.

[0039] It should be noted that Figure 1 The number of disk controllers shown is only illustrative, and the method provided by the embodiments of the present invention is applicable to disk arrays with different numbers of disk controllers.

[0040] The following will be based on Figure 1 the described scenario, through Figures 2 - 9 to describe the information synchronization method of the public embodiments in detail.

[0041] Figure 2 The flowchart of the information synchronization method according to an embodiment of the present invention is shown.

[0042] As Figure 2 shown, the information synchronization method 200 of this embodiment includes operation S210 to operation S250.

[0043] In operation S210, an execution status to-be-marked bitmap for indicating the execution status of a target operation performed on data blocks stored in multiple stripes in a disk array and an initialization bitmap for indicating whether an initialization operation needs to be performed on the data blocks are obtained.

[0044] In operation S220, when it is determined that the first target stripe among the multiple stripes represents a stripe that belongs to and is in a used state under the management of the first disk controller, a target operation is performed on the data blocks stored in the first target stripe, and the execution status of the first target stripe in the to-be-marked bitmap is marked as executed, a marked bitmap is generated, and information for synchronously updating the execution status of the first target stripe is sent to the second disk controller.

[0045] In operation S230, when it is determined that the first target stripe is a stripe that belongs to and is in an unused state under the management of the first disk controller, no target operation is performed on the first target stripe, and no information for synchronously updating the execution status of the target operation and the execution status of the initialization operation of the first target stripe is sent to the second disk controller.

[0046] In operation S240, in response to determining that each disk controller has performed the target operation, the marked bitmaps and the initialization bitmaps of each disk controller are processed to generate a target initialization bitmap.

[0047] In operation S250, an initialization operation is performed based on the target initialization bitmap to achieve information synchronization of each disk controller.

[0048] According to an embodiment of the present invention, the to-be-marked bitmap indicates the execution status of the target operation performed on data blocks stored in multiple stripes in a disk array. The target operation may include a data reconstruction operation, a dirty data recovery operation, etc.

[0049] For example: when a certain disk in the disk array fails, a data reconstruction operation can be performed on the stripes related to the failed disk to recover the data stored on the failed disk.

[0050] For example: when recovering dirty data in a storage system, the dirty data in the data blocks stored in all stripes can be processed to achieve reasonable utilization of data resources in the storage system.

[0051] Whether performing data reconstruction operations or handling dirty data, the execution status of each operation, i.e., the metadata, needs to be synchronized among disk controllers. Each disk controller stores a full set of bitmaps to be marked. For example, in a disk array with four disk controllers, each disk controller stores a bitmap to be marked that includes all four disk controllers. The bitmap to be marked also indicates the ownership relationship between each stripe and each disk controller. Each disk controller can only perform data reconstruction or dirty data recovery operations on the data blocks stored in the stripes it belongs to, mark the execution status of the operations in the full set of bitmaps to be marked, and synchronize the metadata to another disk controller belonging to the same domain.

[0052] Figure 3 FIG. shows an example diagram of valid and invalid regions according to an embodiment of the present invention.

[0053] As Figure 3 shown, the overall region 310 can represent the entire storage area available for users. The valid region 311 can represent the storage area in use. The invalid region 312 can represent the storage area in an unused state.

[0054] According to an embodiment of the present invention, a stripe refers to the smallest logical storage unit obtained by dividing the storage areas of each disk in a disk array.

[0055] The valid region 311 can include multiple stripes in use. Target operations need to be performed on the data blocks stored in the stripes of the valid region 311. The invalid region 312 can include multiple unused stripes. Initialization operations need to be performed on the data blocks stored in the stripes of the invalid region 312.

[0056] When the target operation is a data reconstruction operation, the stripes that need to perform the data reconstruction operation are the stripes that belong to the valid region 311 and correspond to the failed disk.

[0057] When the target operation is a dirty data handling operation, the stripes that need to perform the dirty data handling operation are the stripes that belong to the valid region 311.

[0058] Figure 4 FIG. shows an example diagram of a bitmap to be marked and an initialization bitmap according to an embodiment of the present invention.

[0059] As Figure 4 shown, target operations need to be performed on the data blocks stored in the stripes of the valid region 311, and initialization operations do not need to be performed. Initialization operations need to be performed on the data blocks stored in the stripes of the invalid region 312, but target operations do not need to be performed.

[0060] Each bit in the bitmap to be marked corresponds to a stripe. The first target stripe represents a stripe that belongs to the management of the first disk controller and is in a used state.

[0061] In some embodiments, the target operation is only performed on the data blocks stored in the first target stripe of the valid area in the used state, and the execution status for the first target stripe in the bitmap to be marked is marked as executed, generating a marked bitmap. And information for synchronously updating the execution status of the first target stripe, that is, metadata, is sent to the second disk controller. Thereby reducing the number of times the target operation is performed on the data blocks stored in the stripes of the unused invalid area.

[0062] Moreover, for the data blocks stored in the stripes of the unused invalid area, there is no need to perform the target operation, nor to mark the operation execution status on the bitmap to be marked. At the same time, there is no need to initiate a synchronization request for the execution status information of the stripes in the invalid area to the second disk controller, that is, there is no need for the second disk controller to synchronize the execution status information of the stripes in the invalid area. Thereby reducing the number of times of metadata synchronization for the data blocks stored in the stripes of the unused invalid area.

[0063] However, for the data blocks stored in the stripes of the invalid area, an initialization operation still needs to be performed to ensure the parity consistency in the disk array for the stripes on which the target operation has been performed, for example: the stripes on which the data reconstruction operation has been performed.

[0064] According to an embodiment of the present invention, the initialization bitmap indicates whether an initialization operation needs to be performed on the data block. Since the execution status of the target operation for each stripe has been marked in the marked bitmaps of each disk controller, it can be understood that the reconstructed area or the area where the dirty data recovery has been performed has been marked in the marked bitmap.

[0065] Therefore, when it is determined that all disk controllers in the disk array have performed the target operation, the marked bitmaps and the initialization bitmaps of each disk controller can be processed, and it can be marked at one time in the first target initialization bitmap which stripes need to perform the initialization operation to ensure the parity consistency of the area after the target operation is performed. So as to perform the initialization operation based on the first target initialization bitmap to achieve the information synchronization of each disk controller.

[0066] Figure 5 Shows a schematic diagram of the changes in the bitmap to be marked and the initialization bitmap of a single disk controller during the execution of the target operation task according to an embodiment of the present invention.

[0067] As Figure 5As shown, in this embodiment 500, the execution status of each stripe in the bitmap 510 to be marked for task startup is "1", indicating that the target operation has not been executed. The execution status of each stripe in the initialization bitmap 520 is "0", indicating that no initialization operation is required. The current disk controller can be disk controller Dc 0 .

[0068] During task execution, disk controller Dc 0 only performs the target operation on the stripes that belong to the valid area and are attributed to Dc 0 . However, for the stripes that belong to the invalid area and are attributed to Dc 0 , they are directly skipped.

[0069] Therefore, in the bitmap 511 to be marked during task execution, the execution status of the first stripe attributed to Dc 0 changes from "1" to "0", indicating that the target operation has been completed for this stripe.

[0070] Since disk controller Dc 0 is the backup node of disk controller Dc 3 , therefore, in the bitmap 511 to be marked during task execution, the bits attributed to Dc 3 will be marked with the metadata synchronized by disk controller Dc 3 through asynchronous communication.

[0071] During task execution, there is no need to mark the initialization bitmap and synchronize metadata. Therefore, the markings of each stripe in the initialization bitmap 520 will not change.

[0072] In the marking bitmap 512, the execution status of the stripes in the valid area attributed to disk controller Dc 0 is marked as "0", indicating that the task is completed at this time. The execution status of the stripes in the valid area attributed to disk controller Dc 3 is also the same as that synchronized to disk controller Dc 0 . Therefore, the marking bitmap 512 and the initialization bitmap 520 can be bitwise "OR" operated to generate the target initialization bitmap 521. It can be seen from the target initialization bitmap 521 that there is no need to perform the initialization operation on the valid area where the operation has been executed, and the initialization operation needs to be performed on the invalid area where the operation has not been executed. Thus, the number of metadata synchronizations between disk controllers during task execution can be effectively reduced.

[0073] According to an embodiment of the present invention, the first disk controller marks only the execution status of the stripes in the used state, and sends only the execution status information for synchronously updating the stripes in the used state to the second disk controller for backing up the stored data of the first disk controller. This reduces both the number of operations performed on the stripes in the unused state and the number of information synchronizations between the disk controllers. Therefore, the communication transmission pressure between the disk controllers can be reduced. In addition, after determining that all disk controllers have completed the target operation, the initialization bitmap is updated at one time, achieving that during the execution of the target operation, without synchronously updating the initialization bitmap between the disk controllers, the parity consistency of each storage area in the disk array is still maintained.

[0074] For the data reconstruction task, since the to-be-marked bitmap indicates the execution status of the data reconstruction operations performed on the data blocks stored in each stripe related to the failed disk in the disk array, the positions of the stripes in the marked bitmap obtained after the data reconstruction operation is completed do not correspond to the positions of the stripes in the initialization bitmap.

[0075] Therefore, when the target operation is a data reconstruction operation, processing the target bitmap and the initialization bitmap of each disk controller to generate a target initialization bitmap may include the following operations: processing the marked bitmap of each disk controller based on the identification mapping relationship of each stripe to obtain a target bitmap; and processing the target bitmap and the initialization bitmap to generate a target initialization bitmap.

[0076] According to an embodiment of the present invention, the identification mapping relationship indicates the mapping between the arrangement order identification of each stripe and the row / column identification of each stripe in the disk array.

[0077] Figure 6 FIG. shows a schematic diagram of obtaining a target bitmap based on the stripe identification mapping relationship according to an embodiment of the present invention.

[0078] As Figure 6 shown, the arrangement order identification of each stripe in the disk array is identified in the full stripe bitmap 601. The stripes related to the failed disk are located in the 0th to 7th rows of the 4th column in the full stripe bitmap 601. The row identification of the stripes related to the failed disk in the marked bitmap 612 can be obtained, that is: the stripe with the stripe identification of "0" is actually the stripe number "4" in the full stripe bitmap 601. The stripe with the stripe identification of "1" is actually the stripe number "13" in the full stripe bitmap 601.

[0079] Therefore, based on the identification mapping relationship, the stripe identifiers in the marker bitmap can be converted into actual stripe numbers, and according to the arrangement order of the actual stripe numbers, the execution status information of each stripe is marked at the position corresponding to the stripe number to obtain the target bitmap. This makes the positions of the stripes in the target bitmap correspond to the positions of the stripes in the initialization bitmap.

[0080] In some embodiments, based on the identification mapping relationship of each stripe, processing the marker bitmaps of each disk controller to obtain the target bitmap may include the following operations: reading the first position identifiers of each stripe from the marker bitmaps of each disk controller; based on the identification mapping relationship of each stripe, determining the second position identifiers of each stripe in the initialization bitmap according to each first position identifier; and based on each second position identifier, marking the execution status information indicated by each marker bitmap to generate the target bitmap.

[0081] According to an embodiment of the present invention, the first position identifier indicates the row or column of each stripe in the disk array.

[0082] For example: First, the first position identifiers "0", "1", "2",..., "7" of each stripe can be read from the marker bitmap 612 of each disk controller. The stripes related to the failed disk may be in the 4th column in the disk array. This first position identifier indicates the row where the stripe related to the failed disk is located.

[0083] In some embodiments, based on the identification mapping relationship of each stripe, the arrangement order identifier of each stripe in the disk array can be determined according to each first position identifier; and the arrangement order identifier is determined as the second position identifier.

[0084] For example: The actual stripe numbers of each stripe, that is, the second position identifiers, "4", "13", "22",... "67" can be determined from the full - scale stripe bitmap 601.

[0085] Finally, mark the execution status information of each stripe according to the second position identifier to generate the target bitmap.

[0086] For example: Mark the execution status information of the stripe with stripe number "4" at the 4th position, and mark the execution status information of the stripe with stripe number "13" at the 13th position to generate the target bitmap 613.

[0087] For the data reconstruction task, since the data reconstruction operation is only performed on the stripes corresponding to the failed disk, the stripes for which the data reconstruction is performed are only a part of the full - scale stripes. Therefore, generating the target bitmap based on the identification mapping relationship of each stripe realizes the correspondence between each stripe in the target bitmap and each stripe in the initialization bitmap, so as to update the initialization bitmap bit by bit, thereby ensuring the parity consistency of the reconstructed area.

[0088] In some embodiments, processing the target bitmap and the initialization bitmap to generate a target initialization bitmap may include the following operations: performing an OR operation on the data states of each strip according to the positional correspondence between the target bitmap and each strip in the initialization bitmap to generate the target initialization bitmap.

[0089] For example: if the first bit in the target bitmap is marked as "0", indicating that the data reconstruction operation has been performed, and the first bit in the initialization bitmap is marked as "1", indicating that the initialization operation needs to be performed, then through the OR operation, the first bit in the generated target initialization bitmap should be marked as "1", indicating that the initialization operation needs to be performed.

[0090] According to the embodiments of the present invention, by performing an OR operation on the data states of each strip according to the positional correspondence between each strip in the target bitmap and the initialization bitmap, the update operation of the initialization bitmap can be completed at one time, satisfying the check consistency of the reconstructed area.

[0091] Whether for the data reconstruction task or the dirty data recovery task, during the execution of the task, the state of each strip may change due to the user's operation. For example: the user can change the usage state of each strip and the belonging relationship state between each strip and each disk controller through create or delete operations.

[0092] According to the embodiments of the present invention, the above method may further include the following operations: in response to detecting a state change operation performed on the second target strip, determining an operation strategy for the second target strip according to the changed state; marking the second target strip in the initialization bitmap as needing to perform the initialization operation to generate an updated initialization bitmap, where the second target strip belongs to the first disk controller; and in response to determining that each disk controller has completed the target operation, processing the marker bitmap of each disk controller and the updated initialization bitmap to generate a second target initialization bitmap.

[0093] Regardless of whether the change operation performed on the second target strip is a change in the usage state or a change in the belonging relationship state, the corresponding position in the initialization bitmap needs to be marked and changed. For example: changing the position corresponding to the second target strip in the initialization bitmap from "0" to "1".

[0094] However, the change of the initialization bitmap does not need to be performed in real time during the execution of the data reconstruction task or the dirty data recovery task. When it is determined that each disk controller has completed the target operation, the initialization bitmap can be updated uniformly, thereby reducing the communication times of the metadata for synchronizing the initialization bitmap between each disk controller.

[0095] According to an embodiment of the present invention, determining the operation strategy for the second target stripe based on the changed state may include the following operations: in response to determining that the changed state of the second target stripe is a used state, re-traversing the to-be-marked bitmap to perform the target operation on the data blocks stored in the second target stripe, and marking the execution state of the second target stripe in the to-be-marked bitmap as executed, generating a marking bitmap; and sending information for synchronously updating the data state of the second target stripe to the second disk controller.

[0096] Figure 7A A schematic diagram showing changes in a to-be-marked bitmap and an initialization bitmap when a use state of a single disk controller changes during execution of a target operation task according to an embodiment of the present invention is shown.

[0097] like Figure 7A As shown, the difference between the embodiment 700A and the embodiment 500 is that the use state of the second target strip is changed during the task execution, that is, the use state of the second target strip (the gray area in the figure) is changed from an invalid area to a valid area.

[0098] In the to-be-marked bitmap 713A, since the stripe belongs to an invalid area before the change, the operation on the stripe is skipped during the task execution. After the change, the to-be-marked bitmap needs to be traversed again to perform the target operation on the data block stored in the second target stripe. When the task execution is completed, the mark of the stripe in the mark bitmap 714A changes from "1" to "0".

[0099] At this time, the mark of the stripe needs to be changed from "0" to "1" in the initialization bitmap to obtain an updated initialization bitmap 721A, indicating that the stripe has been changed from an invalid area to a valid area due to user operation, and therefore, an initialization operation needs to be performed on the stripe to ensure the verification consistency of the disk array.

[0100] Finally, the mark bitmap 714A and the initialization bitmap 721A are ORed according to the stripe position to generate the target initialization bitmap 722A. It can be seen from the target initialization bitmap 722A that the stripe for the changed area is still marked as "1", which realizes that the initialization operation can still be accurately and targetedly performed without the need for each disk controller to synchronously update the metadata of the initialization bitmap during task execution, thereby ensuring the verification consistency of the disk array.

[0101] When it is determined that the changed state of the second target stripe is an unused state, the to-be-marked bitmap is traversed again to skip the target operation on the second target stripe.

[0102] In some embodiments, the state of the second target strip before the change is the used state and belongs to the valid area. If the change operation of the used state occurs before the target operation is performed on the second target strip, then in the bitmap to be marked, since the initial state of the second target strip is "1", after it is changed to the invalid area, the operation on the second target strip can be directly skipped without updating the bitmap to be marked. If the change operation of the used state occurs after the target operation is performed on the second target strip, since the execution state of the second target strip has been changed from "1" to "0" at this time, therefore, when traversing again, the second target strip can also be directly skipped without updating the bitmap to be marked.

[0103] According to an embodiment of the present invention, when the state of the second target strip after the change is the unused state belonging to the invalid area, the operation on the second target strip is directly skipped without re-updating the marked bitmap, thereby reducing the number of operations on the invalid area and the number of synchronizations of metadata between disk controllers.

[0104] According to an embodiment of the present invention, the state change operation may be an attribution state change operation. According to the changed state, determining the operation strategy for the second target strip may include the following operations: in response to determining that the state of the second target strip after the change belongs to the second disk controller, changing the attribution relationship in the bitmap to be marked so that the second disk controller determines the operation to be performed on the second target strip according to the changed state.

[0105] Figure 7B The schematic diagram of the changes in the bitmap to be marked and the initialized bitmap when the attribution state of a single disk controller changes during the execution of a target operation task according to an embodiment of the present invention is shown.

[0106] As Figure 7B shown, the difference between this embodiment 700B and embodiment 700A is that the strip corresponding to the gray area belonged to disk controller Dc 1 before the change and belongs to disk controller Dc 0 after the change. Therefore, since before the change, this strip belonged to disk controller Dc 1 , and disk controller Dc 1 is used to synchronize the metadata of disk controller Dc 0 . Therefore, in the bitmap to be marked 713B of disk controller Dc 0 , the initial mark of this strip is "1". When this strip is a valid area, the target operation is directly performed on this strip to generate the marked bitmap 714B, and the mark of this strip in the marked bitmap 714B is "0". When this strip is an invalid area, this strip can be directly skipped.

[0107] At this time, in the initialization bitmap, the flag of this stripe needs to be changed from "0" to "1" to obtain the updated initialization bitmap 721B. This indicates that due to user operations, this stripe has changed from an invalid area to a valid area. Therefore, an initialization operation needs to be performed on this stripe to ensure the parity consistency of the disk array.

[0108] Finally, the flag bitmap 714B and the initialization bitmap 721B are ORed according to the stripe position to generate the target initialization bitmap 722B. It can be seen from the target initialization bitmap 722B that the stripes in the changed area are still marked as "1", achieving the ability to accurately perform targeted initialization operations during the task execution without the need for each disk controller to synchronously update the metadata of the initialization bitmap, ensuring the parity consistency of the disk array.

[0109] Figure 8 Shows a time quantization schematic diagram for asynchronously completing the information synchronization of each disk controller during the execution of the target operation task.

[0110] Such as Figure 8 shown, in related example 800, during the data reconstruction tasks executed by each disk controller, although there is no need to perform data reconstruction operations on the areas that do not need to be reconstructed in the invalid area, initialization operations still need to be performed, and the initialization flags are synchronized among the disk controllers.

[0111] For example: for disk controller Dc 0 , the white area represents the area that needs to be reconstructed in the valid area, the light gray area represents the area that does not need to be reconstructed in the invalid area, and the dark gray represents the area that needs to be initialized obtained by converting the reconstructed area through stripe identification.

[0112] When disk controller Dc 0 performs metadata synchronization with disk controller Dc 1 , not only the synchronization of the reconstruction flags is required, but also the synchronization of the initialization flags.

[0113] Similarly, when disk controller Dc 1 performs metadata synchronization with disk controller Dc 2 , it is also necessary to synchronize both the reconstruction flags in the valid area and the initialization flags in the invalid area.

[0114] Therefore, when asynchronously completing metadata synchronization, the required time quantization can be schematically represented as the sum of the lengths of the area that needs to be reconstructed in the valid area, the area that does not need to be reconstructed in the invalid area, and the area that needs to be initialized.

[0115] Figure 9It shows a time quantization schematic diagram of asynchronously completing the information synchronization of each disk controller during the execution of the target operation task in an embodiment of the present invention.

[0116] As Figure 9 shown, in this embodiment 900, each disk controller only synchronizes the reconstruction marks to the backup disk controller for the areas that need to be reconstructed (white areas) in the valid area of attribution. For the areas that do not need to be reconstructed in the invalid area, neither the reconstruction completion mark is marked, nor the reconstruction mark and the initialization mark are synchronized to the backup disk controller.

[0117] To meet the check consistency of the reconstructed areas of the disk array, it is only necessary to update the initialization bitmap once after each disk controller completes the reconstruction operation. Thereby reducing the number of synchronizations of the metadata between each disk controller.

[0118] As Figure 9 shown, regardless of whether there are state change operations during the task execution, the update of the initialization bitmap does not need to occupy the asynchronous completion duration for synchronizing the metadata.

[0119] Therefore, when asynchronously completing the metadata synchronization, the required duration quantization can be schematically shown as the length of the areas that need to be reconstructed in the valid area of attribution.

[0120] After comparison Figures 8 - 9 with the asynchronous completion duration quantization schematic diagram in [reference], it can be seen that the method provided by the embodiment of the present invention can, while ensuring the data correctness and the reliability of fault recovery during the interaction between the read / write operations of the user host input / output and the reconstruction task, reduce the communication times between each disk controller, improve the completion rate of the reconstruction task, and reduce the consumption of communication resources, and increase the stability of the communication channel interaction between each disk controller.

[0121] During the task execution, a certain disk controller may fail. To ensure the stability of the data stored in the disk array, the above method may further include the following operations: in response to detecting that the first disk controller fails, reorganizing the data backup relationship between the remaining disk controllers in the disk array; and based on the reorganized data backup relationship, performing the information synchronization operation between each disk controller.

[0122] In some embodiments, reorganizing the data backup relationship between the remaining disk controllers among multiple disk controllers may include the following operations: based on the initial data backup relationship, determining a second disk controller and a third disk controller related to the first disk controller; wherein, the second disk controller is used to back up the data of the first disk controller; the first disk controller is used to back up the data of the third disk controller; and by determining that the second disk controller is the disk controller for backing up the data of the third disk controller, obtaining the reorganized data backup relationship.

[0123] Figure 10 Shows a schematic diagram of the reorganization of the backup relationships of each disk controller according to an embodiment of the present invention.

[0124] As Figure 10 shown, in this embodiment 1000, the initial data backup relationships of each disk controller may include: Disk controller Dc 1 102 is used to back up the metadata of disk controller Dc 0 101. Disk controller Dc 2 103 is used to back up the metadata of disk controller Dc 1 102. Disk controller Dc 3 104 is used to back up the metadata of disk controller Dc 2 103. Disk controller Dc 0 101 is used to back up the metadata of disk controller Dc 3 104.

[0125] When disk controller Dc 0 101 fails, based on the above initial data backup relationships, the disk controllers Dc 0 102 and disk controller Dc 1 104 related to disk controller Dc 3 101 can be determined.

[0126] Then, disk controller Dc 1 102 takes over the business of disk controller Dc 0 101, and the reorganized data backup relationships may include: Disk controller Dc 2 103 is used to back up the metadata of disk controller Dc 1 102, disk controller Dc 3 104 is used to back up the metadata of disk controller Dc2103, disk controller Dc 1 102 is used to back up the metadata of disk controller Dc 3 104.

[0127] Since the metadata in disk controller Dc 1 102 is missing the metadata in disk controller Dc 3 104, therefore, the above method further includes: copying the information in the third disk controller to the second disk controller, merging the information in the third disk controller with the information in the second disk controller; based on the merged information, performing information synchronization operations among the disk controllers according to the reorganized data backup relationships.

[0128] For example: Disk controller Dc 3Copy the metadata in 104 to the disk controller Dc 1 in 102, and merge the disk controller Dc 3 104 and the disk controller Dc 1 metadata in 102, so that for the merged information, according to the reorganized data backup relationship, perform the information synchronization operation between each disk controller.

[0129] According to an embodiment of the present invention, when a disk controller failure occurs during the execution of a task, by reorganizing the data backup relationship between each disk controller, the stability of the stored data in the disk array is further improved.

[0130] Figure 11 The block diagram of an electronic device suitable for implementing the information synchronization method according to an embodiment of the present invention is shown.

[0131] As Figure 11 shown, the electronic device 1100 according to an embodiment of the present invention includes a processor 1101, which can perform various appropriate actions and processes according to the program stored in the read-only memory (ROM) 1102 or the program loaded from the storage section 1108 into the random access memory (RAM) 1103. The processor 1101 can include, for example, a general microprocessor (such as a CPU), an instruction set processor, and / or a related chipset, and / or a dedicated microprocessor (such as an application specific integrated circuit (ASIC)), etc. The processor 1101 can also include on-board memory for caching purposes. The processor 1101 can include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present invention.

[0132] In the RAM 1103, various programs and data required for the operation of the electronic device 1100 are stored. The processor 1101, the ROM 1102, and the RAM 1103 are connected to each other through a bus 1104. The processor 1101 performs various operations of the method flow according to an embodiment of the present invention by executing the programs in the ROM 1102 and / or the RAM 1103. It should be noted that the program can also be stored in one or more memories other than the ROM 1102 and the RAM 1103. The processor 1101 can also perform various operations of the method flow according to an embodiment of the present invention by executing the programs stored in the one or more memories.

[0133] According to an embodiment of the present invention, the electronic device 1100 may further include an input / output (I / O) interface 1105, and the input / output (I / O) interface 1105 is also connected to the bus 1104. The electronic device 1100 may further include one or more of the following components connected to the input / output (I / O) interface 1105: an input portion 1106 including a keyboard, a mouse, etc.; an output portion 1107 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc. and a speaker, etc.; a storage portion 1108 including a hard disk, etc.; and a communication portion 1109 including a network interface card such as a LAN card, a modem, etc. The communication portion 1109 performs communication processing via a network such as the Internet. The drive 1110 is also connected to the input / output (I / O) interface 1105 as needed. A removable medium 1111, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 1110 as needed so that a computer program read from it can be installed into the storage portion 1108 as needed.

[0134] The present invention also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or may exist separately without being assembled into the device / apparatus / system. The above computer-readable storage medium carries one or more programs, and when the above one or more programs are executed, the method according to the embodiments of the present invention is implemented.

[0135] According to an embodiment of the present invention, the computer-readable storage medium may be a non-volatile computer-readable storage medium, for example, it may include but is not limited to: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present invention, the computer-readable storage medium may be any tangible medium that contains or stores a program, and this program can be used by or in combination with an instruction execution system, device, or apparatus. For example, according to an embodiment of the present invention, the computer-readable storage medium may include the ROM 1102 and / or the RAM 1103 described above and / or one or more memories other than the ROM 1102 and the RAM 1103.

[0136] An embodiment of the present invention further includes a computer program product, which includes a computer program, and the computer program contains program codes for executing the method shown in the flowchart. When the computer program product runs in a computer system, the program codes are used to cause the computer system to implement the method provided by the embodiments of the present invention.

[0137] When the computer program is executed by the processor 1101, the above functions defined in the system / apparatus of the embodiments of the present invention are executed. According to the embodiments of the present invention, the above-described systems, apparatuses, modules, units, etc. can be implemented by computer program modules.

[0138] In one embodiment, the computer program can rely on tangible storage media such as optical storage devices, magnetic storage devices, etc. In another embodiment, the computer program can also be transmitted and distributed in the form of signals on a network medium, and be downloaded and installed through the communication part 1109, and / or be installed from the removable medium 1111. The program code included in the computer program can be transmitted by any suitable network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0139] In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 1109, and / or be installed from the removable medium 1111. When the computer program is executed by the processor 1101, the above functions defined in the system of the embodiments of the present invention are executed. According to the embodiments of the present invention, the above-described systems, devices, apparatuses, modules, units, etc. can be implemented by computer program modules.

[0140] According to the embodiments of the present invention, the program code for executing the computer program provided by the embodiments of the present invention can be written in any combination of one or more programming languages. Specifically, these computing programs can be implemented using high-level procedural and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages include but are not limited to, such as Java, C++, python, the "C" language or similar programming languages. The program code can be executed entirely on the user computing device, partially on the user device, partially on a remote computing device, or entirely on a remote computing device or server. In the case of a remote computing device, the remote computing device can be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computing device (for example, by using an Internet service provider to connect through the Internet).

[0141] The flowcharts and block diagrams in the accompanying drawings illustrate the possible architectures, functions, and operations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagram may represent a module, a segment of a program, or a portion of code that contains one or more executable instructions for implementing a specified logical function. It should also be noted that, in some alternative implementations, the functions noted in the blocks may occur in an order different from that noted in the accompanying drawings. For example, two consecutive blocks shown may actually be executed substantially in parallel, or they may sometimes be executed in the reverse order, depending on the functions involved. It should also be noted that each block in the block diagram or flowchart, and combinations of blocks in the block diagram or flowchart, may be implemented by a dedicated hardware-based system that performs the specified functions or operations, or by a combination of dedicated hardware and computer instructions.

[0142] Those skilled in the art will appreciate that the features described in the various embodiments of the present invention may be combined and / or combined in various ways, even if such combinations or combinations are not explicitly described in the present invention. In particular, without departing from the spirit and teachings of the present invention, the features described in the various embodiments of the present invention may be combined and / or combined in various ways. All such combinations and / or combinations fall within the scope of the present invention.

[0143] The embodiments of the present invention have been described above. However, these embodiments are for illustrative purposes only and are not intended to limit the scope of the present invention. Although the embodiments have been described separately above, this does not mean that the measures in the various embodiments cannot be used advantageously in combination. Without departing from the scope of the present invention, those skilled in the art can make various substitutions and modifications, and all such substitutions and modifications should fall within the scope of the present invention.

Claims

1. An information synchronization method, characterized in that: Applied to a disk array, the disk array includes a first disk controller and a second disk controller; the method includes: Acquire an execution status to-be-marked bitmap for indicating a target operation performed on a data block stored in a plurality of stripes in a disk array and an initialization bitmap for indicating whether an initialization operation needs to be performed on the data block; In the case where it is determined that a first target stripe among the multiple stripes is a stripe that is managed by the first disk controller and is in use, a marking bitmap is generated by performing a target operation on a data block stored in the first target stripe and marking the execution status of the first target stripe in the to-be-marked bitmap as executed; and information for synchronously updating the execution status of the first target stripe is sent to the second disk controller; In the case where it is determined that the first target stripe is a stripe that is managed by the first disk controller and is in an unused state, the target operation is not performed on the first target stripe, and execution status information of the target operation and execution status information of the initialization operation for synchronously updating the first target stripe are not sent to the second disk controller; In response to determining that each disk controller has performed the target operation, based on the identification mapping relationship of each stripe, the mark bitmap of each disk controller is processed to obtain a target bitmap; Processing the target bitmap and the initialization bitmap to generate a target initialization bitmap; and An initialization operation is performed based on the target initialization bitmap to achieve information synchronization of each disk controller.

2. The method according to claim 1, characterized in that The target operation includes a data reconstruction operation; the to-be-marked bitmap indicates the execution status of the data reconstruction operation performed on the data blocks stored in each stripe associated with the failed disk in the disk array; The identifier mapping relationship indicates the mapping between the arrangement order identifier of each stripe and the row / column identifier of each stripe in the disk array, and the position of each stripe in the target bitmap corresponds to the position of each stripe in the initialization bitmap.

3. The method according to claim 1, characterized in that The processing of the target bitmap and the initialization bitmap to generate the target initialization bitmap includes: According to the position correspondence between the target bitmap and each stripe in the initialization bitmap, an OR operation is performed on the data status of each stripe to generate the target initialization bitmap.

4. The method according to claim 1, characterized in that: The process of processing the mark bitmap of each disk controller based on the identification mapping relationship of each stripe to obtain the target bitmap includes: Reading a first position identifier of each stripe from a mark bitmap of each disk controller; the first position identifier indicates a row or column of each stripe in the disk array; Based on the identification mapping relationship of each stripe, determining the second position identifier of each stripe in the initialization bitmap according to each first position identifier; and Based on each of the second position identifiers, the execution status information indicated by each of the marking bitmaps is marked to generate the target bitmap.

5. The method according to claim 4, characterized in that The determining, based on the identification mapping relationship of each stripe and according to each first position identifier, the second position identifier of each stripe in the initialization bitmap includes: Based on the identification mapping relationship of each stripe, determining the arrangement order identification of each stripe in the disk array according to each first position identification; and The arrangement order identifier is determined as the second position identifier.

6. The method according to claim 1, characterized in that The method further comprises: In response to detecting a state change operation performed on a second target stripe, determining an operation strategy for the second target stripe according to the changed state; Marking the second target stripe in the initialization bitmap as requiring an initialization operation to be performed, generating an updated initialization bitmap, wherein the second target stripe belongs to the first disk controller; and In response to determining that each disk controller has completed the target operation, the mark bitmap of each disk controller and the updated initialization bitmap are processed to generate a second target initialization bitmap.

7. The method according to claim 6, characterized in that The state change operation includes: using the state change operation; and determining the operation strategy for the second target stripe according to the changed state includes: In response to determining that the changed state of the second target stripe is in use, re-traversing the to-be-marked bitmap to perform a target operation on the data block stored in the second target stripe, and marking the execution state of the second target stripe in the to-be-marked bitmap as executed, thereby generating the marking bitmap; and Information for synchronously updating the data status of the second target stripe is sent to the second disk controller.

8. The method according to claim 6, characterized in that The determining, according to the changed state, an operation strategy for the second target stripe includes: In response to determining that the changed state of the second target stripe is an unused state, the to-be-marked bitmap is re-traversed to skip the target operation for the second target stripe.

9. The method according to claim 6, characterized in that The state change operation includes: an attribution state change operation; and determining an operation strategy for the second target stripe according to the changed state includes: In response to determining that the changed state of the second target stripe belongs to the second disk controller, the ownership relationship in the to-be-marked bitmap is changed so that the second disk controller determines the operation to be performed on the second target stripe according to the changed state.

10. The method according to any one of claims 1 to 9, characterized in that: The method further comprises: In response to detecting that the first disk controller has failed, reorganizing the data backup relationship between the remaining disk controllers in the disk array; and Based on the reorganized data backup relationship, information synchronization operations are performed between the disk controllers.

11. The method according to claim 10, characterized in that The reorganizing the data backup relationship between the remaining disk controllers among the plurality of disk controllers comprises: Based on the initial data backup relationship, determining a second disk controller and a third disk controller related to the first disk controller; wherein the second disk controller is used to back up data of the first disk controller; and the first disk controller is used to back up data of the third disk controller; and The reorganized data backup relationship is obtained by determining that the second disk controller is a disk controller used to back up data of the third disk controller.

12. The method according to claim 11, characterized in that The method further comprises: Merging the information in the third disk controller with the information in the second disk controller by copying the information in the third disk controller to the second disk controller; and Based on the merged information, and in accordance with the reorganized data backup relationship, information synchronization operations are performed between the disk controllers.

13. An electronic device, comprising: one or more processors; a memory for storing one or more computer programs, It is characterized in that the one or more processors execute the one or more computer programs to implement the steps of the method according to any one of claims 1 to 12.

14. A computer-readable storage medium having a computer program or instruction stored thereon, characterized in that: When the computer program or instruction is executed by a processor, the steps of the method according to any one of claims 1 to 12 are implemented.

15. A computer program product, comprising a computer program or instructions, which, when executed by a processor, implement the steps of the method according to any one of claims 1 to 12.

Images