WO2014153931A1 - Procédé et dispositif de stockage de fichier, client d'accès et système de serveur de métadonnées - Google Patents

Procédé et dispositif de stockage de fichier, client d'accès et système de serveur de métadonnées Download PDF

Info

Publication number
WO2014153931A1
WO2014153931A1 PCT/CN2013/083689 CN2013083689W WO2014153931A1 WO 2014153931 A1 WO2014153931 A1 WO 2014153931A1 CN 2013083689 W CN2013083689 W CN 2013083689W WO 2014153931 A1 WO2014153931 A1 WO 2014153931A1
Authority
WO
WIPO (PCT)
Prior art keywords
file
copy
files
location information
file access
Prior art date
Application number
PCT/CN2013/083689
Other languages
English (en)
Chinese (zh)
Inventor
胡剑华
朱鹏
俞超
Original Assignee
中兴通讯股份有限公司
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 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2014153931A1 publication Critical patent/WO2014153931A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]

Definitions

  • Embodiments of the present invention relate to the field of cloud storage, and in particular, to a file storage method, apparatus, access client, and metadata server system. Background technique
  • DFS Distributed File System
  • a distributed File System is to divide files into several CHUNKs and store multiple copies on different servers.
  • DFS must be able to Support for the storage of files of various sizes, as small as a few bytes of files, up to tens of gigabytes should be supported, and storage performance should not be different, but according to the existing mechanism, no matter how small the file
  • the file access server stores it separately in a single copy on disk, which unnecessarily increases disk fragmentation when the file access server has more than one such file. Summary of the invention
  • the embodiment of the invention provides a file storage method, which is applied to a metadata server system, and the method includes:
  • the at least two files are respectively stored to offset positions of the at least two files in the copy.
  • the offset positions of the at least two files in the copy respectively include:
  • the method further includes:
  • the embodiment of the present invention further provides a file storage method, which is applied to a file access client, and the method includes:
  • the storage location information includes offset location information and the replica location information of each of the at least two files in one copy;
  • the storing Position information is determined by the metadata server system; interacting with the file access server according to the storage location information, causing the file access server to store the at least two files to the at least two files respectively in the In the copy Offset position.
  • the offset positions of the at least two files in the copy respectively include:
  • the interacting with the file access server according to the storage location information, so that the offset location in the copy includes:
  • the method further includes:
  • the embodiment of the invention further provides a file storage device, which is applied to a metadata server system, and the device includes:
  • a determining module configured to determine storage location information of the at least two files; wherein the storage location information includes offset location information and the replica location information of each of the at least two files in one copy;
  • the sending module is configured to send the storage location information to the file access client, so that the file access client interacts with the file access server according to the storage location information to make an offset position in the copy.
  • the sending module includes:
  • a sending unit configured to send storage location information to the file access client, so that the file access client interacts with the file access server according to the storage location information, so that the file access server sets the at least two files Write a cache block and write the data in the cache block to the copy after the file is written, and set the data after the write is completed.
  • the embodiment of the present invention further provides a file storage device, which is applied to a file access client, and the device includes:
  • a receiving module configured to receive storage location information of at least two files sent by the metadata server system, where the storage location information includes offset location information and the replica location of each of the at least two files in one copy Information; the storage location information is determined by the metadata server system;
  • the interaction module is configured to interact with the file access server according to the storage location information, each offset position in the copy.
  • the interaction module includes: An interaction unit configured to: for each of the at least two files, according to the copy location information and offset location information of each file in the replica, each file is cached Writing a shared memory page to the cache block of the file access server, enabling the file access server to write data in the cache block to the copy and the data after the shared memory page is written Each file described after the completion of writing is stored at an offset position of each of the files in the copy.
  • Embodiments of the present invention also provide a metadata server system including the file storage device described above.
  • Embodiments of the present invention also provide a file access client including the file storage device described above.
  • the embodiment of the present invention has at least the following beneficial effects: Supporting different files to be stored in the same copy, thereby avoiding file access server storage compared with different files in the prior art that cannot be stored in the same copy. An unnecessary increase in the fragmentation of the medium.
  • FIG. 1 is a flow chart of steps of a file storage method according to Embodiment 1 of the present invention
  • FIG. 2 is a flowchart of steps of another file storage method according to Embodiment 2 of the present invention
  • FIG. 3 is a small file of a preferred embodiment. Schematic diagram of polymerization
  • FIG. 4 is a schematic flow chart of a small file aggregation write of a preferred embodiment
  • FIG. 5 is a schematic flow chart of a small file aggregation read of a preferred embodiment. detailed description
  • a first embodiment of the present invention provides a file storage method, where the method includes the following steps: Step 101: Determine storage location information of at least two files, where the storage location information includes offset location information and replica location information of each of the at least two files in one copy; Step 102, send a storage location to the file access client The information causes the file access client to interact with the file access server according to the storage location information, so that the file access server stores the at least two files respectively to the offset positions of the two files in the copy.
  • This method is applied to a metadata server system.
  • the copy is located on the storage medium of the file access server.
  • the storage medium is, for example, a magnetic disk.
  • the copy location information includes: File access server ID and storage media ID in the file access server.
  • the file access server identifier is, for example: IP of the file access server: 10.47.107.111; storage medium identifier such as: IP of the file access server: 10.47.107.111.
  • the sum of the sizes of the at least two files is not greater than the copy size.
  • each of the at least two files is no larger than the shared cache page (PAGE) size in the file access client.
  • PAGE shared cache page
  • the copy location corresponds to the copy handle.
  • the copy location is determined by the metadata server system according to the copy handle; the copy handle is the file name of the first file in the at least two files by the metadata server system.
  • the first file is any one of at least two files; or, in consideration of the file access client sending an open file request to each of the at least two files to the metadata server system, the first file is metadata The file corresponding to the open file request received by the server system from the file access client for the first time.
  • the metadata server system comprises a metadata management server and a plurality of metadata storage servers, wherein the copy handle is specifically allocated by the metadata management server, and the copy location is specifically determined by the first metadata storage server of the plurality of metadata storage servers. Determining, according to the copy handle, the first metadata storage server is from the plurality of elements by the metadata management server according to the file name of the first file The data storage server is selected.
  • At least two files have different offset positions in the copy.
  • the offset position here refers to the position where the file is stored in the copy, and the starting position in the position is coincident or offset from the starting position of the copy.
  • the offset position information of each of the at least two files in the copy includes: offset size information between the start position of each file stored in the copy and the start position of the copy, for example, the number of bytes or The number of bits, the size and number of PAGEs, or the number of PAGEs in which the size of each file in at least two files is not larger than the size of the PAGE, and so on.
  • the offset position information of each of the at least two files in the copy can be determined as follows:
  • the first method is a timing-based approach.
  • the metadata server system considering that the metadata server system sequentially receives the request for opening the file from the file access client, the number of these open file requests is the same as the number of at least two files, and the open file requests and at least two files— - Correspondingly, the metadata server system assigns an offset position to the corresponding file in order from the start position of the copy position in the order in which the file request is received.
  • the offset position of the corresponding file allocation for the first received open file is the starting position of the copy position, and the offset position and copy of the corresponding file allocation are requested for the second received open file request.
  • the starting position differs by a shared cache page size
  • the offset position of the corresponding file allocation for the third received open file request differs from the starting position of the copy by two shared cache page sizes, and so on.
  • the second method is based on the serial number in the file name.
  • the respective offset positions of the plurality of files are assigned according to the sequence number included in the file name in the predetermined size order.
  • the metadata server system receives three open file requests from the file access client, Corresponding to the file with the file name 010, the file with the file name 001, and the file with the file name 003, the offset positions are assigned to the three files in the order of the serial number, which is the file with the file name 001.
  • the assigned offset position is the start position of the copy position
  • the offset position assigned to the file with the file name 003 differs from the start position of the copy by a shared cache page size
  • the offset position assigned to the file with the file name 010 There are two shared cache page sizes that differ from the starting position of the copy.
  • the metadata server system receives three open file requests from the file access client, corresponding to the file with the file name 112, the file with the file name 111, and the file with the file name 113, according to the serial number from large to small.
  • the order of the three files is offset
  • the offset position assigned to the file with the file name 113 is the start position of the copy position
  • the offset position assigned to the file with the file name 112 and the start position of the copy.
  • the difference is a shared cache page size
  • the offset position assigned to the file with the file name 111 differs from the start position of the copy by two shared cache page sizes.
  • Mode 2 is more suitable for scenes with fixed file names.
  • the file name has a series of consecutive serial numbers.
  • the system can put 3 files into one copy.
  • File 001, file 002, and file 003 will be put together, and the offset positions are respectively For no offset, one shared cache page size, two shared cache page sizes; for example, file 010, file 011, and file 012 are also in the same copy, offset positions are no offset, one shared cache page size, Two shared cache page sizes.
  • the file access server stores at least two files respectively.
  • the offset locations of at least two files in the copy include:
  • One, in order to access the client to file access service with existing files The file writing mechanism of the device is compatible, thereby reducing the implementation cost and complexity of the embodiment of the present invention, and interacting with the file access server according to the storage location information, so that the file access server stores at least two files to at least two files respectively.
  • the offset locations in the copy include:
  • the shared memory page in which each file is cached is written to the cache block of the file access server, so that the file is accessed. After the server finishes writing, the data in the cache block is written into the copy, and after the data is written, each file is stored at the offset position of each file in the copy.
  • a cache block in which shared memory pages having different files are written is different, and different cache blocks are written in the copy. The time is different.
  • the cache blocks in which the shared memory pages in which different files are cached are written into the same cache block.
  • the method further includes: recording a file name, a copy location information, and an offset of each of the at least two files in each of the at least two files Correspondence of location information;
  • the first information includes the copy location information and the offset location information of the file to be read in the copy;
  • Step 201 Receive storage location information of at least two files sent by the metadata server system, where the storage location information includes offset location information and replica location information of each of the at least two files in one copy; storing location information by metadata Server system determination;
  • Step 202 interacting with the file access server according to the storage location information, so that the file access service
  • the server stores at least two files in an offset position of each of the at least two files in the copy. This method is applied to the file access client.
  • the file access server stores the at least two files separately to the offset positions of the at least two files in the copy respectively:
  • Enabling the file access server to write at least two files to one cache block and after the at least two files are written the data in the cache block is written into the copy, and at least two files are respectively stored after the data is written.
  • the offset position in at least two files in the copy is
  • the file access server in order to be compatible with the file writing mechanism of the existing file access client to the file access server, thereby reducing the implementation cost and complexity of the embodiment of the present invention, according to the storage location information, and the file access server Interacting, causing the file access server to store at least two files separately to offset positions of at least two files in the copy respectively:
  • the shared memory page in which each file is cached is written to the cache block of the file access server, so that the file is accessed.
  • the server writes the data in the cache block to the copy and each file is stored in the offset position of each file in the copy after the data is written.
  • the method further includes: sending a request to the metadata server system, where the file name of the file to be read is included; and receiving the first information sent by the metadata server system
  • the first information includes copy location information and offset location information of the file to be read in the copy
  • the first information is determined by the metadata server system according to file name, copy location information, and at least file name of each of the at least two files
  • the correspondence between the offset position information of each of the two files in the copy and the file name of the file to be read are determined;
  • the correspondence is recorded by the metadata server system;
  • the file access server According to the first information, interacting with the file access server, reading the corresponding first file from the file access server.
  • the File Access Client (FAC):
  • the DFS-oriented application provides an interface calling service similar to the standard file system, and the read and write data for the application layer is the page (PAGE) size. Managed.
  • Metadata server system It is responsible for managing the metadata information such as file name and copy information of all DFS files, exists in the database, and provides metadata write and query operations to the file access client.
  • the metadata server system includes a metadata management server and a plurality of metadata storage servers.
  • File Access Server responsible for interacting with its own storage medium in the cache block unit, and performing read and write operations on the cache block.
  • the FAS manages the data in the size of the cache block (BLK);
  • the file accesses the client's data read and write request, reads the data from the storage medium and returns it to the file access client; reads the data from the file access client and writes the storage medium;
  • Storage media Generally, it is a normal SCIC disk or SATA disk. Where CHUNK is actually stored, CHUNK is a minimum of BLK size, the maximum value can be set, and the size is increased by BLK size.
  • Each of the at least two files is a small file.
  • the small file here means that the size is not greater than A PAGE size file.
  • the size of the PAGE can be set.
  • a small file corresponds to a PAGE, a BLK, corresponding to a copy on the disk; and in the preferred embodiment, after the aggregation, multiple PAGEs may correspond to the same BLK, and multiple PAGEs correspond to the same copy.
  • the offset size information between the starting position where the file is stored in the copy and the starting position of the copy is the number of PAGEs.
  • the following takes the degree of aggregation as 3 as an example, and illustrates the small file aggregation process in conjunction with FIG. As shown in FIG. 3, at least two files include a file FILE#001, a file FILE#002, and a file FILE#003.
  • the FAC When creating the file FILE#001, the FAC writes the PAGE#1 carrying FILE#001 to the first 1/3 buffer space of a BLK (FAS_BLK#1) of the FAS; after the PAGE#1 is written, When the file FILE#002 is created, the FAC writes the PAGE#2 carrying FILE#002 to the second 1/3 buffer space of FAS_BLK#1; after the PAGE#2 is written, when the file FILE#003 is created, The FAC writes PAGE#3 carrying FILE#003 to the third 1/3 buffer space of FAS_BLK#1.
  • the FAS brushes its own cache block FAS_BLK#1 ie, the data in FAS_BLK#1 is written to a copy on the disk FAS_BLK#1-CHKFILE.
  • the file FILE#001, the file FILE#002 and the file FILE#003 are stored in the respective offset positions in the copy, wherein the file FILE#001 is stored in the copy at the starting position of the copy.
  • the starting position, the corresponding offset position is 0; the starting position of the file FILE#002 in the copy is different from the starting position of the copy by a PAGE size, and the corresponding offset position is 1; File FILE#003 The starting position stored in the copy differs from the starting position of the copy by two PAGE sizes, and the corresponding offset position is 2.
  • the preferred embodiment stores a certain number of files smaller than one PAGE size on the same BLK on the file access server, and stores the same on the disk.
  • CHUNK on the one hand, compared with the prior art, the number of CHUNKs stored on the disk is greatly reduced, the disk fragmentation is effectively reduced, and a certain disk space is saved.
  • the overall read and write performance of the disk is improved; on the other hand, the reading and writing of multiple small files at the application layer only needs to occur once for the disk 10, which reduces the limited IOPS capability of the disk compared with the disk 10 that occurs in the prior art.
  • the limitation of IOPS on the application layer reads and writes, which in turn increases the IOPS of the application layer.
  • the copy location information of the CHUNK file in the metadata that is, the file access server where the copy is located and the volume information of the file are also greatly reduced.
  • the bitmap information in the metadata storage server may be added with a bitmap of the degree of aggregation, and the PAGE number information corresponding to the file is recorded.
  • the offset of the file FILE#001 is 0, the bitmap is 001 (binary); the offset of the file FILE#002 is 1, and the bitmap is 010 (binary); file FILE# The offset of 002 is 2 and the bitmap is 100 (binary).
  • the offset of the file corresponding to the number of PAGEs is 0, and the bitmap is 00000001 (binary); the offset of the file corresponding to the number of PAGEs is 3, and the bitmap is 00001000 (binary) ; The offset of the file corresponding to the number of PAGEs is 7 and the bitmap is 10000000 (binary).
  • the page size is 32k
  • the blk size is 256k.
  • a file file003 is newly written, and the size is lk, which satisfies the condition of small file aggregation (the size is smaller than one page size), and the metadata management server opens the file.
  • the offset is confirmed based on the first few small files.
  • a small file aggregation write process includes:
  • Step 401 The application layer initiates an open file request to the file access client.
  • Step 402 The file access client initiates an open file request (with a file name and a creation flag) to the metadata management server, and the database determines, according to the file name, the metadata storage server to which the file belongs and the copy handle to which the file belongs and the copy Offset position information. Multiple files within the same copy belong to the same metadata storage server.
  • Step 403 After the file access client receives the response from the metadata management server, if the given copy handle is not 0, the copy handle and the offset location information are recorded in the file management global structure of the file access client.
  • Step 404 The file access client opens the file to the corresponding metadata storage server, and the metadata storage server replies to the file access client, and the file access client responds to the application layer after receiving the response.
  • Step 405 The application layer sends a write request to the file access client. After receiving the write request, the file access client first determines whether the copy handle recorded in the global structure of the file management is 0. If not, the copy handle is used to The metadata storage server sends a request for obtaining a copy location, and if it is 0, the request for obtaining the copy location is sent to the metadata storage server by using the file identifier generated by the file identifier plus the calculated copy number of the written page.
  • Step 406 After receiving the request, the metadata storage server obtains the copy location from the database and returns it to the file access client.
  • Step 407 After receiving the copy location of the metadata storage server, the file access client writes the data of the application layer to the shared memory page of the file access client, and responds to the application layer.
  • Step 408 the file access client's write thread writes the shared memory page to the file access server according to the copy handle and the offset location information.
  • the file access client can reuse the existing mechanism for writing file data to the file access server to write different small file data.
  • the FAC only needs to write data of different small files as data buffered by the same file in different PAGEs. Therefore, the preferred embodiment does not need to modify the existing file access server, which saves the upgrade cost of the cloud service system.
  • the cache block For the file access server, if the cache block is missed, a new cache block is requested, and the data page is written into the buffer block. The data of the multiple files is written to the same cache block before being flushed into the disk, and finally stored in the buffer block. In the same copy on the disk.
  • FIG. 5 is a schematic flowchart of a small file aggregation read according to a preferred embodiment.
  • the small file aggregation read process includes the following steps:
  • Step 501 The application layer initiates an open file request to the file access client.
  • Step 502 The file access client initiates an open file request to the metadata management server, and the database determines, according to the file name, the metadata storage server to which the file belongs, and the copy to which the file belongs and the offset location information in the copy. Multiple files within the same copy belong to the same metadata storage server.
  • Step 503 After the file access client receives the response from the metadata storage server, if the given copy handle is not 0, the copy handle and the offset are recorded in the file management global structure.
  • Step 504 The file access client opens the file on the metadata storage server, and the metadata storage server responds to the file access client, and the file access client responds to the application layer after receiving the response.
  • Step 505 The application layer sends a read request to the file access client. After receiving the read request, the file access client first determines whether the copy handle recorded in the global structure of the file management is 0. If not, the copy handle is used to The metadata storage server sends a request for obtaining a copy location, and if it is 0, the request for obtaining the copy location is sent to the metadata storage server by using the file identifier generated by the file identifier plus the calculated copy number of the written page.
  • Step 506 After receiving the request, the metadata storage server obtains the copy location information from the database and returns the file to the file access client.
  • Step 507 After receiving the copy location information of the metadata storage server, the file access client first reads the shared memory of the file access client according to the copy location information and the offset location information, and determines whether there is any corresponding to the offset location information.
  • PAGE hit returns the file in the PAGE to the application layer, otherwise, continue to read to the file access server cache block, hit returns, otherwise, go to disk to read the corresponding copy, a copy of the data stored in multiple files, read One cache block data, the next time you read another file, you may directly hit the cache, no need to go to disk read, where the read data to the cache block is always read at the beginning of the cache block.
  • Step 508 The file access client reads the cache block data read by the disk into the cache of the file access server, and reads the PAGE corresponding to the offset location information into the shared memory of the file access client, and returns it to the application layer.
  • the existing file access server since the file access client reads the small file in the manner of reading the PAGE, the existing file access server does not need to be modified, which saves the upgrade cost of the cloud service system.
  • Step 509 the application layer sends a close request, and the file access client responds.
  • the preferred embodiment is for an application scenario in which small files are stored more or only small files are stored.
  • a third embodiment of the present invention provides a file storage device, which is applied to a metadata server system, where the device includes:
  • a determining module configured to determine storage location information of at least two files; wherein the storage location information includes offset location information and replica location information of each of the at least two files in one copy;
  • the sending module is configured to send the storage location information to the file access client, so that the file access client interacts with the file access server according to the storage location information, so that the file access server stores at least two files respectively into at least two files respectively in the copy The offset position in .
  • the sending module includes:
  • the sending unit is configured to send the storage location information to the file access client, so that the file access client interacts with the file access server according to the storage location information, so that the file access server writes at least two files into one cache block and at least two After the file is written, the cache block will be The data in the write is written in the copy, and at least two files are respectively stored in the offset position of each of the at least two files in the copy after the data is written.
  • the third embodiment of the present invention is an apparatus embodiment, which corresponds to the first embodiment of the present invention (which is a method embodiment), and the part that is not described in detail in the third embodiment of the present invention is related to the first embodiment of the present invention. Part of the description can be, in order to save space, no longer repeat them here.
  • the determining module in the third embodiment of the present invention may be implemented by a central processing unit of the metadata server system.
  • CPU Central Processing Unit
  • processor MPU, Micro Processing Unit
  • DSP digital signal processor
  • the fourth embodiment of the present invention provides another file storage device, which is applied to a file access client, and the device includes:
  • a receiving module configured to receive storage location information of at least two files sent by the metadata server system, where the storage location information includes offset location information and copy location information of each of the at least two files in one copy;
  • the metadata server system determines;
  • the interaction module is configured to interact with the file access server according to the storage location information, so that the file access server stores the at least two files separately to an offset position of each of the at least two files in the copy.
  • the interaction module includes:
  • the interaction unit is configured to write, to each of the at least two files, the shared memory page in which each file is cached to the file access server cache according to the copy location information and the offset location information of each file in the copy Block, after the file access server writes the shared memory page, writes the data in the cache block to the copy and stores each file in each file after the data is written.
  • the offset position of the file in the copy is configured to write, to each of the at least two files, the shared memory page in which each file is cached to the file access server cache according to the copy location information and the offset location information of each file in the copy Block
  • the fourth embodiment of the present invention is an apparatus embodiment, and corresponds to the second embodiment of the present invention (which is a method embodiment), and the parts that are not described in detail in the fourth embodiment of the present invention refer to the first and second embodiments of the present invention. The description of the relevant part is not repeated here.
  • the determining module in the fourth embodiment of the present invention may be implemented by the file accessing the CPU, the MPU or the DSP of the client; the interaction module and the interaction unit in the sending module may be implemented by the chip having the interactive function in the file access client.
  • a fifth embodiment of the present invention provides a metadata server system.
  • the metadata server system includes a file storage device according to Embodiment 3 of the present invention.
  • the sixth embodiment of the present invention provides a file access client, and the file access client includes another file storage device provided in Embodiment 4 of the present invention.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

