CN108319527B - Bad track disk detection method and device - Google Patents
Bad track disk detection method and device Download PDFInfo
- Publication number
- CN108319527B CN108319527B CN201711388972.2A CN201711388972A CN108319527B CN 108319527 B CN108319527 B CN 108319527B CN 201711388972 A CN201711388972 A CN 201711388972A CN 108319527 B CN108319527 B CN 108319527B
- Authority
- CN
- China
- Prior art keywords
- tested
- disk
- target disk
- test
- target
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/22—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing
- G06F11/2273—Test methods
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0706—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment
- G06F11/0727—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment in a storage system, e.g. in a DASD or network based storage system
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/22—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing
- G06F11/2205—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing using arrangements specific to the hardware being tested
- G06F11/2221—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing using arrangements specific to the hardware being tested to test input/output devices or peripheral units
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention provides a bad track disk detection method and a bad track disk detection device, which are applied to a distributed storage system, and the technical scheme is as follows: determining target disks to be tested, setting the test type of each target disk to be tested, and configuring a performance parameter threshold value related to the running condition of the target disk to be tested based on the test type of the target disk to be tested; and aiming at each target disk to be tested, initiating a task request to the target disk to be tested according to the test type of the target disk to be tested and a preset frequency so that when the distributed storage system determines that the performance of the target disk to be tested does not meet the performance parameter threshold requirement related to the running condition of the target disk to be tested, the target disk to be tested is determined to be a bad track disk and the target disk to be tested is kicked out from the distributed storage system. The invention can find the bad track disk in time and reduce the resource waste.
Description
Technical Field
The invention relates to the technical field of communication, in particular to a bad track disk detection method and device.
Background
Various problems may arise with long-term use of a disk, with disk "bad tracks" being the most common of them. The disk is an important carrier for storing data, and if a bad track occurs on the disk, the data of the disk is in danger of being lost.
In a distributed storage system, a bad track of a disk can cause data loss and affect the read-write operation of the system on the data, so that the system cannot normally operate. Therefore, it is necessary to detect whether a bad track disk exists in the system in time, but the detection of the bad track disk needs to occupy extra time and manpower, which results in resource waste.
Disclosure of Invention
In view of this, the present invention provides a method and an apparatus for detecting a bad track disk, which can find the bad track disk in time and reduce resource waste.
In order to achieve the purpose, the invention provides the following technical scheme:
a bad track disk detection method is applied to a distributed storage system and comprises the following steps:
determining a target disk to be tested in a distributed storage system;
setting a test type of each target disk to be tested, and configuring a performance parameter threshold value related to the running condition of the target disk to be tested based on the test type of the target disk to be tested;
and aiming at each target disk to be tested, initiating a task request to the target disk to be tested according to the test type of the target disk to be tested and a preset frequency so that when the distributed storage system determines that the performance of the target disk to be tested does not meet the performance parameter threshold requirement related to the running condition of the target disk to be tested, the target disk to be tested is determined to be a bad track disk and the target disk to be tested is kicked out from the distributed storage system.
A bad track disk detection device is applied to a distributed storage system, and comprises: the device comprises a determining unit, a configuration unit and a testing unit;
the determining unit is used for determining a target disk to be tested in the distributed storage system;
the configuration unit is used for setting the test type of each target disk to be tested and configuring a performance parameter threshold value related to the running condition of the target disk to be tested based on the test type of the target disk to be tested;
the testing unit is used for initiating a task request to each target disk to be tested according to the testing type of the target disk to be tested and a preset frequency so that when the distributed storage system determines that the performance of the target disk to be tested does not meet the performance parameter threshold requirement related to the running condition of the target disk to be tested, the target disk to be tested is determined to be a bad track disk and the target disk to be tested is kicked out from the distributed storage system.
According to the technical scheme, the test type setting and the corresponding performance parameter threshold setting are firstly carried out on the target disk to be tested, then the task request is sent to the target disk to be tested based on the test type, so that the distributed storage system judges whether the target disk to be tested is a bad track disk or not according to the comparison between the performance of the disk and the configured performance parameter threshold in the task execution process. By applying the method of the invention, the bad track disk can be found in time, and the resource waste is reduced.
Drawings
FIG. 1 is a flowchart of a bad track disk detection method according to an embodiment of the present invention;
FIG. 2 is a schematic structural diagram of a bad track disk detection apparatus according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the technical solutions of the present invention are described in detail below with reference to the accompanying drawings according to embodiments.
Referring to fig. 1, fig. 1 is a flowchart of a bad track disk detection method according to an embodiment of the present invention, where the method is applied to a distributed storage system, and as shown in fig. 1, the method includes the following steps:
All the disks in the distributed storage system can be tested, or only a part of target disks can be tested, which is determined according to specific requirements.
In practical application, when a disk is read/written, if the response time of the disk is too slow or the number of tasks accumulated on the disk is too large, the bad operation condition of the disk can be indicated, and whether the bad track of the disk exists or not needs to be considered.
In this embodiment, the detection of the bad track of the disk is realized by performing read/write operations on the disk, and the test types include the following: slow disk test, read error test, write error test. Wherein the content of the first and second substances,
the slow disc detection takes the task amount of a magnetic disc and the response time of the magnetic disc as detection objects, the change of the task amount of the magnetic disc and the change of the response time of the magnetic disc of a target magnetic disc to be detected are detected by performing read operation and/or write operation with preset frequency on the target magnetic disc to be detected, and if the task amount of the magnetic disc exceeds a certain threshold value or the response time of the magnetic disc exceeds a certain threshold value, the target magnetic disc to be detected can be regarded as a bad track magnetic disc.
The read error test takes the response time of a disk as a detection object, the change of the response time of the disk of a target disk to be tested is detected by performing read operation with preset frequency on the target disk to be tested, and if the response time of the disk exceeds a certain threshold, the target disk to be tested can be considered as a bad track disk.
The write error test takes the response time of a disk as a detection object, the change of the response time of the disk of a target disk to be tested is detected by performing write operation with a preset frequency on the target disk to be tested, and if the response time of the disk exceeds a certain threshold, the target disk to be tested can be regarded as a bad track disk.
One or more of the three test types can be selected to perform bad track detection on the target disk to be tested. When the bad track detection of any one of the above test types needs to be performed on the target disk to be tested, the test type needs to be enabled first. In step 102, the specific method for setting the test type of the target disk to be tested is as follows: slow disk testing, read error testing, and/or write error testing of the target disk to be tested is enabled.
In addition, in the three detection types, the slow disk test mainly focuses on the change of the task amount of the disk, and the read error test and the write error test mainly focus on the change of the response time of the disk, so that it can be seen that the test types are different, and the performance parameters which need to be set are not completely the same.
In this step 102, configuring a performance parameter threshold related to the running condition of the target disk to be tested based on the test type of the target disk to be tested specifically includes:
when the test type of the target disk to be tested comprises a slow disk test, setting a disk task quantity threshold and a disk response time threshold, and configuring the disk task quantity threshold and the disk response time threshold as performance parameter thresholds related to the running condition of the target disk to be tested;
when the test type of the target disk to be tested comprises a read error test and/or a write error test, setting a disk response time threshold, and configuring the disk response time threshold as a performance parameter threshold related to the running condition of the target disk to be tested.
103, for each target disk to be tested, initiating a task request to the target disk to be tested according to the test type of the target disk to be tested and a preset frequency so that when the distributed storage system determines that the performance of the target disk to be tested does not meet the performance parameter threshold requirement related to the running condition of the target disk to be tested, the target disk to be tested is determined to be a bad track disk and the target disk to be tested is kicked out from the distributed storage system.
In order to perform disk-to-disk failure detection on a target disk to be tested, a frequency needs to be preset, where the frequency is an access frequency to the disk to be tested in the current detection process.
In this embodiment, the task request includes a read request and a write request, and in an actual test process, the read request is sent as the task request or the write request is sent as the task request, and it needs to be determined according to a specific test type, where if the test type is slow disc test, the sent task request may be the read request and/or the write request, if the test type is read error test, the sent task request may only be the read request, and if the test type is write error test, the sent task request may only be the write request.
Therefore, in step 103, the method for initiating a task request to the target disk to be tested according to the test type of the target disk to be tested and the preset frequency specifically includes:
when the test type of the target disk to be tested only comprises a read error test, initiating a read request to the target disk to be tested according to a preset frequency;
when the test type of the target disk to be tested only comprises a write error test, initiating a write request to the target disk to be tested according to a preset frequency;
and when the test type of the target disk to be tested comprises a slow disk test, initiating a read request and/or a write request to the target disk to be tested according to a preset frequency.
Because the test type of the target disk to be tested is enabled, in the process of performing read operation or write operation on the target disk to be tested, the distributed storage system can detect whether the performance of the target disk to be tested meets the performance parameter threshold requirement related to the running condition of the target disk to be tested in real time, and determine whether the target disk to be tested is a bad track disk according to the performance parameter threshold requirement.
In particular, the amount of the solvent to be used,
when the test type of the target disk to be tested only includes a read error test or a write error test, if the distributed storage system determines that the current disk response time of the target disk to be tested is greater than a disk response time threshold configured for the target disk to be tested, it can be determined that the performance of the target disk to be tested does not meet a performance parameter threshold requirement related to the running condition of the target disk to be tested, at this time, the target disk to be tested can be considered as a bad track disk, and the target disk to be tested is kicked out of the distributed storage system.
When the test type of the target to be tested comprises a slow disk test, if the distributed storage system determines that the current disk response time of the target disk to be tested is greater than a disk response time threshold configured for the target disk to be tested, and/or the current disk task amount of the target disk to be tested is greater than a disk task amount threshold configured for the target disk to be tested, the performance of the target disk to be tested can be determined to be not in accordance with a performance parameter threshold requirement related to the running condition of the target disk to be tested, at this moment, the target disk to be tested can be considered to be a bad track disk, and the target disk to be tested is kicked out of the distributed storage system.
After the bad track detection is finished on all target disks to be tested of the distributed storage system, the disks kicked out of the distributed storage system are considered as bad track disks.
The following description of the implementation of the method shown in fig. 1 is given as a specific example:
in a linux system, when bad track detection needs to be performed on a certain disk, the method can be implemented by the following steps:
1. modifying ufs _ meta parameter to realize the test type setting of the disk;
(1) arrangement for slow disc testing
Disk UUID assigned
-disk_write_slow＝true
-disk_read_slow＝true
(2) Setting of write error test
-disk_write_failed＝true
Disk UUID assigned
(3) Setting of read error test
-disk_read_failed＝true
Disk UUID assigned
2. Configuring a performance parameter threshold based on the test type;
and in slow disk test, a disk task amount threshold and a disk response time threshold corresponding to the disk need to be set.
For the write error test and the read error test, a disk response time threshold corresponding to the disk needs to be set.
3. Performing a test procedure
And (3) slow disk test, wherein a read request and/or a write request is required to be sent to the disk according to a preset frequency.
And (4) performing write error test, namely sending a write request to the disk according to a preset frequency.
And in the read error test, a read request is required to be sent to the disk according to a preset frequency.
During the process of performing read operation and/or write operation on the disk by the distributed storage system, the change of the parameters of the disk related to the operation condition is judged, and if the threshold value exceeds the corresponding maximum threshold value (the task amount threshold value of the disk or the response time threshold value of the disk), the disk is determined to be a bad track disk.
The method for detecting a bad track disk according to the embodiment of the present invention is described in detail above, and the present invention further provides a bad track disk detection apparatus, which is described in detail below with reference to fig. 2.
Referring to fig. 2, fig. 2 is a schematic structural diagram of a bad track disk detection apparatus according to an embodiment of the present invention, which is applied to a distributed storage system, and as shown in fig. 2, the apparatus includes: a determining unit 201, a configuration unit 202 and a testing unit 203; wherein the content of the first and second substances,
a determining unit 201, configured to determine a target disk to be tested in a distributed storage system;
a configuration unit 202, configured to set a test type of each target disk to be tested, and configure a performance parameter threshold related to an operating condition of the target disk to be tested based on the test type of the target disk to be tested;
the testing unit 203 is configured to initiate a task request to each target disk to be tested according to the testing type of the target disk to be tested and according to a preset frequency, so that when the distributed storage system determines that the performance of the target disk to be tested does not meet a performance parameter threshold requirement related to the running condition of the target disk to be tested, the target disk to be tested is determined to be a bad track disk, and the target disk to be tested is kicked out from the distributed storage system.
In the device shown in figure 2 of the drawings,
the test types include: slow disk test, read error test, write error test;
the configuration unit 202, when setting the test type of the target disk to be tested, is configured to: slow disk testing, read error testing, and/or write error testing of the target disk to be tested is enabled.
In the device shown in figure 2 of the drawings,
the configuring unit 202, based on the test type of the target disk to be tested, configures a performance parameter threshold related to the running condition of the target disk to be tested, including:
when the test type of the target disk to be tested comprises a slow disk test, setting a disk task quantity threshold and a disk response time threshold, and configuring the disk task quantity threshold and the disk response time threshold as performance parameter thresholds related to the running condition of the target disk to be tested;
when the test type of the target disk to be tested comprises a read error test and/or a write error test, setting a disk response time threshold, and configuring the disk response time threshold as a performance parameter threshold related to the running condition of the target disk to be tested.
In the device shown in figure 2 of the drawings,
when the test type of the target disk to be tested only comprises a read error test or a write error test, if the current disk response time of the target disk to be tested is greater than a disk response time threshold configured for the target disk to be tested, the performance of the target disk to be tested does not meet the performance parameter threshold requirement related to the running condition of the target disk to be tested;
when the test type of the target to be tested comprises a slow disk test, if the current disk response time of the target disk to be tested is larger than a disk response time threshold configured for the target disk to be tested, and/or the current disk task amount of the target disk to be tested is larger than a disk task amount threshold configured for the target disk to be tested, the performance of the target disk to be tested does not meet the performance parameter threshold requirement related to the running condition of the target disk to be tested.
In the device shown in figure 2 of the drawings,
the testing unit 203, when initiating a task request to the target disk to be tested according to the testing type of the target disk to be tested and the preset frequency, is configured to:
when the test type of the target disk to be tested only comprises a read error test, initiating a read request to the target disk to be tested according to a preset frequency;
when the test type of the target disk to be tested only comprises a write error test, initiating a write request to the target disk to be tested according to a preset frequency;
and when the test type of the target disk to be tested comprises a slow disk test, initiating a read request and/or a write request to the target disk to be tested according to a preset frequency.
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents, improvements and the like made within the spirit and principle of the present invention should be included in the scope of the present invention.
Claims (8)
1. A bad track disk detection method is applied to a distributed storage system and is characterized by comprising the following steps:
determining a target disk to be tested in a distributed storage system;
setting a test type of each target disk to be tested, and configuring a performance parameter threshold value related to the running condition of the target disk to be tested based on the test type of the target disk to be tested;
aiming at each target disk to be tested, initiating a task request to the target disk to be tested according to the test type of the target disk to be tested and a preset frequency so that when the distributed storage system determines that the performance of the target disk to be tested does not meet the performance parameter threshold requirement related to the running condition of the target disk to be tested, the target disk to be tested is determined to be a bad track disk and the target disk to be tested is kicked out from the distributed storage system;
wherein the test types include: slow disk test, read error test, write error test;
the method for initiating the task request to the target disk to be tested according to the test type of the target disk to be tested and the preset frequency comprises the following steps:
when the test type of the target disk to be tested only comprises a read error test, initiating a read request to the target disk to be tested according to a preset frequency;
when the test type of the target disk to be tested only comprises a write error test, initiating a write request to the target disk to be tested according to a preset frequency;
and when the test type of the target disk to be tested comprises a slow disk test, initiating a read request and/or a write request to the target disk to be tested according to a preset frequency.
2. The method of claim 1,
the method for setting the test type of the target disk to be tested comprises the following steps: slow disk testing, read error testing, and/or write error testing of the target disk to be tested is enabled.
3. The method of claim 2,
configuring a performance parameter threshold related to the running condition of the target disk to be tested based on the test type of the target disk to be tested comprises the following steps:
when the test type of the target disk to be tested comprises a slow disk test, setting a disk task quantity threshold and a disk response time threshold, and configuring the disk task quantity threshold and the disk response time threshold as performance parameter thresholds related to the running condition of the target disk to be tested;
when the test type of the target disk to be tested comprises a read error test and/or a write error test, setting a disk response time threshold, and configuring the disk response time threshold as a performance parameter threshold related to the running condition of the target disk to be tested.
4. The method of claim 3,
when the test type of the target disk to be tested only comprises a read error test or a write error test, if the current disk response time of the target disk to be tested is greater than a disk response time threshold configured for the target disk to be tested, the performance of the target disk to be tested does not meet the performance parameter threshold requirement related to the running condition of the target disk to be tested;
when the test type of the target disk to be tested comprises slow disk test, if the current disk response time of the target disk to be tested is larger than a disk response time threshold configured for the target disk to be tested, and/or the current disk task amount of the target disk to be tested is larger than a disk task amount threshold configured for the target disk to be tested, the performance of the target disk to be tested does not meet the performance parameter threshold requirement related to the running condition of the target disk to be tested.
5. A bad track disk detection device is applied to a distributed storage system, and is characterized by comprising: the device comprises a determining unit, a configuration unit and a testing unit;
the determining unit is used for determining a target disk to be tested in the distributed storage system;
the configuration unit is used for setting the test type of each target disk to be tested and configuring a performance parameter threshold value related to the running condition of the target disk to be tested based on the test type of the target disk to be tested;
the testing unit is used for initiating a task request to each target disk to be tested according to the testing type of the target disk to be tested and a preset frequency so that when the distributed storage system determines that the performance of the target disk to be tested does not meet the performance parameter threshold requirement related to the running condition of the target disk to be tested, the target disk to be tested is determined to be a bad track disk and the target disk to be tested is kicked out from the distributed storage system;
wherein the test types include: slow disk test, read error test, write error test;
the test unit is used for initiating a task request to the target disk to be tested according to a preset frequency according to the test type of the target disk to be tested, and is used for:
when the test type of the target disk to be tested only comprises a read error test, initiating a read request to the target disk to be tested according to a preset frequency;
when the test type of the target disk to be tested only comprises a write error test, initiating a write request to the target disk to be tested according to a preset frequency;
and when the test type of the target disk to be tested comprises a slow disk test, initiating a read request and/or a write request to the target disk to be tested according to a preset frequency.
6. The apparatus of claim 5,
the configuration unit is used for setting the test type of the target disk to be tested and is used for: slow disk testing, read error testing, and/or write error testing of the target disk to be tested is enabled.
7. The apparatus of claim 6,
the configuration unit, based on the test type of the target disk to be tested, configures a performance parameter threshold related to the running condition of the target disk to be tested, including:
when the test type of the target disk to be tested comprises a slow disk test, setting a disk task quantity threshold and a disk response time threshold, and configuring the disk task quantity threshold and the disk response time threshold as performance parameter thresholds related to the running condition of the target disk to be tested;
when the test type of the target disk to be tested comprises a read error test and/or a write error test, setting a disk response time threshold, and configuring the disk response time threshold as a performance parameter threshold related to the running condition of the target disk to be tested.
8. The apparatus of claim 7,
when the test type of the target disk to be tested only comprises a read error test or a write error test, if the current disk response time of the target disk to be tested is greater than a disk response time threshold configured for the target disk to be tested, the performance of the target disk to be tested does not meet the performance parameter threshold requirement related to the running condition of the target disk to be tested;
when the test type of the target disk to be tested comprises slow disk test, if the current disk response time of the target disk to be tested is larger than a disk response time threshold configured for the target disk to be tested, and/or the current disk task amount of the target disk to be tested is larger than a disk task amount threshold configured for the target disk to be tested, the performance of the target disk to be tested does not meet the performance parameter threshold requirement related to the running condition of the target disk to be tested.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711388972.2A CN108319527B (en) | 2017-12-21 | 2017-12-21 | Bad track disk detection method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711388972.2A CN108319527B (en) | 2017-12-21 | 2017-12-21 | Bad track disk detection method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108319527A CN108319527A (en) | 2018-07-24 |
| CN108319527B true CN108319527B (en) | 2021-08-24 |
Family
ID=62891273
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201711388972.2A Active CN108319527B (en) | 2017-12-21 | 2017-12-21 | Bad track disk detection method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108319527B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109799960A (en) * | 2019-01-23 | 2019-05-24 | 郑州云海信息技术有限公司 | A method of improving storage system stability, system, equipment and readable storage medium storing program for executing |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101887351A (en) * | 2010-06-22 | 2010-11-17 | 杭州华三通信技术有限公司 | Fault-tolerance method and system for redundant array of independent disk |
| CN102866946A (en) * | 2012-08-15 | 2013-01-09 | 深圳市同洲电子股份有限公司 | Method and device for testing reading/writing function |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100498961C (en) * | 2004-07-01 | 2009-06-10 | 华为技术有限公司 | Hard disc detecting device and method |
| US9443616B2 (en) * | 2014-04-02 | 2016-09-13 | Seagate Technology Llc | Bad memory unit detection in a solid state drive |
| CN106557389B (en) * | 2015-09-29 | 2019-03-08 | 成都华为技术有限公司 | A kind of slow disk detection method and device |
| CN105630416B (en) * | 2015-12-24 | 2018-10-26 | 创新科存储技术（深圳）有限公司 | Disk method and device is kicked in a kind of cloud storage system |
-
2017
- 2017-12-21 CN CN201711388972.2A patent/CN108319527B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101887351A (en) * | 2010-06-22 | 2010-11-17 | 杭州华三通信技术有限公司 | Fault-tolerance method and system for redundant array of independent disk |
| CN102866946A (en) * | 2012-08-15 | 2013-01-09 | 深圳市同洲电子股份有限公司 | Method and device for testing reading/writing function |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108319527A (en) | 2018-07-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108446222B (en) | Application testing method, device and equipment | |
| TWI552158B (en) | Systems and methods for testing memory | |
| US8055948B2 (en) | Resilient software-controlled redundant array of independent disks (RAID) | |
| CN104317693A (en) | Method for automatically testing hard disk performance fluctuation | |
| CN110992992A (en) | Hard disk test method, device and storage medium | |
| US20140101106A1 (en) | Log server and log file storage method | |
| KR20100005699A (en) | Execution of point-in-time copy operations in continuous mirroring environments | |
| KR20190044820A (en) | Method and apparatus for extracting specific dynamic generated file | |
| CN107329914A (en) | It is a kind of that the out of order method and device of hard disk is detected based on linux system | |
| KR101976629B1 (en) | Commit sensitive tests | |
| CN108319527B (en) | Bad track disk detection method and device | |
| CN102222033A (en) | Method and device for saving small computer system interface access error | |
| CN104657088B (en) | A kind of acquisition methods and device of hard disk bad block message | |
| CN107864209B (en) | Data writing method and device and server | |
| US20110202903A1 (en) | Apparatus and method for debugging a shared library | |
| US9009430B2 (en) | Restoration of data from a backup storage volume | |
| CN109669828B (en) | Hard disk detection method and device | |
| CN114138575B (en) | Method, device, equipment and medium for testing hard disk data garbage recovery | |
| US10922249B2 (en) | Input/output control code filter | |
| US10853462B2 (en) | Authorizing file access with user I/O and hardware usage patterns | |
| CN107885640B (en) | Hard disk management method and device | |
| CN111858136A (en) | Method and system for detecting abnormal data of solid state disk, electronic device and storage medium | |
| CN110795297B (en) | Electronic equipment testing method and device | |
| CN110333985B (en) | Method and device for recording operation information of mobile terminal | |
| US20120173181A1 (en) | Electronic device and method for configurating setting values of oscilloscopes |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information | ||
| CB02 | Change of applicant information |
Address after: 518057 Shenzhen Software Park, No. 9, 501, 502, Science and Technology Middle Road, Nanshan District, Shenzhen City, Guangdong Province Applicant after: Shenzhen Innovation Technology Co., Ltd. Address before: 518057 Shenzhen Software Park, No. 9, 501, 502, Science and Technology Middle Road, Nanshan District, Shenzhen City, Guangdong Province Applicant before: UIT Storage Technology (Shenzhen) Co., Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |