A method, device and equipment for saving RAID card configuration data and readable medium

Abstract

The application provides a RAID card configuration data storage method, device, equipment and readable medium, the method comprises the following steps: adding a DDF_VERSION field in a DDF Header of a DDF configuration structure of a RAID card; in response to updating the configuration data of the RAID card, updating the value in the DDF_VERSION field of the corresponding hard disk based on the update condition of the configuration data; in response to reading the DDF configuration data, judging whether the values in the DDF_VERSION fields of each hard disk are consistent; in response to the values in the DDF_VERSION fields of the hard disks being inconsistent, reading the DDF configuration data of the hard disk corresponding to the value in the largest DDF_VERSION field. Through the use of the scheme of the application, complete and accurate configuration data can be read in the case that the configuration data of the hard disks is inconsistent.

Description

Technical Field

[0001] This invention relates to the field of computers, and more specifically to a method, apparatus, device, and readable medium for storing RAID card configuration data. Background Technology

[0002] In the era of massive storage, the demand for storage capacity is increasing, and the importance of data is constantly rising. Therefore, users are demanding higher reliability and availability from their data. RAID (Rapid Array of Independent Disks) cards, based on disk array technology, can better help solve these problems. Therefore, the configuration data within a RAID card is particularly important.<SNIA_DDF_Technical_Position_v2.0> The DDF (Data Foundation Function) standard describes that the RAID group configuration data in a RAID card is stored in the DDF area of ​​each hard drive connected to the RAID card controller. This ensures more reliable storage of the RAID card's configuration data. When a RAID card fails and is replaced with a new one, the new RAID card can recover the original normal user data configuration based on the configuration data stored in the DDF area of ​​each hard drive, and continue to serve the user.

[0003] However, because the configuration data is stored on all hard drives connected to the RAID card controller, during the storage process, some hard drives may experience I / O errors or other issues, resulting in inconsistent configuration data. This leads to situations where some hard drives contain the correct and up-to-date configuration data, while others have failed to update. During recovery, it's impossible to determine which hard drive stored the most up-to-date and accurate configuration. Therefore, a secure and reliable method is needed to store the RAID card configuration data. Summary of the Invention

[0004] In view of this, the purpose of this invention is to provide a method, apparatus, device and readable medium for saving RAID card configuration data. By using the technical solution of this invention, complete and accurate configuration data can be read even when the configuration data of the hard drive is inconsistent.

[0005] To achieve the above objectives, one aspect of the present invention provides a method for saving RAID card configuration data, comprising the following steps:

[0006] Add the DDF_VERSION field to the DDF Header of the DDF configuration structure of the RAID card;

[0007] In response to updates to the RAID card's configuration data, the value in the DDF_VERSION field of the corresponding hard drive is updated based on the updated configuration data.

[0008] In response to reading DDF configuration data, determine whether the value in the DDF_VERSION field is consistent across each hard drive;

[0009] In response to inconsistencies in the DDF_VERSION field values ​​on the hard drive, the DDF configuration data corresponding to the hard drive with the largest DDF_VERSION field value is read.

[0010] According to one embodiment of the present invention, the DDF_VERSION field is 8 bytes in size, wherein the first byte indicates whether the DDF configuration update was successful or failed, the second to fourth bytes indicate the content of the DDF configuration update, and the fifth to eighth bytes indicate the count of successful DDF configuration updates.

[0011] According to one embodiment of the present invention, updating the value in the DDF_VERSION field of the corresponding hard disk based on the update status of configuration data includes:

[0012] In response to a successful DDF configuration update, modify the content of each byte in the DDF_VERSION field;

[0013] In response to a DDF configuration update failure, modify the content of the first byte of the DDF_VERSION field.

[0014] According to one embodiment of the present invention, in response to reading DDF configuration data, determining whether the value in the DDF_VERSION field of each hard disk is consistent includes:

[0015] In response to reading DDF configuration data, compare the counts in bytes 5-8 of the DDF_VERSION field in each hard disk;

[0016] In response to identical counts, it is determined that the value in the DDF_VERSION field is consistent across all hard drives.

[0017] In response to the different counts, it was determined that the value in the DDF_VERSION field was inconsistent across each hard drive.

