WO2012075845A1 - Système de fichiers distribué - Google Patents

Système de fichiers distribué Download PDF

Info

Publication number
WO2012075845A1
WO2012075845A1 PCT/CN2011/079685 CN2011079685W WO2012075845A1 WO 2012075845 A1 WO2012075845 A1 WO 2012075845A1 CN 2011079685 W CN2011079685 W CN 2011079685W WO 2012075845 A1 WO2012075845 A1 WO 2012075845A1
Authority
WO
WIPO (PCT)
Prior art keywords
storage system
metadata
data
module
backup
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.)
Ceased
Application number
PCT/CN2011/079685
Other languages
English (en)
Chinese (zh)
Inventor
张辉
范家星
姜南
吴波
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Publication of WO2012075845A1 publication Critical patent/WO2012075845A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/18—File system types
    • G06F16/182—Distributed file systems

Definitions

  • Embodiments of the present invention relate to data backup technologies, and in particular, to a distributed file system. Background technique
  • RAID Redundant Array of Independent Disk
  • RAID is a combination of multiple independent hard disks (physical hard disks) in different ways to form a disk group (logical hard disk), which provides higher storage performance and data backup technology than a single hard disk.
  • the prior art generally uses the storage striping management of the distributed file system to superimpose the aggregated hard disk bandwidth.
  • the striping is a management function, and the function is to spread data on multiple storage devices in a certain step size, so that the data is obtained from multiple physical storage devices in parallel during reading, and the performance of multiple physical storage devices is superimposed. .
  • the data redundancy and data striping features of RAID technology ensure high reliability and high performance of distributed file systems.
  • a distributed file system can be understood to be built on a network storage system.
  • the trend of hard disk being replaced by solid state disk is growing.
  • the solid state disk is extremely expensive, the RAID technology of solid state disk backup SSD is causing a sharp increase in server cost.
  • RAID technology is often implemented in RAID1 and RAID5.
  • RAID1 is a level 1 RAID technology. It uses a full-mirror backup. It requires two homogeneous storage systems to perform read and write operations simultaneously and mirror each other. Even if one disk is damaged, the system can work normally.
  • RAID5 is a storage solution that combines storage performance, data security, and storage costs.
  • the data and the corresponding parity information are stored on the respective disks constituting the RAID 5, and the parity information and the corresponding data are respectively stored on different disks.
  • the remaining data and corresponding parity information are used to recover the corrupted data.
  • An embodiment of the present invention provides a distributed file system, including: an access module, a metadata management unit connected to the access module, and an active storage system and an alternate storage system respectively connected to the metadata management unit.
  • the access module is further connected to the primary storage system and the backup storage system respectively; between the access module, the metadata management unit, the primary storage system, and the backup storage system And the external storage system is connected to the primary storage system and the backup storage system by using a network; wherein: the access module is configured to receive a read/write data request, Transmitting, to the metadata management unit, a metadata request to acquire metadata corresponding to the requested data, and applying the metadata to read and write data to the primary storage system or the standby storage system;
  • the metadata management unit is configured to: when the access module requests the metadata, find a location of the requested data on the primary storage system or the backup storage system, and construct the metadata Returning to the access module, the primary storage system, configured to provide the requested data to the access module when the distributed file system is in a normal state; and the standby storage system is configured to When the distributed file system is in an abnormal state or a restored state, the primary storage system is Providing data backup; the external storage system is configured to provide data backup for the primary storage system.
  • the asynchronous backup mechanism is used to backup to the backup storage system, which does not affect the read and write performance of the high-speed device;
  • the data is automatically restored during the external service process, and the recovery process is accelerated.
  • FIG. 1 is a schematic diagram showing the composition of a distributed file system according to an embodiment of the present invention
  • FIG. 2 is a schematic diagram of a composition of a distributed file system according to another embodiment of the present invention.
  • FIG. 3 is a schematic diagram of a process flow of a distributed file system in a normal state according to an embodiment of the present invention
  • FIG. 4 is a schematic flowchart of a process of a distributed file system in an abnormal state and a read data request according to an embodiment of the present invention
  • FIG. 5 is a schematic diagram of a process flow of a distributed file system in an abnormal state and in the case of a write data request according to an embodiment of the present invention
  • FIG. 6 is a schematic flowchart of a process for a distributed file system to respond to a read data request in a recovery state according to an embodiment of the present invention
  • FIG. 7 is a schematic diagram of a process flow of a distributed file system in response to a write data request in a recovery state according to an embodiment of the present invention
  • FIG. 8 is a schematic diagram of a processing flow of a data recovery process in a system recovery state of a distributed file system according to an embodiment of the present invention.
  • the distributed file system 1 includes an access module 11, a metadata management unit 12 connected to the access module 11, and a separate element.
  • the primary storage system 13 and the backup storage system 14 are connected to the data management unit 12, and the access module 11 is also connected to the primary storage system 13 and the backup storage system 14, respectively; wherein, the access module 11, the metadata management unit 12, and the main The storage system 13 and the backup storage system 14 are both located in the internal network, and the functional modules are connected by a system bus;
  • the distributed file system 1 further includes an external storage system 15 located in the external network, and the external storage system 15 is used by the primary storage system 15
  • the storage system 13 and the alternate storage system 14 are networked and connected.
  • the access module 11 in the distributed file system 1 is configured to receive a read/write data request, send a metadata request to the metadata management unit 12 to obtain metadata corresponding to the requested data, and apply the metadata to the primary storage.
  • System 13 or backup storage system 14 reads and writes data;
  • the access module 11 is an entry for the distributed file system 1 to access data, receives read and write data requests from the application, acquires metadata from the metadata management unit 12, and reads the metadata information to the primary storage system 13 and the backup storage system 14 using the metadata information. Write data.
  • As a function module it can be deployed in a single processing unit, such as a PC or a board. There are multiple general access modules to provide high throughput to the outside of the system, at least one.
  • the metadata management unit 12 is configured to: when the access module 11 requests the metadata, find a location of the requested data on the primary storage system 13 or the backup storage system 14, and construct the metadata, and return the connection.
  • the module 11 is also used to convert the system state of the distributed file system 1 according to the device status event of the primary storage system 13.
  • Distributed file system 1 has three states: normal state, abnormal state, and recovery state: where: In the normal state, the storage device of the primary storage system 13 is not faulty, and the data is stored on the primary storage system, and is backed up to the backup storage system 14 when necessary.
  • the abnormal state refers to the failure of the storage device in the primary storage system.
  • the primary storage system 13 and the standby storage system 14 work together to coordinate the completion of data storage, and the coordination result is saved, and the coordination result is used for the data recovery process.
  • Recovery status refers to the primary storage system. After the failed storage device is restored, the system is triggered to perform system data recovery. The backup data on the backup storage system 14 is used to restore the data originally stored on the failed storage device.
  • the metadata management unit 12 is responsible for finding the location of the data on the storage system and constructing the metadata when the access module 11 requests the metadata, and returns it to the access module 11.
  • the metadata management unit 12 is also responsible for managing the system status, receiving the device status event of the primary storage system 13, converting the system status, selecting the storage system, determining the data storage device (location) according to the event information, and also responsible for the reliability of the system. Automatically back up data based on data access information.
  • the available metadata is automatically formed according to the data distribution of the primary, backup, and external storage systems to ensure the availability of the system; and the system is automatically responsible for online online recovery to ensure data availability and data consistency.
  • the metadata management unit 12 can be deployed separately on one server.
  • the primary storage system 13 is configured to provide the requested data to the access module 11 in the normal state.
  • the primary storage system 13 is the main storage of the distributed file system 1, and is used to store all data of the system for the purpose of high read/write performance.
  • the system uses the primary storage system 13 to read and write data and all data in a normal state. It is stored on the primary storage system 13, and is composed of a high-speed storage device.
  • the storage striping technology supports storage bandwidth aggregation to improve read and write performance, and provides a block access mode.
  • the access module 11 can directly read and write the stored information in a block manner. data.
  • the backup storage system 14 is configured to provide a backup of the data to the primary storage system 13 in the abnormal state and the restored state.
  • the backup storage system 14 is a secondary storage of the distributed file system 1 for backing up data to support system reliability, availability, and data recoverability, and using storage striping technology to support storage bandwidth aggregation to improve read and write performance. , provide block access mode, connect The incoming module 11 can directly read and write data stored thereon in a block manner.
  • the external storage system 15 is configured to provide data for the primary storage system 13 .
  • the external storage system 15 refers to a storage system that stores more data, and may be an upper layer or other system in the same layer.
  • the external storage system 15 is connected to other modules of the system through the network, and uses the network access method to read and write data, and is used as a supplement to the external data backup. If the primary storage system 13 or the backup storage system 14 cannot find the corresponding data, the external storage system 15 can The external storage system 15 requests data.
  • the above internal network is a network directly connected to the access module 11, the metadata management unit 12, the primary storage system 13 and the backup storage system 14, and may be an Ethernet or an internal bus (e.g., a PCIe bus).
  • the metadata is mainly information describing the data attributes, and is used to support such as indicating the storage location, history information, resource information, and file records, etc., for example, may be a storage address of the data (the length and offset of the request) of the saved request (may be included) Storage device number, storage block number, data offset). Metadata can also be the inode number of the data.
  • the index node of the data is stored in the storage device and identifies the storage address of the data. Based on the inode number of the data, the storage address of the inode can be calculated.
  • the distributed file system 1 includes an access module 11, a metadata management unit 12, and a primary storage system 13. And the alternate storage system 14 and the external storage system 15. Further, the metadata management unit 12 includes a metadata operation module, a backup module, and an exception recovery module; wherein:
  • the metadata operation module is respectively connected to the access module 11 and the primary storage system 13 for receiving the metadata request, requesting metadata from the primary storage system 13 or the abnormal recovery module, and returning to the access module 11
  • the metadata is further configured to update the system state according to the device status event reported by the received primary storage system 13; and further responsible for state management of the system, and record data control information in the read/write data request.
  • the metadata operation module receives all metadata requests of the access module 11 and first retrieves its metadata cache. If the metadata is not found, the metadata needs to be requested from the primary storage system 13 or the backup storage system 14. The cache obtains the metadata, and finally returns the metadata to the access module 11. In the normal state, the metadata cache is retrieved.
  • the metadata management unit 12 may include a data control information recording module connected between the metadata operation module and the backup module for permanently storing the data control information.
  • the metadata operation module forwards the metadata request sent by the receiving module 11 to the abnormality recovery module, and the abnormality recovery module is responsible for obtaining the metadata information to the primary storage system 13 and the backup storage system 14.
  • the write data process In the recovery state, the write data process is the same as in the normal state, the metadata operation module requests metadata from the main storage system 13; the read data process requests the exception recovery module to handle the processing.
  • the metadata operation module is responsible for state management.
  • the primary storage system 13 is responsible for reporting device status events. When a device failure event is received, the faulty device ID is recorded, and the system status changes from normal to abnormal. When the device recovery event is received, the system status is determined by The abnormality is changed to recovery; when the recovery operation is completed, after the metadata recovery module is notified by the abnormality recovery module, the system state is changed from normal to normal.
  • the backup module is connected to the metadata operation module and the backup storage system 13, and is configured to read the data control information recorded by the metadata operation module, generate data backup operation control information, and send the data to the backup storage system. 14.
  • the data on the primary storage system 13 is backed up to the alternate storage system 14. Specifically, in the normal state, the module is operated by a background thread, and the data control information recorded by the metadata operation module of the previous period is read, the data usage status is analyzed according to the backup policy, and a data backup request is generated, and then The backup operation control information (operation type, target file path, source file path) is issued to the backup storage system 14, and the file on the primary storage system is required to be backed up to a specified location on the alternate storage server.
  • the backup module combines the backup strategy and can flexibly implement various data backup schemes, including a full backup scheme.
  • analyzing data only the write data operation is analyzed. Once the data is written, a backup request needs to be generated; including a hotspot backup scheme, when analyzing data. Only analyze the read data usage (read data request times, read data frequency), according to the data hotspot conditions in the policy (the number of times that can be used, the frequency of reading data); including the backup specified data side
  • the data feature code can be specified by the strategy, and the specified data feature code is analyzed and the backup request is generated when analyzing the data; the analysis includes the information in the data, and the request information is generated according to the request information.
  • the abnormality recovery module is respectively connected to the metadata operation module, the backup module, the primary storage system 13, and the backup storage system 14, and is configured to acquire the metadata in the abnormal state and the restored state. And return to the metadata operation module.
  • the abnormality recovery module is responsible for obtaining metadata information in an abnormal, recovery state and maintaining the validity of the metadata cache, and controlling the data recovery operation of the primary storage system 13 to support system availability under the failure of the primary storage system 13.
  • the abnormality recovery module may include the following submodules:
  • a first processing submodule configured to perform a missing block detection on the metadata obtained from the cache or from the primary storage system 13 for the read data request in the abnormal state, and if the metadata is detected to have a missing block,
  • the request information is sent to the alternate storage system 14 including the missing block information and the address of the external storage system 14; after the backup storage system 14 returns the metadata, a block address rebinding operation is performed, the available metadata is reassembled and transmitted.
  • the abnormality recovery module first retrieves its metadata cache through the first processing submodule, and if no metadata is found, requests the primary storage system 13 for metadata, and then The metadata performs a missing block (data is stored on the faulty storage device, detecting its storage device ID).
  • the metadata is requested from the standby storage system 14, and the request information includes missing block information (block number, data ID). , offset) with the external storage system 15 address, after the backup storage system 14 returns metadata, a block address rebinding operation is performed.
  • the block address rebinding operation refers to replacing the metadata information corresponding to the missing block on the spare storage system 14 with the metadata information corresponding to the missing block on the primary storage system 13, reconstituting the available metadata, and buffering the metadata. Speed up metadata acquisition.
  • a second processing submodule configured to, in the abnormal state, request metadata for the standby storage system 14 and return to the metadata operation module for the write data request; and also for recording the write data operation to the data
  • the data is synchronized to the primary storage system 13 in accordance with the recorded write data operation during the recovery process.
  • the abnormality recovery module automatically selects the backup storage system 14 as a storage target through the second processing submodule, and only supplies the standby storage system.
  • the access module 11 writes the data to the backup storage system 14 according to the metadata information
  • the abnormal recovery module also records the write data operation, and the data recovery process The data is synchronized to the primary storage system 13 based on these records.
  • the abnormal recovery module In the recovery state, the abnormal recovery module is responsible for online data recovery, and can perform data service and data recovery at the same time.
  • the abnormality recovery module indicates the missing block recovery through the bitmap of the faulty storage device.
  • the exception recovery module is responsible for maintaining the update of the bitmap.
  • the abnormality recovery module may further include a third processing submodule for performing, in the recovery state, a missing block detection on the metadata obtained from the cache or from the primary storage system 13 for the read data request, if the If the metadata has a missing block, the request information is sent to the backup storage system 14 including the missing block information. After the backup storage system 14 returns the metadata, the missing block recovery operation information is constructed for the primary storage system 13 to perform data recovery; and the primary is updated. The faulty storage device bitmap of the storage system 13 returns the metadata.
  • the abnormality recovery module first retrieves its metadata cache through the third processing submodule, and if the metadata is not found, requests the primary storage system 13 for metadata, and then the secondary data.
  • the metadata obtained by the cache or the primary storage system 13 performs missing block detection. If a missing block is found, the metadata is requested from the alternate storage system 14, and the missing block information (block number, data ID, offset) is passed in the spare storage.
  • the primary storage system 13 is constructed to delete the block recovery operation information, and the primary storage system 13 restores the data to the backup storage system 14 or to the external storage system 15 based on this information.
  • the abnormality recovery module may further include a fourth processing submodule, configured to, in the recovery state, request metadata for the primary storage system 13 for the write data request, and after the metadata is obtained, if the metadata is detected If there is a missing block, the failed storage device bitmap of the primary storage system 13 is updated, and the metadata is returned.
  • the abnormality recovery module requests the metadata to the primary storage system 13 through the fourth processing submodule, and after obtaining the metadata, the fault storage is configured.
  • the standby ID detects the missing block. If there is a missing block, it directly updates the fault storage device bitmap bitmap, and then returns the request result to the metadata operation module.
  • the exception recovery module starts a background recovery thread.
  • the recovery thread selects the recovery process based on the type of device being restored. If the storage device has no read/write failure (maybe the storage device is hot swapped and plugged in again), you only need to save the data written to the backup storage system during the abnormal period to the primary storage system, and delete the rebinding element. Data cache.
  • the abnormal recovery module first retrieves its metadata cache. If the metadata cache is found, it is necessary to check whether there is data in the standby storage system. If there is data in the alternate storage system (that is, there is a re-bound metadata cache), the primary storage missing block recovery operation information is constructed, and the primary storage system restores the data to the backup storage system based on the information. After recovery, delete the re-bound metadata cache and update the faulty storage device bitma bitmap.
  • the metadata is requested from the primary storage system, and then the missing block detection is performed on the metadata obtained from the primary storage system. If a missing block is found, the metadata is requested from the standby storage system.
  • the request information includes missing block information (block number, data ID, offset), but does not include an external storage address, after the backup storage system returns the metadata, constructing the primary storage system missing block recovery operation information, the primary storage system is based on This information either restores data to the backup storage system or to an external storage system. After recovery, update the fault memory device bitmap bitmap.
  • the background recovery thread traverses the data of the primary storage system, it also traverses the write data operation recorded by the abnormal recovery module during the abnormal period, and is responsible for saving the data written in the standby storage system to the primary storage system, and then updating the fault storage device bitmap bit. Figure and delete the metadata cache.
  • the distributed file system may further include an active data management module connected between the primary storage system 13 and the metadata management unit 12 for managing data stored by the primary storage system 13.
  • the active data management module is responsible for responding to the metadata request, and is also responsible for receiving the recovery operation information and realizing the data recovery.
  • recovery operation information There are two types of recovery operation information, one having an alternate storage system address information, and one having an external storage system address information. of.
  • the active data management module restores the data block according to the recovery operation information or to the standby storage system or the external storage system.
  • the distributed file system may further include an alternate data management module connected between the backup storage system 14 and the metadata management unit 12 for managing data stored by the standby storage system 14, responding to metadata requests and data operation requests. .
  • the standby data management module is responsible for responding to the metadata request, and is also responsible for receiving the backup request and implementing data backup.
  • metadata requests There are two types of metadata requests, the first type has external storage address information, and the second type has no external storage system address.
  • the difference between the backup data management module and the two types of metadata requests is: If the secondary storage system 14 does not retrieve the element The data, when processing the first class, requests all data to the external storage system 15 and stores it, returning the stored metadata.
  • the backup storage system processes the backup request, it requests data directly from the primary storage system 13 and saves it according to the backup request.
  • the primary storage system includes a plurality of high-speed storage devices, including but not limited to a high data transfer rate SCSI hard disk, a SATA hard disk, and an SSD.
  • the active storage system is also responsible for monitoring the status of its own storage devices and reporting device events (such as device failures and device recovery).
  • the above device faults include storage device read/write failures and hot-swappable storage devices.
  • the backup storage system includes a plurality of high-speed storage devices and/or low-speed storage devices, wherein the high-speed storage devices include but are not limited to SCSI hard disks with high data transfer rates, SATA hard disks, and SSDs; and low-speed storage devices include, but are not limited to, low data transfer rates. Storage device.
  • the active data management module restores the data block according to the recovery operation information or to the standby storage system or the external storage system. That is, the recovery operation information of the spare storage system address information, the main data management module recovers the recovery operation information of the external storage system address information from the backup storage system, and the main data management module recovers the data block from the external storage system.
  • the above recovery operation information is constructed, so that the read data service is provided and the accessed data is immediately restored.
  • the recently accessed data is also the focus of most users.
  • the backup storage system In the abnormal state, when reading data, it needs to request metadata from the standby storage system, which includes the external storage address.
  • the backup storage system first The external storage system requests data (equivalent to backing up all data from the external storage system to the alternate storage system) and returns the metadata. In this way, both the read data service and the data are backed up from the external storage system to the standby storage system, and the data can be recovered from the standby storage system during recovery, thereby speeding up data recovery.
  • metadata may be requested from the alternate storage system, which does not include external storage addresses, so that if the standby storage system itself does not have the requested metadata, the alternate storage The system does not request data from the external storage storage system and the alternate storage system returns null. Then the primary storage system uses the external storage address to request data from the external storage system (only the data contained in the missing block is requested, and only the data contained in the missing block needs to be recovered when the data is recovered).
  • the distributed file system writes data to the primary storage system and uses the asynchronous backup mechanism to back up to the backup storage system without affecting the read and write performance of the high-speed device.
  • the data can be restored online, and the data is externally serviced. Automatically realize data recovery and speed up the recovery process; and no need to calculate when recovering data, even if the data is not backed up, it can be restored by external storage;
  • use the policy backup data mechanism and available external storage to obtain data without backup Partial data backup can be achieved without affecting availability; in addition, an inexpensive storage device can be used to form an alternate storage system to reduce product cost.
  • FIG. 3 is a schematic diagram of a process flow of a distributed file system in a normal state according to an embodiment of the present invention. As shown in FIG. 3, the process includes:
  • Step 1 The backup management module reads the data control information.
  • Step 2 The backup management module analyzes the read and write requests of the data control information according to the backup policy. If the policy requirements are met, the backup control information is formed and sent to the standby data management module, and the files on the primary storage system are backed up to the backup storage. On the server;
  • Step 3 The standby data management module receives the backup control request (operation type, target file path, source file path) sent by the backup management module, and uses the backup control request information according to the backup control request information. Issue a backup request according to the management module;
  • Step 4 The primary data management module receives the backup request, and reads data from the storage device in the primary storage system.
  • Step 5 The primary data management module returns data to the standby data management module
  • Step 6. The standby data management module writes the data to the storage device in the standby storage system.
  • Step 7. Return the backup status to the backup management module.
  • FIG. 4 is a schematic flowchart of a process in a distributed file system in an abnormal state and in a case of a read data request according to an embodiment of the present invention. As shown in FIG. 4, the process includes:
  • Step 1 The application sends a request for reading data to the access module.
  • Step 2 The access module issues a read metadata request to the metadata operation module.
  • Step 3 The metadata operation module forwards the read metadata request to the abnormality recovery module.
  • Step 4 The abnormality recovery module first searches for metadata in the metadata information cache, and if it finds a turn, step 6;
  • Step 5 The abnormality recovery module initiates a metadata request to the primary data management module, and the primary data management module receives the backup request, reads the metadata to the storage device in the primary storage system, and returns the metadata to the abnormality recovery module.
  • Step 6 The abnormality recovery module checks whether the metadata information returned from the metadata cache or the primary storage system has a missing block, and then initiates a metadata request to the standby storage system and carries an external backup control information (including external storage). System location, data location information), if not, return metadata information to the metadata operation module, and go to step 9;
  • Step 7 If the data is backed up in the standby storage system, the standby data management module returns the metadata, otherwise the standby data management module requests data from the external storage system according to the external backup control information, stores the obtained data in the standby storage system, and returns Metadata information;
  • Step 8 The abnormality recovery module performs a block address rebinding operation, modifies the block mapping table of the metadata of the missing block, replaces the missing block address by applying the corresponding block address on the alternate storage system, and generates the bound metadata. Cache up, return all metadata to the metadata operation module; Step 9. The metadata operation module returns the metadata to the access module.
  • Step 10 The access module initiates a data request to the corresponding primary storage system and the standby storage system according to the returned metadata information.
  • Step 11 The primary storage system and the backup storage system return data to the access module.
  • Step 12 The access module returns data to the application.
  • FIG. 5 is a schematic diagram of a process flow of a distributed file system in an abnormal state and in the case of a write data request according to an embodiment of the present invention. As shown in FIG. 5, the process includes:
  • Step 1 The application sends a request for writing data to the access module.
  • Step 2 The access module issues a read metadata request to the metadata operation module.
  • Step 3 The metadata operation module forwards the read metadata request to the abnormality recovery module.
  • Step 4 The abnormality recovery module directly initiates a metadata request to the standby storage system.
  • Step 5 The standby data management module receives the metadata request and constructs the metadata, and returns the metadata.
  • Step 6 The exception recovery module returns the metadata information to the metadata operation module.
  • Step 7 The metadata operation module returns the metadata to the access module.
  • Step 8 The access module initiates a data request to the backup storage device according to the returned metadata information.
  • Step 9 The access module writes data to the backup storage system.
  • Step 10 The access module returns a write data result to the application.
  • FIG. 6 is a schematic flowchart of a process for a distributed file system to respond to a read data request in a recovery state according to an embodiment of the present invention. As shown in FIG. 6, the process includes:
  • Step 1 The application sends a request for writing data to the access module.
  • Step 2 The access module issues a read metadata request to the metadata operation module.
  • Step 3 The metadata operation module forwards the read metadata request to the abnormality recovery module.
  • Step 4 The abnormality recovery module retrieves the metadata cache, and if not found, requests metadata from the primary storage system, and if found, jumps to the sixth Step
  • Step 5 The primary storage system receives the request metadata and returns the metadata.
  • Step 6 The abnormality recovery module checks whether there is a missing block, and if so, requests metadata from the standby storage system. If not, skips to step 11;
  • Step 7 The abnormality recovery module constructs the recovery control information and sends the information to the primary storage system according to the metadata returned by the standby storage system.
  • Step 8. The primary storage system receives the recovery control information and performs data recovery.
  • Step 9. Return the data recovery result to the abnormality recovery module.
  • Step 10 The abnormality recovery module updates the missing block bitmap bitmap that has been restored
  • Step 11 Return metadata obtained from the metadata cache or the primary storage system to the metadata operation module.
  • Step 12 The metadata operation module returns the metadata to the access module.
  • Step 13 The access module initiates a data request to the corresponding primary storage system and the standby storage system according to the returned metadata information.
  • Step 14 The primary storage system and the standby storage system return data to the access module.
  • Step 15. The access module returns data to the application.
  • FIG. 7 is a schematic diagram of a process flow of a distributed file system responding to a write data request in a recovery state according to an embodiment of the present invention. As shown in FIG. 7, the process includes:
  • Step 1 The application sends a request for writing data to the access module.
  • Step 2 The access module issues a read metadata request to the metadata operation module.
  • Step 3 The metadata operation module forwards the read metadata request to the abnormality recovery module.
  • Step 4 The abnormality recovery module requests metadata from the primary storage system.
  • Step 5 The primary storage system receives the request metadata and returns the metadata
  • Step 6 The abnormality recovery module checks whether there is a missing block, and if so, updates the bitmap block bitmap of the missing block that has been restored, and sets the bitmap corresponding to the missing block to 1;
  • Step 7. Return the metadata from the metadata to the operation module.
  • FIG. 8 is a schematic diagram of a processing flow of a data recovery process of a distributed file system in a system recovery state according to an embodiment of the present invention. As shown in FIG. 8, the process includes: Step 1. The background data recovery thread searches the metadata cache for the metadata of the data to be restored, and if not found, skips to step 6;
  • Step 2 If the metadata cache is found, the background data recovery thread checks whether there is data on the standby storage system. If there is no data on the standby storage system, skip to step 11;
  • Step 3 If there is data on the standby storage system, the background data recovery thread constructs the primary storage missing block recovery operation information and sends the operation information to the primary storage system;
  • Step 4 The primary storage system receives the missing block recovery operation information and executes, restores the backup storage system data to the missing block, and returns the missing block recovery operation result;
  • Step 5 The background data recovery thread deletes the re-bound metadata cache and jumps to step 11; Step 6. If the metadata is not found in the metadata cache, the background data recovery thread requests metadata from the primary storage system. ;
  • Step 7. Perform a missing block check on the returned metadata. If there is no missing block, skip to step 11; Step 8. If there is a missing block, the background data recovery thread requests to restore data to the standby storage system; Step 9, if the 8th If the backup is successful, skip to step 11;
  • Step 10 If the backup in step 8 fails, the background data recovery thread requests to restore data to the external storage system.
  • Step 11 Update the fault memory device bitmap bitmap, and the data recovery is completed.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