L'invention concerne un procédé et un dispositif de stockage de fichier, un client d'accès et un système de serveur de métadonnées. Le procédé consiste à : déterminer des informations d'emplacement de stockage concernant au moins deux fichiers, les informations d'emplacement de stockage comprenant des informations d'emplacement décalé respectif concernant les au moins deux fichiers dans une copie et des informations d'emplacement concernant la copie ; et envoyer les informations d'emplacement de stockage à un client d'accès à un fichier pour permettre au client d'accès à un fichier d'interagir avec un serveur d'accès à un fichier selon les informations d'emplacement de stockage et permettre au serveur d'accès à un fichier de stocker respectivement les au moins deux fichiers dans les emplacements décalés respectifs des au moins deux fichiers dans la copie. Les modes de réalisation de la présente invention évitent l'augmentation inutile de fragments d'un support de stockage du serveur d'accès à un fichier.
PCT/CN2013/083689 2013-03-27 2013-09-17 Procédé et dispositif de stockage de fichier, client d'accès et système de serveur de métadonnées WO2014153931A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201310102382.4 2013-03-27
CN201310102382.4A CN104079600B (zh) 2013-03-27 2013-03-27 文件存储方法、装置、访问客户端及元数据服务器系统

Publications (1)

Publication Number Publication Date
WO2014153931A1 true WO2014153931A1 (fr) 2014-10-02