[0018] In another aspect, embodiments of the present invention also provide an apparatus for storing RAID card configuration data, the apparatus comprising:

[0019] Add a module that is configured to add a DDF_VERSION field to the DDF Header of the DDF configuration structure of the RAID card;

[0020] The update module is configured to respond to updates to the RAID card's configuration data and update the value in the DDF_VERSION field of the corresponding hard drive based on the updated configuration data.

[0021] The judgment module is configured to read DDF configuration data and determine whether the value in the DDF_VERSION field of each hard disk is consistent.

[0022] The read module is configured to read the DDF configuration data from the hard drive corresponding to the largest value in the DDF_VERSION field when there is a discrepancy in the values ​​in the DDF_VERSION field.

[0023] According to one embodiment of the present invention, the DDF_VERSION field is 8 bytes in size, wherein the first byte indicates whether the DDF configuration update was successful or failed, the second to fourth bytes indicate the content of the DDF configuration update, and the fifth to eighth bytes indicate the count of successful DDF configuration updates.

[0024] According to one embodiment of the present invention, the update module is further configured to:

[0025] In response to a successful DDF configuration update, modify the content of each byte in the DDF_VERSION field;

[0026] In response to a DDF configuration update failure, modify the content of the first byte of the DDF_VERSION field.

[0027] According to one embodiment of the present invention, the determining module is further configured to:

[0028] In response to reading DDF configuration data, compare the counts in bytes 5-8 of the DDF_VERSION field in each hard disk;

[0029] In response to identical counts, it is determined that the value in the DDF_VERSION field is consistent across all hard drives.

[0030] In response to the different counts, it was determined that the value in the DDF_VERSION field was inconsistent across each hard drive.

[0031] Another aspect of the embodiments of the present invention also provides a computer device, the computer device comprising:

[0032] At least one processor; and

[0033] The memory stores computer instructions that can be executed by a processor, which, when executed by the processor, implement the steps of any of the methods described above.

[0034] In another aspect, embodiments of the present invention also provide a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of any of the above methods.

[0035] The present invention has the following beneficial technical effects: The method for saving RAID card configuration data provided in the embodiments of the present invention adds a DDF_VERSION field to the DDF Header of the DDF configuration structure of the RAID card; updates the value in the DDF_VERSION field of the corresponding hard drive based on the update status of the configuration data in response to updating the configuration data of the RAID card; determines whether the value in the DDF_VERSION field of each hard drive is consistent in response to reading the DDF configuration data; and reads the DDF configuration data of the hard drive corresponding to the largest value in the DDF_VERSION field in response to the inconsistency of the DDF_VERSION field in the hard drives. This technical solution enables the reading of complete and accurate configuration data even when the configuration data of the hard drives is inconsistent. Attached Figure Description

[0036] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other embodiments can be obtained based on these drawings without creative effort.

[0037] Figure 1 A schematic flowchart illustrating a method for configuring data storage on a RAID card according to an embodiment of the present invention;

[0038] Figure 2 This is a schematic diagram of the DDF_VERSION field according to an embodiment of the present invention;

[0039] Figure 3 A schematic diagram of an apparatus for configuring data storage for a RAID card according to an embodiment of the present invention;

[0040] Figure 4 This is a schematic diagram of a computer device according to an embodiment of the present invention;

[0041] Figure 5 This is a schematic diagram of a computer-readable storage medium according to an embodiment of the present invention. Detailed Implementation

[0042] To make the objectives, technical solutions, and advantages of the present invention clearer, the embodiments of the present invention will be further described in detail below with reference to specific examples and the accompanying drawings.

[0043] Based on the above objectives, a first aspect of the embodiments of the present invention provides an embodiment of a method for storing RAID card configuration data. Figure 1 The diagram shown is a schematic flowchart of the method.

[0044] like Figure 1 As shown, the method may include the following steps:

[0045] S1 adds a DDF_VERSION field to the DDF Header of the RAID card's DDF configuration structure. The DDF Header contains information related to other sections and the overall configuration. The DDF_VERSION field is designed to be 8 bytes in size, where the first byte indicates whether the DDF configuration update was successful or failed, bytes 2-4 represent the content of the DDF configuration update, and bytes 5-8 represent a count of successful DDF configuration updates. The value of DDF_VERSION is updated whenever a write operation is performed on the DDF structure to update the RAID card's configuration data.