La présente invention porte sur un système de fichier distribué, comprenant un module d'accès (11) pour le système de fichiers distribué, une unité de gestion de métadonnées (12), un système mémoire principal (13), un système mémoire de secours (14) et un système mémoire externe (15). Parmi ceux-ci, le module d'accès (11), l'unité de gestion de métadonnées (12), le système mémoire principal (13) et le système mémoire de secours (14) sont reliés les uns aux autres par l'intermédiaire d'un bus système, et le système mémoire externe (15) est relié au système mémoire principal (13) et au système mémoire de secours (14) par l'intermédiaire d'un réseau. Dans le système de fichiers distribué de la présente invention, par l'écriture de données dans le système mémoire principal (13) et la sauvegarde de celles-ci dans le système mémoire de secours (14) au moyen d'un mécanisme de sauvegarde asynchrone, les performances de lecture-écriture d'un équipement à grande vitesse ne sont pas affectées, une récupération de données en ligne peut être réalisée, et une récupération de données peut être automatiquement mise en œuvre au cours d'une opération de service externe de données, accélérant ainsi le processus de récupération.
PCT/CN2011/079685 2010-12-08 2011-09-15 Système de fichiers distribué Ceased WO2012075845A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201010587235.7 2010-12-08
CN2010105872357A CN102024044B (zh) 2010-12-08 2010-12-08 分布式文件系统