Family

ID=51600642

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2013/083689 WO2014153931A1 (fr) 2013-03-27 2013-09-17 Procédé et dispositif de stockage de fichier, client d'accès et système de serveur de métadonnées

Country Status (2)

Country Link
CN (1) CN104079600B (fr)
WO (1) WO2014153931A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105141685A (zh) * 2015-08-18 2015-12-09 浪潮(北京)电子信息产业有限公司 文件读写系统及其元数据存储器和文件读写方法和装置

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104331428B (zh) * 2014-10-20 2017-07-04 暨南大学 一种小文件和大文件的存储及访问方法
CN108733761B (zh) 2014-12-27 2021-12-03 华为技术有限公司 一种数据处理方法装置及系统
CN106911743B (zh) * 2015-12-23 2019-03-26 中兴通讯股份有限公司 小文件的写聚合、读聚合方法及系统和客户端
CN107451070B (zh) * 2016-06-01 2020-08-04 腾讯科技（深圳）有限公司 一种数据的处理方法和服务器
CN106250212A (zh) * 2016-07-29 2016-12-21 努比亚技术有限公司 资源访问方法及装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101167047A (zh) * 2005-04-22 2008-04-23 微软公司 本地缩略图高速缓存
US8095577B1 (en) * 2008-03-31 2012-01-10 Emc Corporation Managing metadata
CN102707900A (zh) * 2011-03-11 2012-10-03 微软公司 虚拟盘存储技术
CN102855239A (zh) * 2011-06-28 2013-01-02 清华大学 一种分布式地理文件系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101167047A (zh) * 2005-04-22 2008-04-23 微软公司 本地缩略图高速缓存
US8095577B1 (en) * 2008-03-31 2012-01-10 Emc Corporation Managing metadata
CN102707900A (zh) * 2011-03-11 2012-10-03 微软公司 虚拟盘存储技术
CN102855239A (zh) * 2011-06-28 2013-01-02 清华大学 一种分布式地理文件系统

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105141685A (zh) * 2015-08-18 2015-12-09 浪潮(北京)电子信息产业有限公司 文件读写系统及其元数据存储器和文件读写方法和装置