[0046] S2 responds to the updated RAID card configuration data by updating the value in the DDF_VERSION field of the corresponding hard drive based on the updated configuration data. If the hard drive's DDF configuration update is successful, it modifies the content of each byte in the DDF_VERSION field; if the DDF configuration update fails, it modifies the content of the first byte in the DDF_VERSION field to indicate that the DDF configuration update failed.

[0047] S3 responds to reading DDF configuration data by determining whether the value in the DDF_VERSION field is consistent across all hard drives. When DDF configuration data needs to be read, the counts in bytes 5-8 of the DDF_VERSION field on each hard drive are compared. If the counts are the same, it is determined that the value in the DDF_VERSION field on each hard drive is consistent, and the DDF configuration data on the hard drives is up-to-date and complete. If the counts are different, it is determined that the value in the DDF_VERSION field on each hard drive is inconsistent.

[0048] In response to inconsistencies in the DDF_VERSION field values ​​on the hard drives, S4 reads the DDF configuration data corresponding to the hard drive with the largest DDF_VERSION value. If the DDF_VERSION values ​​on the hard drives are different, it indicates that the configuration data on the hard drives is inconsistent. The hard drive with the larger DDF_VERSION value indicates that the configuration data stored on that drive is up-to-date and complete; otherwise, it indicates that the configuration data on that drive is unavailable. Users can obtain usable configuration data even when there is inconsistency in the configuration data.

[0049] By using the technical solution of the present invention, complete and accurate configuration data can be read even when the configuration data of the hard disk is inconsistent.

[0050] In a preferred embodiment of the present invention, the DDF_VERSION field is 8 bytes in size, where the first byte indicates whether the DDF configuration update was successful or failed, bytes 2-4 indicate the content of the DDF configuration update, and bytes 5-8 indicate the count of successful DDF configuration updates. Figure 2 As shown, byte 1 indicates that the field is set when the entire DDF configuration update is successful. The size of data written to the hard drive is in page (4096 bytes) granularity. When the DDF structure size is larger than one page, if the previous page is written successfully while the next page fails, atomicity cannot be guaranteed during the write process, leading to incomplete configuration data. Therefore, this field is only set after the entire DDF structure has undergone atomic operations to indicate a successful DDF configuration update. This field needs to be reset before writing. Bytes 2-4 indicate that the currently updated configuration is a specific section within the DDF structure. This field clearly shows which parts of the configuration have been updated. This field also needs to be reset before writing. Bytes 5-8 represent a count of the updated configuration. Each time the configuration is updated, this field is incremented by 1. If the value of this field on a certain hard drive is the largest compared to the values ​​on other hard drives, it means that the DDF structure on that hard drive has the latest configuration. To prevent overflow of this field, the following algorithm is used for comparison:

[0051] #define write_last(value1,value2)\

[0052] (typecheck(unsigned int,value1)&&\

[0053] typecheck(unsigned int,value2)&&\

[0054] ((int)(value2)-(int)(value1)<0))

[0055] When write_last(value1,value2) is true, it means that value1 represents the latest DDF configuration data; otherwise, it means that value2 represents the latest DDF configuration data.

[0056] In a preferred embodiment of the present invention, updating the value in the DDF_VERSION field of the corresponding hard disk based on the update status of the configuration data includes:

[0057] In response to a successful DDF configuration update, modify the content of each byte in the DDF_VERSION field;

[0058] In response to a DDF configuration update failure, modify the content of the first byte of the DDF_VERSION field.

[0059] In a preferred embodiment of the present invention, determining whether the value of the DDF_VERSION field in each hard disk is consistent in response to reading DDF configuration data includes:

[0060] In response to reading DDF configuration data, compare the counts in bytes 5-8 of the DDF_VERSION field in each hard disk;

[0061] In response to identical counts, it is determined that the value in the DDF_VERSION field is consistent across all hard drives.

[0062] In response to the different counts, it was determined that the value in the DDF_VERSION field was inconsistent across each hard drive.

[0063] This invention improves efficiency and reliability by reading and writing RAID card configuration data in a page-aligned manner. By comparing the DDF_VERSION field, it can ensure that complete and accurate configuration data can be read even when the configuration data may be inconsistent.

