CN103761256A - Maintenance system and method of branch points of remote directories - Google Patents
Maintenance system and method of branch points of remote directories Download PDFInfo
- Publication number
- CN103761256A CN103761256A CN201310743906.8A CN201310743906A CN103761256A CN 103761256 A CN103761256 A CN 103761256A CN 201310743906 A CN201310743906 A CN 201310743906A CN 103761256 A CN103761256 A CN 103761256A
- Authority
- CN
- China
- Prior art keywords
- directory
- data server
- remote
- meta data
- request
- 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.)
- Granted
Links
- 238000012423 maintenance Methods 0.000 title claims abstract description 51
- 238000000034 method Methods 0.000 title claims abstract description 33
- 238000012545 processing Methods 0.000 claims description 18
- 238000013507 mapping Methods 0.000 claims description 15
- GWAOOGWHPITOEY-UHFFFAOYSA-N 1,5,2,4-dioxadithiane 2,2,4,4-tetraoxide Chemical compound O=S1(=O)CS(=O)(=O)OCO1 GWAOOGWHPITOEY-UHFFFAOYSA-N 0.000 description 13
- 238000010586 diagram Methods 0.000 description 8
- 238000012546 transfer Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000002457 bidirectional effect Effects 0.000 description 1
- VQLYBLABXAHUDN-UHFFFAOYSA-N bis(4-fluorophenyl)-methyl-(1,2,4-triazol-1-ylmethyl)silane;methyl n-(1h-benzimidazol-2-yl)carbamate Chemical compound C1=CC=C2NC(NC(=O)OC)=NC2=C1.C=1C=C(F)C=CC=1[Si](C=1C=CC(F)=CC=1)(C)CN1C=NC=N1 VQLYBLABXAHUDN-UHFFFAOYSA-N 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 230000008531 maintenance mechanism Effects 0.000 description 1
- 239000002699 waste material Substances 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR 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
- G06F16/1824—Distributed file systems implemented using Network-attached Storage [NAS] architecture
- G06F16/183—Provision of network file services by network file servers, e.g. by using NFS, CIFS
-
- 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/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
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)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a maintenance system of branch points of remote directories. The maintenance system comprises a metadata server cluster and a client; the metadata server cluster further comprises a main metadata server and a plurality of remote metadata servers; the main metadata server is used for recording inodes of newly-built directories in a parent directory, enabling the positional information of the remote metadata servers to be embedded into the inodes and performing recording and maintenance on the positional information of the remote metadata servers; the remote metadata servers are used for creating remote sub-directories so as to achieve metadata access of the remote sub-directories; the client is used for determining a target metadata server according to the maintained positioning information of the metadata server cluster, establishing the connection with the target metadata server and sending an access request to the target metadata server. The invention also discloses a maintenance method of the branch points of the remote directories.
Description
Technical field
The present invention relates to the metadata cluster technology of cluster file system, particularly a kind of maintaining method based on crossing over the remote directory take-off point of a plurality of servers in metadata cluster.
Background technology
In large-scale cluster file system, metadata is separated with data, services has become a kind of trend.On the one hand, data access needn't pass through meta data server, but adopts out-band method DASD, thereby obtains higher data access performance; On the other hand, meta data server provides Metadata Service specially, has unloaded data access load, thereby separate unit meta data server can be supported higher client-access performance, manages more memory device, supports larger system scale expansion.Yet along with the continuous expansion of system scale, separate unit meta data server becomes the bottleneck of system for restricting expansion gradually.In order further to promote the extended capability of cluster file system, conventionally adopt many meta data servers to form meta data server cluster, to disperse metadata load, support to reach the extending transversely of cluster file system by increasing meta data server quantity.
Take catalogue as granularity, the load of some sub-directories is transferred to other meta data servers is a kind of common methods that metadata load disperses, by cluster file systems such as Lustre, pNFS, BWFS, adopted.The distribution of metadata load is in the constructive process of sub-directory, to create the mode of long-range sub-directory, the load of sub-directory metadata is transferred to other meta data server, select the meta data server outside the meta data server at parent directory place to carry out sub-directory establishment, this sub-directory is called remote directory take-off point.The storage of remote directory take-off point and access relate to the meta data server at parent directory place, meta data server and the client at the actual place of take-off point, increased system implementation complexity, especially the establishment of remote directory take-off point, access and deletion have been produced to larger impact.
Existing pNFS integrates being positioned at the name space of a plurality of subfile systems on different server by the position attribution (fs_locations) of catalogue, thereby realizes multiserver name space.In specific implementation, the index node that creaties directory respectively on the destination server that pNFS shifts in the server at parent directory place and load, and be the positional information of destination server on the fs_locations setup of attribute of respective directories index node on the server at parent directory place.During client-access remote directory take-off point, obtain NFS4ERR_MOVED mistake, then by Get_fslocations, operate the position of the destination server that further obtains the actual place of remote directory take-off point, could access afterwards the remote directory take-off point being positioned on destination server.
In pNFS, each directory branches point need to create an extra index node and assist transfer on the meta data server at parent directory place, and client needs extra operation requests to obtain the meta data server position at remote directory take-off point place.Simultaneously because catalogue is arranged in different file system, and inode number does not obtain unified management, cause pNFS not support the directory metadata operation across meta data server, such as the catalogue rename (rename) across meta data server, hard link (hardlink) operation.
Summary of the invention
The technical problem to be solved in the present invention is that in prior art, cluster file system distributes loading process medium-long range directory branches point to safeguard that space availability ratio is not high, the problem of complicated operation between many meta data servers, a kind of new remote directory take-off point maintaining method is provided, to improve space availability ratio, reduce operation complexity.
In order to reach above object, the invention provides a kind of remote directory take-off point maintenance system, it is characterized in that, described system comprises:
One meta data server cluster, described meta data server cluster further comprises: a pivot data server and a plurality of remote meta data server, wherein, described pivot data server is for being recorded in parent directory by the index node inode of all newly-built catalogues, and in described index node inode, embed the positional information of described remote meta data server, the positional information of described remote meta data server is recorded and safeguarded, described remote meta data server is used for creating long-range sub-directory, to realize the metadata access of described long-range sub-directory,
One client, for according to the locating information of the described meta data server cluster of safeguarding, determines target metadata server, and foundation is connected with described target metadata server, and described target metadata server is sent to request of access.
Above-mentioned remote directory take-off point maintenance system, is characterized in that, the call number ino of described index node inode comprises: partial indexes node number in the sequence number seqid of identification index node i node place meta data server and separate file system.
Above-mentioned remote directory take-off point maintenance system, is characterized in that, described pivot data server further comprises with remote meta data server described in each:
Directory service module: for receiving the request of described client, and build and resolve file identification filehandle.
Index node maintenance module: for the maintenance of inode number ino, the positional information of described remote meta data server is embedded in described inode number ino.
Above-mentioned remote directory take-off point maintenance system, is characterized in that, described file identification filehandle comprises: file system numbering fsid, inode number ino, the described index node inode generation of version number territory.
Above-mentioned remote directory take-off point maintenance system, is characterized in that, described pivot data server also comprises:
Directory entry maintenance module: for adding and the item that deltrees, and the information of newly-built described index node inode is added in parent directory, and the information of described index node inode to be deleted is deleted from described parent directory.
Above-mentioned remote directory take-off point maintenance system, is characterized in that, described client also comprises:
Meta data server address mapping module: for the positional information mapping table by described meta data server cluster, inquire about the position of the described target metadata server at described index node inode place according to the sequence number seqid of identification index node i node place meta data server;
Catalog request module: for inquire about the position of described target metadata server by described meta data server address mapping module, foundation is connected and sends request with described target metadata server.
The present invention also provides a kind of remote directory take-off point maintaining method to be applied to described remote directory take-off point maintenance system, it is characterized in that, described method comprises:
Directory entry adds step: for adding directory entry at described meta data server cluster;
Directory entry accessing step: for completing the access of described meta data server cluster.
Above-mentioned remote directory take-off point maintaining method, is characterized in that, described directory entry adds step and also comprises:
Application local index node step: for distribute local index node i node at described index node maintenance module, by described inode number ino and described generation territory, be sent to described pivot data server;
Add sequence number step: the sequence number seqid that by described index node maintenance module, the described inode number ino sending is added to described remote meta data server for described pivot data server identifies;
Sequence number determining step: if be 0 for the seqid of described inode number ino, target directory is local directory, according to the original directory entry addition manner of system, add the directory entry of target directory, if described seqid is non-zero, described target directory is remote directory, increases described generation territory on the basis of original directory entry;
File identification foundation step: for building described file identification filehandle according to described inode number ino and described generation territory, and the described filehandle building is returned to described client preserve.
Above-mentioned remote directory take-off point maintaining method, is characterized in that, described directory entry accessing step also comprises:
Client-requested forwarding step: for the positional information of inquiring about described target metadata server by described meta data server address mapping module, described client sends request to described target metadata server;
Meta data server end request receiving step: the request of sending for described target metadata server parses and the described client of processing.
Above-mentioned remote directory take-off point maintaining method, is characterized in that, described meta data server end request receiving step also comprises:
Request analysis step: receive after the described request that described client sends by described directory service module for described target metadata server, resolve described file identification filehandle;
Request processing step: the described file identification filehandle that described request analyzing step is obtained, according to described request being positioned to the judgement of described pivot data server or described remote meta data server, complete the processing of described file identification filehandle, and give described client by result feedback.
Above-mentioned remote directory take-off point maintaining method, is characterized in that, described request analyzing step also comprises:
Lookup request analysis step: receive after the described request that described client sends, the filehandle of the described parent directory that parsing sends, inquire about the inode number ino of described parent directory, read the directory entry of the directory entry file acquisition file destination of described parent directory;
Getattr request analysis step: obtain described filehandle the request sending from described client, and resolve the described seqid in described inode number ino, described seqid and local seqid are compared.
Above-mentioned remote directory take-off point maintaining method, is characterized in that, described request treatment step also comprises:
Lookup request processing step: described directory service module builds filehandle according to inode number ino described in the directory entry getting in described Lookup request analysis step and described generation territory, and described filehandle is returned to described client;
Getattr request processing step: the described seqid getting is converted into local seqid, builds local index node number ino, and use described local index node number ino to read described index node inode and attribute information thereof from this locality.
Compared with prior art, beneficial effect of the present invention is, by increasing directory entry information, expands directory index node implication, eliminates index node waste, eliminates the operation bidirectional that newly-increased take-off point causes, reduction is across the implementation complexity of meta data server operation.
Accompanying drawing explanation
Fig. 1 is the structural representation of remote directory take-off point maintenance system of the present invention;
Fig. 2 is inode number structural representation of the present invention;
Fig. 3 is the schematic flow sheet of remote directory take-off point maintaining method of the present invention;
Fig. 4 is one embodiment of the invention remote directory take-off point foundation step schematic diagram;
Fig. 5 is directory entry physical record mode of the present invention;
Fig. 6 is one embodiment of the invention remote directory take-off point accessing step schematic diagram;
Fig. 7 is another embodiment of the present invention remote directory take-off point accessing step schematic diagram.
Wherein, Reference numeral:
1 meta data server cluster 2 clients
11 pivot data server 12 remote meta data servers
111 directory service module 112 directory entry maintenance modules
113 index point maintenance module 121 directory service modules
122 index point maintenance modules
21 meta data server address mapping module 22 catalog request modules
S1～S2, S11～S14, S300～S303, S310～S312, S321～S324: the administration step of various embodiments of the present invention
Embodiment
Provide the specific embodiment of the present invention below, in conjunction with diagram, the present invention has been made to detailed description.
The present invention proposes a kind of new metadata cluster medium-long range directory branches point maintaining method, the storage of take-off point is separated with record, in the meta data server at parent directory place, record inode number (ino) and the index node version number (generation) of take-off point, without increasing system space expense.And, in inode number, embed the positional information of meta data server, the operation of additionally obtaining remote directory take-off point place target metadata server location without client, and can effectively reduce the complexity realizing across meta data server operation.
Fig. 1 is the structural representation of remote directory take-off point maintenance system of the present invention.As shown in Figure 1, a kind of remote directory take-off point maintenance system provided by the invention, comprising:
Meta data server cluster 1, meta data server cluster 1 further comprises: pivot data server 11 and a plurality of remote meta data server 12, wherein, pivot data server 11 is for being recorded in parent directory by the index node inode of all newly-built catalogues, and in index node inode, embed the positional information of remote meta data server 12, the positional information of remote meta data server 12 is recorded and safeguarded, remote meta data server 12 is for creating long-range sub-directory, to realize the metadata access of long-range sub-directory;
System of the present invention at least comprises two meta data servers (MDS) end and a client.For sake of convenience the meta data server at parent directory place is designated as to pivot data server, MMDS(Master MDS), the meta data server at remote directory take-off point place is designated as remote meta data server, RMDS(Remote MDS).Wherein, pivot data server and the interchangeable role of remote meta data server where necessary, remote meta data server originally, also can be created to sub-directory on pivot data server originally, with spread loads.
Pivot data server 11 also comprises:
Directory service module 111: for receiving the request of client 2, and build and resolve file identification filehandle.
Directory service module 111, for receiving the request of client, builds, resolves filehandle.Filehandle is the sign of a file in unique representative system, and file identification filehandle comprises: file system numbering fsid, the inode number inoHe inode generation of version number territory.This module is used No. ino and generation structure filehandle in inode structure.Wherein, index node inode comprises: inode number ino and the identification index node generation of version number territory.Fig. 2 is inode number structural representation of the present invention, and as shown in Figure 2, inode number ino comprises: partial indexes node number in the sequence number seqid of identification index node i node place meta data server and separate file system.For long-range inode, can directly use its ino(containing the seqid of RMDS) and generation to build filehandle; For local inode, be required to be the seqid of the MDS at inode place in its ino interpolation, and at MDS metadata disk, read the generation of local inode, use afterwards its ino and generation thereof to build filehandle.Be the seqid that ino in filehandle comprises the MDS at the real place of inode all the time.The ino that unifies to comprise seqid by use builds filehanle, and filehandle can be resolved at MMDS and RMDS end, and need to not hold at MMDS that additional allocation inode is corresponding with inode on RMDS has assisted load transfer.While resolving filehandle, after obtaining the ino and generation of inode, ino is sent to inode maintenance module and further processes, if the seqid in ino is identical with the seqid of this MDS, be expressed as local ino, otherwise be expressed as remote directory take-off point ino.
Directory entry maintenance module 112: for adding and the item that deltrees, and the information of newly-built index node inode is added in parent directory, and the information of index node inode to be deleted is deleted from parent directory.
Directory entry maintenance module 112 is for adding and the item that deltrees, and this module is createing directory or during file, the information of newly-built inode added in the directory entry file of its parent directory; Deltreeing or during file, the information of inode to be deleted is being deleted from the directory entry file of its parent directory.The directory entry of system medium-long range directory branches point adds the directory entry file of the parent directory being arranged on MMDS to, and on the basis that comprises remote directory inode number (ino), increase the record in generation territory, make the directory service module of MMDS end can independently build filehandle, and needn't be mutual with RMDS; Local directory continues to keep the directory entry maintenance mechanism of original system.
Index node maintenance module 113: for the maintenance of inode number ino, the positional information of remote meta data server 12 is embedded in inode number ino.
Index node inode maintenance module 113 is safeguarded for No. ino.The present invention embeds inode number ino MDS locating information, has avoided identifying with extended attribute the expense of inode position.Be divided into seqid territory and partial indexes node number territory in file system independently for No. ino, wherein seqid territory takies the top N in No. ino.If long-range inode, the sequence number (seqid) of the actual place MDS of seqid sign inode; If local inode, seqid is by clear 0, and local inode still organizes according to the original resource management mode of system.By embed the locating information of MDS in No. ino, client operates to obtain the position at the actual place of remote directory take-off point without the Get_fslocations with extra, just can directly locate and initiate request of access.
Remote meta data server 12 comprises remote meta data server 1, remote meta data server 2... remote meta data server n-1, remote meta data server n, and each remote meta data server 12 also comprises:
Directory service module 121: for receiving the request of client 2, and build and resolve file identification filehandle.
Index node maintenance module 122: for the maintenance of inode number ino, the positional information of remote meta data server 12 is embedded in inode number ino.
Wherein, client 2 also comprises:
Meta data server address mapping module 21: for passing through the positional information mapping table of meta data server cluster 1, according to the position of the target metadata server at the sequence number seqid search index node i node place of identification index node i node place meta data server;
Meta data server address mapping module 21, i.e. mdsmap module, the seqid of all MDS and the mapping table of MDS particular location in maintenance system, inquire about the MDS at certain real place of inode according to sequence number.
Catalog request module 22: for passing through the position of meta data server address mapping module 21 query aim meta data servers, foundation is connected and sends request with described target metadata server.
Refer to Fig. 3, Fig. 3 is the schematic flow sheet of a kind of remote directory take-off point of the present invention maintaining method, and as shown in Figure 3, the method comprises:
Directory entry adds step S1: for adding directory entry at meta data server cluster;
Directory entry accessing step S2: for completing the access of meta data server cluster.
Wherein, directory entry interpolation step S1 also comprises:
Application local index node step S11: for distribute local index node i node at index node maintenance module, by inode number ino and generation territory, be sent to pivot data server;
Add sequence number step S12: for pivot data server, by index node maintenance module, the inode number ino sending is added to remote meta data server sequence number seqid and identify;
Sequence number determining step S13: if be 0 for the seqid of ino, target directory is local directory, according to the original directory entry addition manner of system, add the directory entry of target directory, if seqid is non-zero, target directory is remote directory, increases generation territory on the basis at original directory entry;
File identification foundation step S14: for building file identification filehandle according to seqid and generation territory, and the filehandle building is returned to client preserve.
Wherein, directory entry accessing step S2 also comprises:
Client-requested forwarding step S21: for passing through the positional information of meta data server address mapping module query aim meta data server, client sends request to target metadata server;
Meta data server end request receiving step S22: the request of sending for target metadata server parses and processing client.
Wherein, meta data server end request receiving step S22 also comprises:
Request analysis step S221: after the request of sending by directory service module reception client for target metadata server, carry out resolution file sign filehandle;
Request processing step S222: the file identification filehandle that request analysis step S221 is obtained, according to request being positioned to the judgement of pivot data server or remote meta data server, complete the processing of file identification filehandle, and by result feedback to client 2.
Wherein, request analysis step S221 also comprises:
Lookup request analysis step S2211: receive after the request that client sends, the filehandle of the parent directory that parsing sends, the inode number ino of inquiry parent directory, and whether be 0 by the seqid in the ino of analysis judgment parent directory, set up local index node i node or long-range index node inode, read the directory entry file of parent directory, and obtain the directory entry of file destination.
Getattr request analysis step S2212: obtain filehandle the request sending from client, and resolve the seqid in inode number ino, seqid and local seqid are compared.
Wherein, request processing step S222 also comprises:
Lookup request processing step S2221: directory service module builds filehandle according to the ino in the directory entry getting in Lookup request analysis step and generation territory, and filehandle is returned to client;
Getattr request processing step S2222: the seqid getting is converted into local seqid, builds local index node number ino, and use local index node number ino to read index node inode and attribute information thereof from this locality.
Below in conjunction with diagram, specific embodiments of the invention are described, the present invention mainly comprises that directory entry adds step and client-access step.
Fig. 4 is one embodiment of the invention remote directory take-off point foundation step schematic diagram, and as shown in Figure 4, a specific embodiment remote directory take-off point creation operation of the present invention, illustrates the adding procedure of directory entry.
RMDS applies for that the inode maintenance module on local inode step S300:RMDS distributes local inode, is sent to MMDS by ino and generation.Ino is wherein that RMDS holds local ino, the top N of ino (seqid) clear 0.
The inode maintenance module adding on sign seqid step S301:MMDS is that the ino that RMDS sends adds the sequence number seqid of sign RMDS, and sets up the inode structure of MMDS end.By embed seqid in ino, MMDS can distinguish local inode and long-range inde; Client can be extracted the seqid wherein comprising after obtaining ino, thereby navigates to RMDS, without the position that re-uses Get_fslocations and operate to obtain RMDS; Meanwhile, in system, all inode are unified sign, can simplify the realization of the operation (as the rename across meta data server, hardlink) across meta data server.
The directory entry maintenance module that adds directory entry step S302:MMDS end adds directory entry.If seqid equals 0 in the catalogue ino of directory entry to be added, illustrate that this catalogue is local directory, only need add according to the original directory entry structure of system.Otherwise, if the seqid in ino is not 0, illustrate that this catalogue is remote directory take-off point, for its directory entry increases the igen territory of the generation of sign inode, and the end that igen territory is placed on to directory entry structure is to reduce the impact on local directory maintenance process.For the directory entry of remote directory take-off point increases generation territory, can make the MMDS end can be independently for remote directory take-off point builds filehandle, and without with RMDS end alternately.Fig. 5 is directory entry physical record mode of the present invention, directory entry physical record mode shown in Figure 5.
The directory service module that builds filehandle step S303:MMDS is used the long-range ino and the generation that comprise seqid to build filehandle.If above-mentioned catalogue is remote directory take-off point, the ino in catalogue inode has comprised the seqid of the RMDS at the sign real place of catalogue; If local directory inode needs manually to add the seqid of current MDS for its ino.Subsequently, directory service module returns to client by the filehandle building.
Fig. 6 is one embodiment of the invention remote directory take-off point accessing step schematic diagram, and as shown in Figure 6, a specific embodiment remote directory take-off point lookup of the present invention operates, and the access process of directory entry is described.
Lookup: the present embodiment is with the file parameter by name of catalogue, and object is to obtain the filehandle of catalogue.
Client-requested forwarding step S310: the catalog request module of client is obtained the ino of parent directory inode.Call the position of the MDS that seqid in mdsmap module inquiry ino is corresponding.Subsequently, catalog request module sends to MDS by request.If target directory is remote directory take-off point, request will be sent to the MMDS at parent directory place.
The directory service module of MDS request analysis step S311:MDS end is received after request, resolves the filehandle of parent directory.Read the directory entry file of parent directory, the ino of the file of inquiry file name by name, and analyze seqid wherein.If the seqid in ino is not 0, illustrate that this sub-directory is remote directory take-off point, continue to read the igen territory of the generation that identifies long-range inode in directory entry, the ino getting and generation are recorded in the inode structure of setting up into remote directory take-off point; Otherwise, if the seqid in ino equals 0, illustrate that this catalogue is local directory, without reading igen territory, utilize ino to read corresponding inode in local physical store, set up complete inode structure, comprise generation.
MDS request processing step S312: directory service module is used the ino and the generation that comprise seqid to build filehandle, and filehandle is returned to client.In the filehandle of remote directory take-off point building process, can directly use the ino in inode structure; For local directory, should first for its ino, add the seqid of sign MDS position, place, carry out again afterwards filehandle structure.
Fig. 7 is another embodiment of the present invention remote directory take-off point accessing step schematic diagram, and as shown in Figure 7, another specific embodiment remote directory take-off point Getattr of the present invention operates, and the access process of directory entry is described.
Getattr: it is parameter that this example be take the filehandle of catalogue, and object is to obtain the attribute of catalogue.
Client-requested forwarding step S321: the catalog request module of client is obtained the inode of target directory, takes out ino wherein.Call the position of the MDS that seqid that mdsmap module inquiry ino comprises is corresponding.Subsequently, catalog request module sends to MDS by request.If target directory is remote directory take-off point, request will be sent to the RMDS at target directory place.
The filehandle that MDS request analysis step S322:MDS sends from client, obtain ino and extract seqid wherein, the seqid of seqid and book server is compared.If both equate, illustrate that target directory is local directory; Otherwise both are unequal, illustrate that corresponding catalogue is remote directory take-off point.
MDS request processing step S323: if target directory is local directory, the ino getting is removed to the corresponding position of seqid, be converted into local ino.Use amended ino, from physical store, obtain inode and attribute information thereof, comprise generation.When attribute is returned to client, for ino wherein adds the seqid of upper sign book server position again.Otherwise, if judgement target directory is remote directory take-off point, for client restoring to normal position is made mistakes.
Return to step S324: client directory request module is after request is returned, and the attribute returning according to MDS upgrades the attribute (wherein comprising seqid information in ino) of local inode.
Certainly; the present invention also can have other various embodiments; in the situation that not deviating from spirit of the present invention and essence thereof; those of ordinary skill in the art are when making according to the present invention various corresponding changes and distortion, but these corresponding changes and distortion all should belong to the protection domain of the appended claim of the present invention.
Claims (12)
1. a remote directory take-off point maintenance system, is characterized in that, described system comprises:
One meta data server cluster, described meta data server cluster further comprises: a pivot data server and a plurality of remote meta data server, wherein, described pivot data server is for being recorded in parent directory by the index node inode of all newly-built catalogues, and in described index node inode, embed the positional information of described remote meta data server, the positional information of described remote meta data server is recorded and safeguarded, described remote meta data server is used for creating long-range sub-directory, to realize the metadata access of described long-range sub-directory,
One client, for according to the locating information of the described meta data server cluster of safeguarding, determines target metadata server, and foundation is connected with described target metadata server, and described target metadata server is sent to request of access.
2. remote directory take-off point maintenance system according to claim 1, it is characterized in that, the call number ino of described index node inode comprises: partial indexes node number in the sequence number seqid of identification index node i node place meta data server and separate file system.
3. remote directory take-off point maintenance system according to claim 1, is characterized in that, described pivot data server further comprises with remote meta data server described in each:
Directory service module: for receiving the request of described client, and build and resolve file identification filehandle.
Index node maintenance module: for the maintenance of inode number ino, the positional information of described remote meta data server is embedded in described inode number ino.
4. remote directory take-off point maintenance system according to claim 3, is characterized in that, described file identification filehandle comprises: file system numbering fsid, inode number ino, the described index node inode generation of version number territory.
5. remote directory take-off point maintenance system according to claim 1, is characterized in that, described pivot data server also comprises:
Directory entry maintenance module: for adding and the item that deltrees, and the information of newly-built described index node inode is added in parent directory, and the information of described index node inode to be deleted is deleted from described parent directory.
6. remote directory take-off point maintenance system according to claim 1, is characterized in that, described client also comprises:
Meta data server address mapping module: for the positional information mapping table by described meta data server cluster, inquire about the position of the described target metadata server at described index node inode place according to the sequence number seqid of identification index node i node place meta data server;
Catalog request module: for inquire about the position of described target metadata server by described meta data server address mapping module, foundation is connected and sends request with described target metadata server.
7. a remote directory take-off point maintaining method, is applied to the remote directory take-off point maintenance system as described in any one in claim 1-6, it is characterized in that, described method comprises:
Directory entry adds step: for adding directory entry at described meta data server cluster;
Directory entry accessing step: for completing the access of described meta data server cluster.
8. remote directory take-off point maintaining method according to claim 7, is characterized in that, described directory entry adds step and also comprises:
Application local index node step: for distribute local index node i node at described index node maintenance module, by described inode number ino and described generation territory, be sent to described pivot data server;
Add sequence number step: the sequence number seqid that by described index node maintenance module, the described inode number ino sending is added to described remote meta data server for described pivot data server identifies;
Sequence number determining step: if be 0 for the seqid of described inode number ino, target directory is local directory, according to the original directory entry addition manner of system, add the directory entry of target directory, if described seqid is non-zero, described target directory is remote directory, increases described generation territory on the basis of original directory entry;
File identification foundation step: for building described file identification filehandle according to described inode number ino and described generation territory, and the described filehandle building is returned to described client preserve.
9. remote directory take-off point maintaining method according to claim 7, is characterized in that, described directory entry accessing step also comprises:
Client-requested forwarding step: for the positional information of inquiring about described target metadata server by described meta data server address mapping module, described client sends request to described target metadata server;
Meta data server end request receiving step: the request of sending for described target metadata server parses and the described client of processing.
10. remote directory take-off point maintaining method according to claim 9, is characterized in that, described meta data server end request receiving step also comprises:
Request analysis step: receive after the described request that described client sends by described directory service module for described target metadata server, resolve described file identification filehandle;
Request processing step: the described file identification filehandle that described request analyzing step is obtained, according to described request being positioned to the judgement of described pivot data server or described remote meta data server, complete the processing of described file identification filehandle, and give described client by result feedback.
11. remote directory take-off point maintaining methods according to claim 10, is characterized in that, described request analyzing step also comprises:
Lookup request analysis step: receive after the described request that described client sends, the filehandle of the described parent directory that parsing sends, inquire about the inode number ino of described parent directory, read the directory entry of the directory entry file acquisition file destination of described parent directory; Getattr request analysis step: obtain described filehandle the request sending from described client, and resolve the described seqid in described inode number ino, described seqid and local seqid are compared.
12. remote directory take-off point maintaining methods according to claim 10, is characterized in that, described request treatment step also comprises:
Lookup request processing step: described directory service module builds filehandle according to inode number ino described in the directory entry getting in described Lookup request analysis step and described generation territory, and described filehandle is returned to described client;
Getattr request processing step: the described seqid getting is converted into local seqid, builds local index node number ino, and use described local index node number ino to read described index node inode and attribute information thereof from this locality.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310743906.8A CN103761256B (en) | 2013-12-30 | 2013-12-30 | Maintenance system and method of branch points of remote directories |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310743906.8A CN103761256B (en) | 2013-12-30 | 2013-12-30 | Maintenance system and method of branch points of remote directories |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103761256A true CN103761256A (en) | 2014-04-30 |
| CN103761256B CN103761256B (en) | 2017-04-12 |
Family
ID=50528494
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201310743906.8A Expired - Fee Related CN103761256B (en) | 2013-12-30 | 2013-12-30 | Maintenance system and method of branch points of remote directories |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103761256B (en) |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106649601A (en) * | 2016-11-24 | 2017-05-10 | 郑州云海信息技术有限公司 | Method and system for processing data of file system as well as client and server |
| CN106844578A (en) * | 2017-01-07 | 2017-06-13 | 郑州云海信息技术有限公司 | The method and device that subtree root is inquired about is loaded to meta data server |
| CN107958034A (en) * | 2017-11-20 | 2018-04-24 | 郑州云海信息技术有限公司 | Distribution method, device and the medium of the inode number of distributed file system |
| CN108021472A (en) * | 2017-11-28 | 2018-05-11 | 厦门市美亚柏科信息股份有限公司 | The formatting restoration methods and storage medium of ReFS file system |
| CN108351797A (en) * | 2015-11-02 | 2018-07-31 | 微软技术许可有限责任公司 | Control heavy parsing behavior associated with middle directory |
| CN113111034A (en) * | 2021-04-07 | 2021-07-13 | 山东英信计算机技术有限公司 | Index pre-allocation method and device |
| CN117149708A (en) * | 2023-08-31 | 2023-12-01 | 中电云计算技术有限公司 | File access method, device, equipment and storage medium |
| WO2024109051A1 (en) * | 2022-11-21 | 2024-05-30 | 华为云计算技术有限公司 | Data warehouse system-based data processing method, and data warehouse system |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102075581B (en) * | 2011-01-25 | 2013-06-12 | 中国科学院计算技术研究所 | Data transmission method and device oriented to distributed file system |
-
2013
- 2013-12-30 CN CN201310743906.8A patent/CN103761256B/en not_active Expired - Fee Related
Cited By (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108351797A (en) * | 2015-11-02 | 2018-07-31 | 微软技术许可有限责任公司 | Control heavy parsing behavior associated with middle directory |
| CN108351797B (en) * | 2015-11-02 | 2021-08-31 | 微软技术许可有限责任公司 | Method and system for controlling reparse behavior associated with an intermediate directory |
| CN106649601A (en) * | 2016-11-24 | 2017-05-10 | 郑州云海信息技术有限公司 | Method and system for processing data of file system as well as client and server |
| CN106844578A (en) * | 2017-01-07 | 2017-06-13 | 郑州云海信息技术有限公司 | The method and device that subtree root is inquired about is loaded to meta data server |
| CN107958034A (en) * | 2017-11-20 | 2018-04-24 | 郑州云海信息技术有限公司 | Distribution method, device and the medium of the inode number of distributed file system |
| CN108021472A (en) * | 2017-11-28 | 2018-05-11 | 厦门市美亚柏科信息股份有限公司 | The formatting restoration methods and storage medium of ReFS file system |
| CN108021472B (en) * | 2017-11-28 | 2021-02-02 | 厦门市美亚柏科信息股份有限公司 | Format recovery method of ReFS file system and storage medium |
| CN113111034A (en) * | 2021-04-07 | 2021-07-13 | 山东英信计算机技术有限公司 | Index pre-allocation method and device |
| CN113111034B (en) * | 2021-04-07 | 2023-08-04 | 山东英信计算机技术有限公司 | Index pre-allocation method and device |
| WO2024109051A1 (en) * | 2022-11-21 | 2024-05-30 | 华为云计算技术有限公司 | Data warehouse system-based data processing method, and data warehouse system |
| CN117149708A (en) * | 2023-08-31 | 2023-12-01 | 中电云计算技术有限公司 | File access method, device, equipment and storage medium |
| CN117149708B (en) * | 2023-08-31 | 2024-06-04 | 中电云计算技术有限公司 | File access method, device, equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103761256B (en) | 2017-04-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103761256A (en) | Maintenance system and method of branch points of remote directories | |
| CN101692239B (en) | Method for distributing metadata of distributed type file system | |
| WO2016180055A1 (en) | Method, device and system for storing and reading data | |
| CN101226530B (en) | Media system having synchronization with preemptive prioritization of synchronization order | |
| CN101729442A (en) | Method and device for realizing content sharing | |
| AU2016204919A1 (en) | Intelligent data delivery and storage based on data characteristics | |
| CN102769638A (en) | Method, device and system for downloading files | |
| WO2018036324A1 (en) | Smart city information sharing method and device | |
| CN111209259B (en) | NAS distributed file system and data processing method | |
| CA2399657A1 (en) | System for distributed media network and meta data server | |
| CN103916467A (en) | Load transfer method and system in metadata cluster | |
| CN102171717A (en) | Aggregating media content from multiple clients to a server | |
| CN113986873A (en) | Massive Internet of things data modeling processing, storing and sharing method | |
| CN103778202A (en) | Enterprise electronic document managing server side and system | |
| CN105138275B (en) | A kind of Lustre memory system datas sharing method | |
| US11003711B2 (en) | Accessing audio files from an online content management system | |
| CN105354250A (en) | Data storage method and device for cloud storage | |
| CN102111285A (en) | Method and system for managing log information | |
| CN100498766C (en) | Mass file management system and method based on database | |
| CN103631820A (en) | Metadata management method and device of distributed file system | |
| CN104092726A (en) | Automatic replacing method and apparatus of same-name file | |
| CN105930233A (en) | Method and system for automatically backing up data of specified public cloud account | |
| KR101654314B1 (en) | Distributed processing system in spatial data and method for operating the same | |
| CN101873342A (en) | Data access method, data access system and disk array storage system | |
| CN104021137A (en) | Method and system for opening and closing file locally through client side based on catalogue authorization |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20170412 |