Publications (1)

Publication Number Publication Date
WO2012075845A1 true WO2012075845A1 (fr) 2012-06-14

Family

ID=43865341

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/079685 Ceased WO2012075845A1 (fr) 2010-12-08 2011-09-15 Système de fichiers distribué

Country Status (2)

Country Link
CN (1) CN102024044B (fr)
WO (1) WO2012075845A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20250094295A1 (en) * 2021-11-16 2025-03-20 Netapp, Inc. Use of cluster-level redundancy within a cluster of a distributed storage management system to address node-level errors

Families Citing this family (26)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102024044B (zh) * 2010-12-08 2012-11-21 华为技术有限公司 分布式文件系统
CN103095767B (zh) * 2011-11-03 2019-04-23 中兴通讯股份有限公司 分布式缓存系统及基于分布式缓存系统的数据重构方法
CN103220162B (zh) * 2012-01-19 2016-08-31 百度在线网络技术（北京）有限公司 基于hdfs的scsi容错优化方法及装置
GB2503016B (en) * 2012-06-14 2017-10-04 Draeger Safety Uk Ltd A telemetry monitoring system and a data recovery method for a telemetry monitoring system
CN103516736A (zh) * 2012-06-20 2014-01-15 中兴通讯股份有限公司 分布式缓存系统的数据恢复方法及装置
CN102867035B (zh) * 2012-08-28 2015-09-23 浪潮(北京)电子信息产业有限公司 一种分布式文件系统集群高可用方法和装置
CN102890716B (zh) * 2012-09-29 2017-08-08 南京中兴新软件有限责任公司 分布式文件系统和分布式文件系统的数据备份方法
CN103049390B (zh) * 2012-12-14 2016-03-09 华为技术有限公司 应用元数据的数据处理方法及存储系统
CN103902349B (zh) * 2012-12-27 2017-05-31 中国移动通信集团江西有限公司 一种虚拟化平台存储管理服务器及其管理方法
CN103167026B (zh) * 2013-02-06 2016-05-18 数码辰星科技发展（北京）有限公司 一种云存储环境数据处理方法、系统及设备
CN103207894A (zh) * 2013-03-14 2013-07-17 深圳市知正科技有限公司 一种多路实时视频数据存储系统及其进行缓存控制的方法
CN103347086B (zh) * 2013-07-11 2016-06-29 南京大学 基于分布式协商算法的协同内核构建方法
CN105556462A (zh) * 2013-07-29 2016-05-04 惠普发展公司，有限责任合伙企业 写入文件和文件元数据
CN103473184B (zh) * 2013-08-01 2016-08-10 记忆科技(深圳)有限公司 文件系统的缓存方法及系统
CN104657392B (zh) * 2013-11-25 2020-02-11 腾讯科技（深圳）有限公司 一种实现检索异常还原的方法及装置
CN104135539B (zh) * 2014-08-15 2018-03-16 华为技术有限公司 数据存储方法、sdn控制器和分布式网络存储系统
CN104202387B (zh) * 2014-08-27 2017-11-24 华为技术有限公司 一种元数据恢复方法及相关装置
CN105915600A (zh) * 2016-04-13 2016-08-31 乐视控股（北京）有限公司 基于cdn网络系统的数据写入方法及cdn网络系统
CN108108422A (zh) * 2017-12-15 2018-06-01 郑州云海信息技术有限公司 一种Ceph文件系统的元数据获取方法、装置及介质
CN110096220B (zh) 2018-01-31 2020-06-26 华为技术有限公司 一种分布式存储系统、数据处理方法和存储节点
CN108388604B (zh) * 2018-02-06 2022-06-10 平安科技（深圳）有限公司 用户权限数据管理装置、方法及计算机可读存储介质
CN109327539A (zh) * 2018-11-15 2019-02-12 上海天玑数据技术有限公司 一种分布式块存储系统及其数据路由方法
CN110659157A (zh) * 2019-08-30 2020-01-07 安徽芃睿科技有限公司 一种无损恢复的分布式多语种检索平台及其方法
CN111026432A (zh) * 2019-12-06 2020-04-17 中国建设银行股份有限公司 一种大数据处理平台、平台构建方法和存储介质
CN112532525B (zh) * 2020-11-25 2022-11-25 北京金山云网络技术有限公司 设备恢复服务的处理方法、装置和系统
JP7232281B2 (ja) * 2021-03-29 2023-03-02 株式会社日立製作所 ストレージシステム及びストレージシステムの制御方法

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1418422A (zh) * 2000-02-04 2003-05-14 里逊·Com股份有限公司 用于分布式媒体网络和元数据服务器的系统
CN101539873A (zh) * 2009-04-15 2009-09-23 成都市华为赛门铁克科技有限公司 数据恢复的方法、数据节点及分布式文件系统
CN102024044A (zh) * 2010-12-08 2011-04-20 华为技术有限公司 分布式文件系统

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6728849B2 (en) * 2001-12-14 2004-04-27 Hitachi, Ltd. Remote storage system and method
WO2004047078A2 (fr) * 2002-11-20 2004-06-03 Filesx Ltd. Sauvegarde de memoire rapide et recuperation rapide de donnees (fbsrd)
CN1955939A (zh) * 2006-10-13 2007-05-02 清华大学 基于虚拟内存盘的备份与恢复方法
CN101394424B (zh) * 2008-10-27 2011-11-09 中国科学院计算技术研究所 一种磁盘级网络数据备份的系统及方法
CN101408855B (zh) * 2008-11-07 2010-06-02 北京威视数据系统有限公司 连续数据保护系统在远程备份设备临时异常时的保护方法
CN101436151B (zh) * 2008-12-01 2012-01-11 成都索贝数码科技股份有限公司 基于文件系统的数据实时备份方法及其系统
CN101436149B (zh) * 2008-12-19 2010-06-30 华中科技大学 磁盘阵列数据重建方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1418422A (zh) * 2000-02-04 2003-05-14 里逊·Com股份有限公司 用于分布式媒体网络和元数据服务器的系统
CN101539873A (zh) * 2009-04-15 2009-09-23 成都市华为赛门铁克科技有限公司 数据恢复的方法、数据节点及分布式文件系统
CN102024044A (zh) * 2010-12-08 2011-04-20 华为技术有限公司 分布式文件系统

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20250094295A1 (en) * 2021-11-16 2025-03-20 Netapp, Inc. Use of cluster-level redundancy within a cluster of a distributed storage management system to address node-level errors