[0064] It should be noted that those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. The storage medium can be a magnetic disk, optical disk, read-only memory (ROM), or random access memory (RAM), etc. The embodiments of the computer program described above can achieve the same or similar effects as any of the corresponding foregoing method embodiments.

[0065] Furthermore, the method disclosed in the embodiments of the present invention can also be implemented as a computer program executed by a CPU, which may be stored in a computer-readable storage medium. When the computer program is executed by the CPU, it performs the functions defined in the method disclosed in the embodiments of the present invention.

[0066] Based on the above objectives, a second aspect of the embodiments of the present invention provides an apparatus for storing RAID card configuration data, such as... Figure 3 As shown, the device 200 includes:

[0067] Add a module that is configured to add a DDF_VERSION field to the DDF Header of the DDF configuration structure of the RAID card;

[0068] The update module is configured to respond to updates to the RAID card's configuration data and update the value in the DDF_VERSION field of the corresponding hard drive based on the updated configuration data.

[0069] The judgment module is configured to read DDF configuration data and determine whether the value in the DDF_VERSION field of each hard disk is consistent.

[0070] The read module is configured to read the DDF configuration data from the hard drive corresponding to the largest value in the DDF_VERSION field when there is a discrepancy in the values ​​in the DDF_VERSION field.

[0071] In a preferred embodiment of the present invention, the DDF_VERSION field is 8 bytes in size, wherein the first byte indicates whether the DDF configuration update was successful or failed, the second to fourth bytes indicate the content of the DDF configuration update, and the fifth to eighth bytes indicate the count of successful DDF configuration updates.

[0072] In a preferred embodiment of the present invention, the update module is further configured as follows:

[0073] In response to a successful DDF configuration update, modify the content of each byte in the DDF_VERSION field;

[0074] In response to a DDF configuration update failure, modify the content of the first byte of the DDF_VERSION field.

[0075] In a preferred embodiment of the present invention, the determining module is further configured as follows:

[0076] In response to reading DDF configuration data, compare the counts in bytes 5-8 of the DDF_VERSION field in each hard disk;

[0077] In response to identical counts, it is determined that the value in the DDF_VERSION field is consistent across all hard drives.

[0078] In response to the different counts, it was determined that the value in the DDF_VERSION field was inconsistent across each hard drive.

[0079] In view of the above objectives, a third aspect of the present invention provides a computer device. Figure 4 The diagram shown is a schematic representation of an embodiment of the computer device provided by the present invention. Figure 4 As shown, embodiments of the present invention include the following apparatus: at least one processor 21; and a memory 22 storing computer instructions 23 executable on the processor, which, when executed by the processor, implement the following method:

[0080] Add the DDF_VERSION field to the DDF Header of the DDF configuration structure of the RAID card;

[0081] In response to updates to the RAID card's configuration data, the value in the DDF_VERSION field of the corresponding hard drive is updated based on the updated configuration data.

[0082] In response to reading DDF configuration data, determine whether the value in the DDF_VERSION field is consistent across each hard drive;

[0083] In response to inconsistencies in the DDF_VERSION field values ​​on the hard drive, the DDF configuration data corresponding to the hard drive with the largest DDF_VERSION field value is read.

[0084] In a preferred embodiment of the present invention, the DDF_VERSION field is 8 bytes in size, wherein the first byte indicates whether the DDF configuration update was successful or failed, the second to fourth bytes indicate the content of the DDF configuration update, and the fifth to eighth bytes indicate the count of successful DDF configuration updates.

[0085] In a preferred embodiment of the present invention, updating the value in the DDF_VERSION field of the corresponding hard disk based on the update status of the configuration data includes:

[0086] In response to a successful DDF configuration update, modify the content of each byte in the DDF_VERSION field;

[0087] In response to a DDF configuration update failure, modify the content of the first byte of the DDF_VERSION field.

[0088] In a preferred embodiment of the present invention, determining whether the value of the DDF_VERSION field in each hard disk is consistent in response to reading DDF configuration data includes:

[0089] In response to reading DDF configuration data, compare the counts in bytes 5-8 of the DDF_VERSION field in each hard disk;

