CN108932249B - Method and device for managing file system - Google Patents
Method and device for managing file system Download PDFInfo
- Publication number
- CN108932249B CN108932249B CN201710375466.3A CN201710375466A CN108932249B CN 108932249 B CN108932249 B CN 108932249B CN 201710375466 A CN201710375466 A CN 201710375466A CN 108932249 B CN108932249 B CN 108932249B
- Authority
- CN
- China
- Prior art keywords
- file system
- file
- check value
- target file
- 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/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1448—Management of the data involved in backup or backup restore
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
A method and a device for managing a file system are used for solving the problem that a user cannot use the file system in time due to consistency check when the file system is mounted in the prior art. The method for managing the file system comprises the following steps: when consistency check is not carried out on a first file system corresponding to the first data partition, mounting the first file system; when a target file is read through the first file system, judging whether a first check value of the target file is correct or not; if the first check value of the target file is incorrect, the first file system is repaired by a file system checking Fsck tool.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method and an apparatus for managing a file system.
Background
File Systems (FS) in computers require file structure integrity, consistency between metadata, which refers to data used to describe data attributes, and between metadata and data. However, sometimes the consistency of the file system may be destroyed, for example, when the system is powered off, the data in the memory may be lost, or the consistency of the file system data may be destroyed due to a failure of the disk, for example, a bad track of the disk, etc. To check and maintain inconsistent file systems, file systems may provide a file system check (Fsck) tool to facilitate user checking and repair of file systems.
The Fsck tool may check the consistency of the file system before mounting the file system, for example, at initial system boot or when reloading the file system. The time consumed by the Fsck check is related to the size of the data partition corresponding to the file system and the number of files of the data partition, and the larger the data partition is, the larger the number of files is, the longer the time consumed by the Fsck check is.
At present, a big data service requires that a data partition has a larger size and more data are stored in the data partition, so that a large amount of time is consumed for checking the consistency of a file system when the file system is mounted, and a user cannot use the file system in time.
Disclosure of Invention
The application provides a method and a device for managing a file system, which are used for solving the problem that a user cannot use the file system in time due to consistency check during mounting of the file system in the prior art.
In a first aspect, an embodiment of the present application provides a method for managing a file system, including: when the system starts to mount the file system and re-mounts the file system after the system runs, the file system to be mounted is regarded as meeting the consistency requirement, consistency check is not carried out on the file system, and the file system is directly mounted. When an application reads a target file in a file system, the file system verifies the target file, if a verification value is wrong, the target file is determined to be wrong, data consistency on the file system is determined to be damaged, and an Fsck tool is called to carry out consistency repair on the file system.
According to the technical scheme, the node does not carry out consistency check on the file system before mounting the file system, so that the file system can be mounted in time, and a user can use the file system as soon as possible. In the process of reading the file through the file system, once a file error is found, the Fsck tool can be called to repair the file system, so that the data consistency of the file system is ensured. When the probability of file errors in the file system is low, the number of times of repairing the file system through the Fsck is small, and compared with a scheme of performing consistency check before mounting the file system every time in the prior art, the method can effectively reduce the number of times of Fsck check, reduce the time consumption of consistency check and further improve the efficiency of the file system.
As an optional design, when the first check value of the target file in the file system is incorrect, the reliability of the file system is reduced, the file system is unloaded, the correctness of the service is guaranteed, and it is ensured that the user obtains the correct file.
As an alternative design, when the first check value of the target file in the file system is incorrect, most of the files in the file system may still be correct, and the file system still has the capability of providing the correct files to the user, and the file system is not uninstalled, but is set to be in a read-only mode, so that the user can continue to access the files in the file system without errors, and the performance of the whole file system is improved. Moreover, the file system is set to be in a read-only mode, so that errors can be avoided after new data are written into the file system, and the reliability of the data is ensured.
As an alternative design, if the file system is uninstalled when the first check value of the target file in the file system is incorrect, after the file system is repaired by the Fsck tool, the file system is reinstalled and set to a readable and writable mode so that the file system can continue to provide services to the user.
As an alternative design, if the file system is set to the read-only mode when the first check value of the target file in the file system is incorrect, after the file system is repaired by the Fsck tool, the file system is set to the read-writable mode so that the file system can continue to provide services to the user.
As an optional design, if the target file is verified by the file system and no error occurs in the target file, the target file is read by the file system and sent to the application, and the application performs secondary verification on the file after acquiring the file from the file system, so that the correctness of the file is further ensured, and the reliability of the service is improved. And after the application determines that the target file is wrong, the backup data of the file can be read from other file systems, and the wrong file is repaired by using the backup, so that the reliability of the data in the file system is improved.
As an optional design, the two file systems may both store the same file, and the data partitions corresponding to the two file systems may be located in the same storage device (e.g., a disk), may also be located on different storage devices of the same node, and may also be located in two different nodes, respectively.
As an optional mode, the application performs secondary verification on the target file, and stops the data partition storing the target file after determining that the target file is in error, so as to ensure correctness of the service and ensure that the user obtains the correct file.
In a second aspect, an embodiment of the present application provides an apparatus for managing a file system, where the apparatus for managing a file system is configured to perform the method in the first aspect or any optional design of the first aspect. In particular, the apparatus for managing a file system comprises means for performing the method of the first aspect described above or any of the alternative designs of the first aspect.
In a third aspect, an embodiment of the present application provides an apparatus for managing a file system, including: a memory, a processor, and a communication interface. The memory stores computer instructions, and the processor communicates with other nodes via the communication interface and invokes the computer instructions stored in the memory to perform the method of the first aspect or any alternative design of the first aspect.
In a fourth aspect, embodiments of the present application provide a computer-readable storage medium having stored thereon computer instructions, which, when executed on a computer, cause the computer to perform the method of the first aspect or any alternative design of the first aspect.
Drawings
Fig. 1 is a schematic diagram of a distributed file system according to an embodiment of the present application;
FIG. 2 is a flowchart illustrating a method for managing a file system according to an embodiment of the present application;
FIG. 3 is a diagram illustrating a file system verifying data according to an embodiment of the present application;
FIG. 4 is a schematic flow chart illustrating a method for managing a file system according to an embodiment of the present application;
FIG. 5 is a diagram illustrating a file system management system according to an embodiment of the present application;
FIG. 6 is a diagram illustrating an apparatus for managing a file system according to an embodiment of the present application;
FIG. 7 is another diagram illustrating an apparatus for managing a file system according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more clear, the present application will be further described in detail with reference to the accompanying drawings.
In the prior art, when a system starts or re-mounts a file system, consistency check needs to be performed on the file system, and the consistency check consumes a large amount of time, so that a user cannot use the file system in time. In some network file systems, the consistency of files is maintained by a remote storage server, but the remote storage server becomes a bottleneck of the file system, which restricts the access efficiency of the file system, and once the remote storage server fails, the whole file system is inaccessible.
The application provides a method and a device for managing a file system, which are used for solving the problem that a user cannot use the file system in time due to consistency check during mounting of the file system in the prior art. The method and the device are based on the same inventive concept, and because the principles of solving the problems of the method and the device are similar, the implementation of the device and the method can be mutually referred, and repeated parts are not repeated.
It is to be understood that the plurality referred to in the present application means two or more. In addition, in the description of the present application, the terms "first," "second," and the like are used for descriptive purposes only and are not intended to indicate or imply relative importance nor order to be construed.
The application can be applied to a distributed system, and two or more nodes in the distributed system can form a High Availability (HA) cluster. As shown in FIG. 1, the node 1 includes data partitions 1-3, each of which corresponds to a file system, FS 1-FS 3, and similarly, the node 2 includes data partitions 4-6, which correspond to file systems FS 4-FS 6. The same application for providing service for the client is run on the node 1 and the node 2, and when data stored in the file system FS2 in the node 1 is wrong, so that the application on the node 1 cannot provide service, the application on the node 2 can immediately continue the application on the node 1 to provide service for the client, thereby realizing uninterrupted or short-term interruption of service. In the embodiment of the present application, the relationship between different nodes that are HA for each other may be: the method comprises the following steps of active/standby, full-active and N + M, wherein the active/standby refers to that one node is a main node (namely an active node) and the other nodes are standby nodes; full activity means that all nodes are active nodes; n + M means that N nodes are active nodes and M nodes are standby nodes.
Fig. 2 is a flowchart of a method for managing a file system according to an embodiment of the present application, where the method may include the following steps:
In the embodiment of the application, when the system starts to mount the file system and re-mounts the file system after the system runs, the file system to be mounted is regarded as meeting the consistency requirement, consistency check is not carried out on the file system, and the file system is directly mounted.
The first file system is a file system corresponding to any data partition on any node. When the application reads the target file in the first file system of the file, the first file system checks the target file, for example, calculates a first check value of the target file, compares the first check value with a pre-stored check value, and determines that the target file is in error if the first check value is inconsistent with the pre-stored check value. The first check value can be realized in various ways and corresponds to various check means. For example, referring to fig. 3, when data of a file is written to the first file system, Check values of the file (or data blocks of the file) are recorded, such as a checksum (checksum), a hash (hash) value, a Cyclic Redundancy Check (CRC), and the like. Then, when the application reads the file from the first file system, the first file system calculates a data check value of the file (or a data block of the file), compares the calculated data check value with a stored data check value, and if the calculated data check value is inconsistent with the stored data check value, it indicates that the file has an error.
And 103, if the first check value of the target file is incorrect, repairing the first file system by using a file system checking Fsck tool.
After the first file system determines that the target file has an error by calculating the data check value, it is determined that the data consistency on the first file system is damaged, and an Fsck tool is called to perform consistency repair on the first file system. For the specific process of Fsck repairing the first file system, please refer to various technical means in the prior art, which are not described in detail herein.
According to the technical scheme, the node does not carry out consistency check on the file system before mounting the file system, so that the file system can be mounted in time, and a user can use the file system as soon as possible. In the process of reading the file through the file system, once a file error is found, the Fsck tool can be called to repair the file system, so that the data consistency of the file system is ensured. It can be seen that when the probability of a file error in the file system is low, the number of times of repairing the file system through the Fsck is small, and compared with a scheme of performing consistency check before mounting the file system every time in the prior art, the scheme provided by the embodiment of the application can effectively reduce the number of times of Fsck check, reduce time consumption of consistency check, and improve the efficiency of the file system. Moreover, after a data inconsistency error may exist in the mounted file system, the standby node or other active nodes in the HA system can still provide services to the outside, and the user can still continue to read the target file.
As an alternative design, referring to fig. 4, after step 102, the following steps are further included:
and step 104, if the first check value of the target file is incorrect, setting the first file system to be in a read-only mode or unloading the first file system.
The first check value of the target file is incorrect, which indicates that the target file is wrong, the reliability of the first file system is reduced, and the unloading of the first file system can ensure the correctness of the service and ensure that a user obtains a correct file.
Another possible implementation is: instead of unloading the first file system, the first file system is set to read-only mode. This is because although the first file in the first file system is erroneous, most of the files in the first file system are still typically correct, and the first file system still has the ability to provide the correct files to the user. However, since the file with the error already exists in the first file system, and the error may be an error in the storage area of the first data partition corresponding to the first file system, new data is continuously written into the first file system, and the new data may have an error, and reliability of the data newly written into the first file system cannot be guaranteed. Therefore, the first file system is set to be in a read-only mode, so that a user can continuously access files without errors in the first file system, the performance of the whole file system is improved, new data can be prevented from being written into the first file system, and the reliability of the data is ensured.
As an alternative design, after step 103 and step 104, if the Fsck tool successfully repairs the first file system, the service of reading and writing files through the first file system may be continued. Specifically, if the first file system is set to the read-only mode in step 104, the first file system is set to the read-writable mode after the Fsck tool successfully repairs the first file system. If the first file system is unmounted in step 104, the first file system is re-mounted after the Fsck tool successfully repairs the first file system and is set to a read-writable mode. The technical scheme can repair the file system with consistency errors in time, and the file system is configured to continue providing services to the outside after the repair is successful.
As an alternative design, if the Fsck tool successfully repairs the first file system, the first file system may notify the application using the first file system that the first file system is restored and the application may continue to access the first file system.
As an alternative design, with continuing reference to fig. 4, after step 102, the following steps are also included:
and 105, if the first check value of the target file is correct, reading the target file through the first file system, and if the target file is successfully read, sending the target file to the application requesting the target file.
And 106, judging whether the second check value of the target file is correct or not through the application, wherein the second check value is different from the first check value. The second check value and the first check value may be the same type of check value, for example, the first check value and the second check value are both checksums of the target file (or data blocks of the target file), but the first check value and the second check value are different due to different specific algorithms for calculating the two checksums. In addition, the first check value and the second check value may also be different types of check values, for example, the first check value is a checksum, and the second check value is a hash value. After receiving the target file returned by the first file system, the application can perform secondary verification on the target file according to the second verification value to ensure the correctness of the service.
When the second check value is incorrect, which indicates that an error still exists although the target file passes the check of the first file system, the application may read the target file from the second file system of another data partition (i.e., the second data partition) storing the backup data of the target file, and repair the target file in the first file system according to the target file in the second file system when the target file in the second file system is correct. The second data partition and the first data partition may be located in the same storage device (e.g., a disk), may also be located in different storage devices of the same node, or may also be located in two different nodes.
According to the technical scheme, after the file is acquired from the file system, the file is subjected to secondary verification, so that the correctness of the file is further ensured, and the reliability of the service is improved. And after the application determines that the target file is wrong, the backup data of the file can be read from other file systems, and the wrong file is repaired by using the backup, so that the reliability of the data in the file system is improved.
As an optional mode, after determining that the second check value of the target file is incorrect, the application disables the first data partition, so as to ensure correctness of the service and ensure that the user obtains the correct file.
Fig. 5 is a schematic diagram of a possible implementation manner of managing a file System in an embodiment of the present application, where an OS in the diagram refers to an Operating System (Operating System) of a node, and an Fsck tool may be implemented by a hardware chip or a software module, that is, implemented by a processor of the node running a computer program. In the implementation of fig. 5, at the time of OS startup, instead of running Fsck tool to perform consistency check on the file system, the file system is mounted directly, and the mounted file system can be accessed by the application. In the process of using the file system, if a consistency error exists in the file system, the application stops the file system with the consistency error and calls an Fsck tool to repair the file system. After the repair is successful, the Fsck tool or the repaired file system may notify the application so that the application may resume continued access to the repaired file system.
Fig. 6 is a schematic diagram of an apparatus for managing a file system according to an embodiment of the present application, where the apparatus includes:
the mount module 201 is configured to mount a first file system corresponding to a first data partition when consistency check is not performed on the first file system;
a determining module 202, configured to determine whether a first check value of a target file is correct when the target file is read through the first file system;
a repairing module 203, configured to repair the first file system through a file system checking Fsck tool when the first check value of the target file is incorrect.
Optionally, the apparatus further comprises:
a configuration module 204, configured to set the first file system to a read-only mode or uninstall the first file system when the first check value of the target file is incorrect.
Optionally, the configuration module 204 is further configured to: after the repair module 203 repairs the first file system through the Fsck tool, if the first file system is set to the read-only mode, setting the first file system to a readable and writable state; or if the first file system is unloaded, mounting the first file system.
Optionally, the apparatus further comprises:
a sending module 205, configured to, after the determining module determines that the first check value of the target file is correct, read the target file through a first file system, and if the target file is successfully read, send the target file to an application requesting the target file;
a second determining module 206, configured to determine whether a second check value of the target file is correct through the application, where the second check value is different from the first check value;
a second repair module 207, configured to, when the second check value of the target file is incorrect, obtain data of the target file from a second file system corresponding to a second data partition in which backup data of the target file is stored; and recovering the data of the target file in the first file system according to the data of the target file in the second file system.
Optionally, the first data partition and the second data partition are located on different servers.
In the embodiments of the present application, the division of the module of the apparatus for managing a file system is schematic, and is only a logical function division, and in actual implementation, there may be another division manner, and in addition, each functional module in each embodiment of the present application may be integrated in one processor, may also exist alone physically, or may also integrate two or more modules in one module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode.
Where the integrated module may be implemented in hardware, as shown in fig. 7, the apparatus for managing a file system may include a processor 301. The hardware of the entity corresponding to the above modules may be the processor 301. The processor 301 may be a Central Processing Unit (CPU), a digital processing module, or the like. The means for managing the file system may further comprise a communication interface 302, the processor 301 communicating with other nodes via the communication interface 302. The apparatus for managing a file system further comprises: a memory 303 for storing programs executed by the processor 301. The memory 301 may be a nonvolatile memory such as a Hard Disk Drive (HDD) or a solid-state drive (SSD), and may also be a volatile memory (RAM), for example, a random-access memory (RAM). The memory 303 is any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to such.
The processor 301 is configured to execute the program code stored in the memory 303, and in particular to execute the method of the embodiment shown in fig. 2, 4 or 5. The implementation of the apparatus for managing a file system can refer to the method in the embodiment shown in fig. 2, fig. 4, or fig. 5, and is not described herein again.
The specific connection medium among the communication interface 302, the processor 301, and the memory 303 is not limited in the embodiment of the present application. In the embodiment of the present application, the memory 303, the processor 301, and the communication interface 302 are connected by a bus in fig. 7, the bus is represented by a thick line in fig. 7, and the connection manner between other components is merely illustrative and not limited thereto. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 7, but this is not intended to represent only one bus or type of bus.
The embodiment of the present invention further provides a computer-readable storage medium, which is used for storing computer software instructions required to be executed for executing the processor, and which contains a program required to be executed for executing the processor.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.
Claims (10)
1. A method of managing a file system, comprising:
when consistency check is not carried out on a first file system corresponding to a first data partition, mounting the first file system;
when a target file is read through the first file system, judging whether a first check value of the target file is correct or not;
if the first check value of the target file is incorrect, repairing the first file system by a file system checking Fsck tool;
after judging whether the first check value of the target file is correct, the method further comprises the following steps:
if the first check value of the target file is correct, reading the target file through the first file system and sending the target file to an application requesting the target file;
judging whether a second check value of the target file is correct or not through the application, wherein the second check value is different from the first check value;
if the second check value of the target file is incorrect, obtaining the data of the target file from a second file system corresponding to a second data partition in which the backup data of the target file is stored;
and recovering the data of the target file in the first file system according to the data of the target file in the second file system.
2. The method of claim 1, further comprising:
and when the first check value of the target file is incorrect, setting the first file system to a read-only mode or unloading the first file system.
3. The method of claim 2, further comprising, after repairing the first file system via the Fsck tool:
if the first file system is set to be in a read-only mode, setting the first file system to be in a read-write state; or
And if the first file system is unloaded, mounting the first file system.
4. The method of claim 1, wherein the first data partition is located on a different server than the second data partition.
5. An apparatus for managing a file system, comprising:
the mounting module is used for mounting the first file system when consistency check is not carried out on the first file system corresponding to the first data partition;
the judging module is used for judging whether a first check value of a target file is correct or not when the target file is read through the first file system;
a repair module, configured to repair the first file system through a file system check Fsck tool when the first check value of the target file is incorrect;
further comprising:
the sending module is used for reading the target file through the first file system and sending the target file to an application requesting the target file after the judging module judges that the first check value of the target file is correct;
the second judging module is used for judging whether a second check value of the target file is correct or not through the application, and the second check value is different from the first check value;
the second repair module is used for obtaining the data of the target file from a second file system corresponding to a second data partition in which the backup data of the target file is stored when the second check value of the target file is incorrect; and recovering the data of the target file in the first file system according to the data of the target file in the second file system.
6. The apparatus of claim 5, further comprising:
and the configuration module is used for setting the first file system into a read-only mode or unloading the first file system when the first check value of the target file is incorrect.
7. The apparatus of claim 6, wherein the configuration module is further configured to: after the repair module repairs the first file system through the Fsck tool, if the first file system is set to be in a read-only mode, setting the first file system to be in a read-write state; or if the first file system is unloaded, mounting the first file system.
8. The apparatus of claim 5, wherein the first data partition is located on a different server than the second data partition.
9. An apparatus for managing a file system, comprising:
a memory storing computer instructions;
a processor coupled to the memory for invoking computer instructions stored in the memory for performing the method of managing a file system of any of claims 1-4.
10. A computer-readable storage medium having stored therein computer instructions which, when run on a computer, cause the computer to perform the method of managing a file system of any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710375466.3A CN108932249B (en) | 2017-05-24 | 2017-05-24 | Method and device for managing file system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710375466.3A CN108932249B (en) | 2017-05-24 | 2017-05-24 | Method and device for managing file system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108932249A CN108932249A (en) | 2018-12-04 |
| CN108932249B true CN108932249B (en) | 2021-02-12 |
Family
ID=64451400
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710375466.3A Active CN108932249B (en) | 2017-05-24 | 2017-05-24 | Method and device for managing file system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108932249B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US11875062B1 (en) | 2022-06-23 | 2024-01-16 | Western Digital Technologies, Inc. | Proactive hardening of data storage system |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110059056A (en) * | 2019-04-18 | 2019-07-26 | 北京思特奇信息技术股份有限公司 | The distributed system read/writable detection method of multinode multifile, device, equipment |
| CN110532032B (en) * | 2019-07-31 | 2021-01-05 | 华为技术有限公司 | Startup file system detection method and related equipment |
| CN111177085A (en) * | 2019-12-27 | 2020-05-19 | 浪潮(北京)电子信息产业有限公司 | Method, device and medium for verifying data consistency function of file system |
| CN112783444A (en) * | 2021-01-18 | 2021-05-11 | 深圳市科思科技股份有限公司 | Cluster disk sharing method, system and storage medium |
| CN112817911B (en) * | 2021-02-09 | 2023-07-11 | 海信视像科技股份有限公司 | File system repairing method and terminal equipment |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101025770A (en) * | 2006-02-20 | 2007-08-29 | 联想(北京)有限公司 | Method for starting protected partition |
| CN101038556A (en) * | 2007-04-30 | 2007-09-19 | 中国科学院软件研究所 | Trusted bootstrap method and system thereof |
| CN101567805A (en) * | 2009-05-22 | 2009-10-28 | 清华大学 | Method for recovering failed parallel file system |
| US7765187B2 (en) * | 2005-11-29 | 2010-07-27 | Emc Corporation | Replication of a consistency group of data storage objects from servers in a data network |
| CN102932621A (en) * | 2011-08-08 | 2013-02-13 | 杭州海康威视数字技术股份有限公司 | Method and device for storing data |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6895413B2 (en) * | 2002-03-22 | 2005-05-17 | Network Appliance, Inc. | System and method for performing an on-line check of a file system |
| CN101883028B (en) * | 2010-06-30 | 2015-06-24 | 中兴通讯股份有限公司 | Method and device for detecting network file system server |
| US8756458B2 (en) * | 2011-12-12 | 2014-06-17 | Apple Inc. | Mount-time reconciliation of data availability |
| CN103164523A (en) * | 2013-03-19 | 2013-06-19 | 华为技术有限公司 | Inspection method, device and system of data consistency inspection |
| CN106227839A (en) * | 2016-07-26 | 2016-12-14 | 浪潮电子信息产业股份有限公司 | The expansion method of a kind of lustre file system and device |
-
2017
- 2017-05-24 CN CN201710375466.3A patent/CN108932249B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7765187B2 (en) * | 2005-11-29 | 2010-07-27 | Emc Corporation | Replication of a consistency group of data storage objects from servers in a data network |
| CN101025770A (en) * | 2006-02-20 | 2007-08-29 | 联想(北京)有限公司 | Method for starting protected partition |
| CN101038556A (en) * | 2007-04-30 | 2007-09-19 | 中国科学院软件研究所 | Trusted bootstrap method and system thereof |
| CN101567805A (en) * | 2009-05-22 | 2009-10-28 | 清华大学 | Method for recovering failed parallel file system |
| CN102932621A (en) * | 2011-08-08 | 2013-02-13 | 杭州海康威视数字技术股份有限公司 | Method and device for storing data |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US11875062B1 (en) | 2022-06-23 | 2024-01-16 | Western Digital Technologies, Inc. | Proactive hardening of data storage system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108932249A (en) | 2018-12-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108932249B (en) | Method and device for managing file system | |
| EP2048579B1 (en) | System and method for managing memory errors in an information handling system | |
| US20110099148A1 (en) | Verification Of Remote Copies Of Data | |
| CN111078662B (en) | Block chain data storage method and device | |
| US9977706B2 (en) | System and method of validating data for incremental format of backup archive | |
| CN107315616B (en) | Firmware loading method and device and electronic equipment | |
| US10819611B2 (en) | Dynamic timeout-based fault detection | |
| CN111651304B (en) | Software recovery method and device based on double-core intelligent ammeter and computer equipment | |
| US20220334733A1 (en) | Data restoration method and related device | |
| CN112099597A (en) | Board adapting method, device, equipment and machine readable storage medium | |
| CN113377569B (en) | Method, apparatus and computer program product for recovering data | |
| CN113672270A (en) | Upgrading method, computer system and remote upgrading device | |
| US11726879B2 (en) | Multiple block error correction in an information handling system | |
| US20190317861A1 (en) | High availability state machine and recovery | |
| CN111124294B (en) | Sector mapping information management method and device, storage medium and equipment | |
| CN117131014A (en) | Database migration method, device, equipment and storage medium | |
| CN115470041A (en) | Data disaster recovery management method and device | |
| WO2021043246A1 (en) | Data reading method and apparatus | |
| US11249868B2 (en) | Method of fault management in a network of nodes and associated part of network of nodes | |
| CN114385418A (en) | Protection method, device, equipment and storage medium for communication equipment | |
| US10706169B1 (en) | Quarantining storage objects using a quarantine list | |
| CN110544504A (en) | test method, system and equipment for memory ADDDC function | |
| CN117271225B (en) | FRU information backup method, FRU information backup device and FRU information backup server | |
| WO2023060976A1 (en) | File reading and writing method for embedded file system, and electronic device and storage medium | |
| CN112306747B (en) | RAID card fault processing method and device |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20220211 Address after: 550025 Huawei cloud data center, jiaoxinggong Road, Qianzhong Avenue, Gui'an New District, Guiyang City, Guizhou Province Patentee after: Huawei Cloud Computing Technology Co.,Ltd. Address before: 518129 Bantian HUAWEI headquarters office building, Longgang District, Guangdong, Shenzhen Patentee before: HUAWEI TECHNOLOGIES Co.,Ltd. |