Also Published As

Publication number Publication date
CN104079600A (zh) 2014-10-01
CN104079600B (zh) 2018-10-12

Similar Documents

Publication Publication Date Title
US10782880B2 (en) Apparatus and method for providing storage for providing cloud services
US10346081B2 (en) Handling data block migration to efficiently utilize higher performance tiers in a multi-tier storage environment
CN106547476B (zh) 用于数据存储系统的方法和装置
US8504797B2 (en) Method and apparatus for managing thin provisioning volume by using file storage system
US11397668B2 (en) Data read/write method and apparatus, and storage server
US9182912B2 (en) Method to allow storage cache acceleration when the slow tier is on independent controller
US8290911B1 (en) System and method for implementing data deduplication-aware copying of data
US20180059949A1 (en) Tier based data file management
WO2014153931A1 (fr) Procédé et dispositif de stockage de fichier, client d'accès et système de serveur de métadonnées
JP2009181148A (ja) ストレージサブシステム
US20180203637A1 (en) Storage control apparatus and storage control program medium
WO2017148242A1 (fr) Procédé d'accès à un disque dur d'enregistrement magnétique à pistes superposées (smr), et serveur
US11899580B2 (en) Cache space management method and apparatus
WO2013107029A1 (fr) Procédé, dispositif et système de traitement de données basés sur une mémoire à blocs
US11226778B2 (en) Method, apparatus and computer program product for managing metadata migration
WO2023169235A1 (fr) Procédé et système d'accès à des données, dispositif et support de stockage
JP2019028954A (ja) ストレージ制御装置、プログラム、及び重複排除方法
US20220350779A1 (en) File system cloning method and apparatus
CN113360098A (zh) 一种数据写入方法、装置、系统、电子设备及存储介质
US20220129346A1 (en) Data processing method and apparatus in storage system, and storage system
JP4502375B2 (ja) ファイルシステムおよびその制御方法
CN109144403B (zh) 一种用于云盘模式切换的方法与设备
US20210224002A1 (en) Storage control apparatus and storage medium
WO2012171363A1 (fr) Procédé et équipement destinés à une opération de données dans un système de cache réparti
CN108984432B (zh) 一种处理io请求的方法及装置

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: 13880301

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: 13880301

Country of ref document: EP

Kind code of ref document: A1