[0090] In response to identical counts, it is determined that the value in the DDF_VERSION field is consistent across all hard drives.

[0091] In response to the different counts, it was determined that the value in the DDF_VERSION field was inconsistent across each hard drive.

[0092] In view of the above objectives, a fourth aspect of the present invention provides a computer-readable storage medium. Figure 5 The diagram shown is a schematic representation of an embodiment of the computer-readable storage medium provided by the present invention. Figure 5As shown, computer-readable storage medium 31 stores a computer program 32 that, when executed by a processor, performs the following methods:

[0093] Add the DDF_VERSION field to the DDF Header of the DDF configuration structure of the RAID card;

[0094] In response to updates to the RAID card's configuration data, the value in the DDF_VERSION field of the corresponding hard drive is updated based on the updated configuration data.

[0095] In response to reading DDF configuration data, determine whether the value in the DDF_VERSION field is consistent across each hard drive;

[0096] In response to inconsistencies in the DDF_VERSION field values ​​on the hard drive, the DDF configuration data corresponding to the hard drive with the largest DDF_VERSION field value is read.

[0097] In a preferred embodiment of the present invention, the DDF_VERSION field is 8 bytes in size, wherein the first byte indicates whether the DDF configuration update was successful or failed, the second to fourth bytes indicate the content of the DDF configuration update, and the fifth to eighth bytes indicate the count of successful DDF configuration updates.

[0098] In a preferred embodiment of the present invention, updating the value in the DDF_VERSION field of the corresponding hard disk based on the update status of the configuration data includes:

[0099] In response to a successful DDF configuration update, modify the content of each byte in the DDF_VERSION field;

[0100] In response to a DDF configuration update failure, modify the content of the first byte of the DDF_VERSION field.

[0101] In a preferred embodiment of the present invention, determining whether the value of the DDF_VERSION field in each hard disk is consistent in response to reading DDF configuration data includes:

[0102] In response to reading DDF configuration data, compare the counts in bytes 5-8 of the DDF_VERSION field in each hard disk;

[0103] In response to identical counts, it is determined that the value in the DDF_VERSION field is consistent across all hard drives.

[0104] In response to the different counts, it was determined that the value in the DDF_VERSION field was inconsistent across each hard drive.

[0105] Furthermore, the method disclosed in the embodiments of the present invention can also be implemented as a computer program executed by a processor, which may be stored in a computer-readable storage medium. When the computer program is executed by the processor, it performs the functions defined in the method disclosed in the embodiments of the present invention.

[0106] Furthermore, the above-described method steps and system units can also be implemented using a controller and a computer-readable storage medium for storing a computer program that enables the controller to perform the functions of the above-described steps or units.

[0107] Those skilled in the art will also understand that the various exemplary logic blocks, modules, circuits, and algorithm steps described in conjunction with the disclosure herein can be implemented as electronic hardware, computer software, or a combination of both. To clearly illustrate this interchangeability between hardware and software, the functionality of various illustrative components, blocks, modules, circuits, and steps has been generally described. Whether this functionality is implemented as software or as hardware depends on the specific application and the design constraints imposed on the system as a whole. Those skilled in the art can implement the functionality in various ways for each specific application, but such implementation decisions should not be construed as departing from the scope of the embodiments disclosed herein.

[0108] In one or more exemplary designs, functionality may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, functionality may be stored as one or more instructions or code on or transmitted via a computer-readable medium. Computer-readable media include computer storage media and communication media, including any medium that facilitates the transfer of a computer program from one location to another. Storage media may be any available medium accessible to a general-purpose or special-purpose computer. By way of example, and not limitation, computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disc storage devices, disk storage devices or other magnetic storage devices, or any other medium that may be used to carry or store the required program code in the form of instructions or data structures and is accessible to a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Furthermore, any connection may be appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the aforementioned coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are all included in the definition of media. As used herein, disks and optical discs include compact discs (CDs), laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs, where disks typically reproduce data magnetically, while optical discs reproduce data optically using lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0109] The above are exemplary embodiments disclosed in this invention. However, it should be noted that various changes and modifications can be made without departing from the scope of the embodiments of this invention as defined by the claims. The functions, steps, and / or actions of the methods according to the disclosed embodiments described herein do not need to be performed in any particular order. Furthermore, although the elements disclosed in the embodiments of this invention may be described or claimed individually, they may be understood as multiple unless explicitly limited to a singular number.