Also Published As

Publication number Publication date
CN102024044B (zh) 2012-11-21
CN102024044A (zh) 2011-04-20

Similar Documents

Publication Publication Date Title
CN102024044B (zh) 分布式文件系统
US12267252B2 (en) Shared storage model for high availability within cloud environments
US12073091B2 (en) Low overhead resynchronization snapshot creation and utilization
US11748208B2 (en) Persistent memory architecture
US7313721B2 (en) Apparatus and method for performing a preemptive reconstruct of a fault-tolerant RAID array
TWI450087B (zh) 複數個磁碟陣列系統之資料儲存方法及資料儲存系統
US11714782B2 (en) Coordinating snapshot operations across multiple file systems
CN102110154B (zh) 一种集群文件系统中文件冗余存储方法
CN103942112A (zh) 磁盘容错方法、装置及系统
US12001724B2 (en) Forwarding operations to bypass persistent memory
US8117493B1 (en) Fast recovery in data mirroring techniques
WO2017097233A1 (fr) Procédé de tolérance aux anomalies pour une charge de stockage de données et système iptv
US10915405B2 (en) Methods for handling storage element failures to reduce storage device failure rates and devices thereof
US20250004893A1 (en) Mediator assisted switchover between clusters
CN116204137B (zh) 基于dpu的分布式存储系统、控制方法、装置及设备
US8276017B2 (en) Process, apparatus, and program for system management
US12061528B2 (en) Storage system and storage system control method
US20250238335A1 (en) Storage system and failure handling method in storage system
US20260050525A1 (en) Multi-Controller Drive Recovery
US10331358B1 (en) High performance and low-latency replication using storage mirroring
CN121326870A (zh) 一种数据恢复方法、数据恢复装置以及计算设备集群

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 11847286

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 11847286

Country of ref document: EP

Kind code of ref document: A1