[0110] It should be understood that, as used herein, the singular form “a” is intended to include the plural form as well, unless the context clearly supports an exception. It should also be understood that, as used herein, “and / or” refers to any and all possible combinations of one or more of the associated listed items.

[0111] The embodiment numbers disclosed in the above embodiments of the present invention are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0112] Those skilled in the art will understand that all or part of the steps of the above embodiments can be implemented by hardware or by a program instructing related hardware. The program can be stored in a computer-readable storage medium, such as a read-only memory, a disk, or an optical disk.

[0113] Those skilled in the art should understand that the discussion of any of the above embodiments is merely exemplary and is not intended to imply that the scope of the invention (including the claims) is limited to these examples. Within the framework of the invention, technical features of the above embodiments or different embodiments can be combined, and many other variations of different aspects of the invention exist, which are not provided in the details for the sake of brevity. Therefore, any omissions, modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the invention should be included within the protection scope of the invention.

Claims

1. A method for storing RAID card configuration data, characterized in that, Includes the following steps: Add the DDF_VERSION field to the DDF Header of the DDF configuration structure of the RAID card; In response to updates to the RAID card's configuration data, the value in the DDF_VERSION field of the corresponding hard drive is updated based on the updated configuration data. In response to reading DDF configuration data, determine whether the value in the DDF_VERSION field is consistent across each hard drive; In response to inconsistencies in the DDF_VERSION field values ​​on the hard drive, the DDF configuration data corresponding to the hard drive with the largest DDF_VERSION field value is read. Determining whether the value of the DDF_VERSION field is consistent across all hard drives includes: Compare the counts in bytes 5-8 of the DDF_VERSION field in each hard drive; In response to identical counts, it is determined that the value in the DDF_VERSION field is consistent across all hard drives. The inconsistency in the DDF_VERSION field value is determined in response to the different counts on each hard drive. The DDF_VERSION field is 8 bytes in size. The first byte indicates whether the DDF configuration update was successful or failed. The second to fourth bytes indicate the content of the DDF configuration update. The fifth to eighth bytes indicate the count of successful DDF configuration updates.

2. The method according to claim 1, characterized in that, Updating the value of the DDF_VERSION field of the corresponding hard drive based on the update status of the configuration data includes: In response to a successful DDF configuration update, modify the content of each byte in the DDF_VERSION field; In response to a DDF configuration update failure, modify the content of the first byte of the DDF_VERSION field.

3. A device for storing RAID card configuration data, characterized in that, The device includes: Add a module, which is configured to add a DDF_VERSION field to the DDF Header of the DDF configuration structure of the RAID card; The update module is configured to update the value in the DDF_VERSION field of the corresponding hard drive in response to updating the configuration data of the RAID card. The judgment module is configured to determine whether the value in the DDF_VERSION field of each hard disk is consistent in response to reading DDF configuration data. A reading module, configured to read the DDF configuration data of the hard disk corresponding to the largest value in the DDF_VERSION field in response to inconsistencies in the values ​​in the DDF_VERSION field in the hard disk; The judgment module is further configured to: in response to reading DDF configuration data, compare the counts in bytes 5-8 of the DDF_VERSION field in each hard disk; in response to the same count, determine that the values ​​in the DDF_VERSION field in each hard disk are consistent; in response to different counts, determine that the values ​​in the DDF_VERSION field in each hard disk are inconsistent. The DDF_VERSION field is 8 bytes in size, where the first byte indicates whether the DDF configuration update was successful or failed, the second to fourth bytes indicate the content of the DDF configuration update, and the fifth to eighth bytes indicate the count of successful DDF configuration updates.

4. The apparatus according to claim 3, characterized in that, The update module is also configured to: In response to a successful DDF configuration update, modify the content of each byte in the DDF_VERSION field; In response to a DDF configuration update failure, modify the content of the first byte of the DDF_VERSION field.

5. A computer device, characterized in that, include: At least one processor; as well as A memory storing computer instructions executable on the processor, which, when executed by the processor, implement the steps of the method according to any one of claims 1-2.

6. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1-2.

Images