CN103761256B - 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
- CN103761256B CN103761256B CN201310743906.8A CN201310743906A CN103761256B CN 103761256 B CN103761256 B CN 103761256B CN 201310743906 A CN201310743906 A CN 201310743906A CN 103761256 B CN103761256 B CN 103761256B
- Authority
- CN
- China
- Prior art keywords
- directory
- remote
- metadata server
- inode
- 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.)
- Expired - Fee Related
Links
- 238000012423 maintenance Methods 0.000 title claims abstract description 51
- 238000000034 method Methods 0.000 title claims abstract description 35
- 238000013507 mapping Methods 0.000 claims description 14
- 238000012545 processing Methods 0.000 claims description 14
- 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 3
- 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
- 239000006185 dispersion Substances 0.000 description 1
- 235000013399 edible fruits Nutrition 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000008531 maintenance mechanism Effects 0.000 description 1
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
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 Clustering of cluster file system, it is more particularly to a kind of based in metadata cluster across
The maintaining method of the remote directory branch point of more multiple servers.
Background technology
In large-scale cluster file system, metadata is separated with data, services and has become a kind of trend.On the one hand,
Data access is higher so as to obtain but using out-band method DASD without going through meta data server
Data access performance；On the other hand, meta data server specially provides Metadata Service, has unloaded data access load, so as to
Separate unit meta data server can support higher client access performance, manage more storage devices, support bigger be
System Expansion.However, with the continuous expansion of system scale, separate unit meta data server is increasingly becoming system for restricting extension
Bottleneck.In order to further lift the extended capability of cluster file system, generally metadata is constituted using multiple stage meta data server
Server cluster, to disperse metadata to load, supports the horizontal stroke that cluster file system is reached by increasing meta data server quantity
To extension.
It is metadata load dispersion that other meta data servers are transferred to catalogue as granularity, the load of some subdirectories
A kind of common method, adopted by cluster file systems such as Lustre, pNFS, BWFS.The distribution of metadata load is in son
During the establishment of catalogue, to create long-range subdirectory in the way of the load of subdirectory metadata is transferred to into other metadata clothes
Business device, that is, select the meta data server outside the meta data server at parent directory place to carry out subdirectory establishment, the subdirectory
Referred to as remote directory branch point.The storage of remote directory branch point and access be related to parent directory place meta data server,
The meta data server and client at the actual place of branch point, increased system implementation complexity, especially to remote directory point
Establishment, access and the deletion of fulcrum produces large effect.
Existing pNFS by the position attribution (fs_locations) of catalogue will on different server multiple Ziwens
The name space of part system is integrated, so as to realize multiserver name space.In implementing, pNFS is in parent directory institute
Server and load transfer destination server on be respectively created directory inode, and the server being located for parent directory
The fs_locations attributes of upper respective directories index node arrange the positional information of upper destination server.Client accesses long-range
NFS4ERR_MOVED mistakes are obtained during directory branches point, then long-range mesh is further obtained by Get_fslocations operations
The position of the destination server at the actual place of record branch point, could access afterwards the remote directory branch on destination server
Point.
Each directory branches point needs to create an extra rope on the meta data server being located in parent directory in pNFS
Draw node to aid in completing transfer, client needs extra operation requests to obtain the metadata at remote directory branch point place
Server location.Simultaneously because catalogue is located in different file system, and inode number does not obtain unified management, leads
PNFS is caused not support that the directory metadata across meta data server is operated, such as across the catalogue renaming of meta data server
(rename), hard link (hardlink) operation.
The content of the invention
The technical problem to be solved in the present invention be in prior art cluster file system between multiple stage meta data server
Distribution loading process medium-long range directory branches point safeguards that space availability ratio is high, complex operation problem, there is provided a kind of new
Remote directory branch point maintaining method, to improve space availability ratio, reduces operation complexity.
In order to reach object above, the invention provides a kind of remote directory branch point maintenance system, it is characterised in that institute
The system of stating includes：
Meta-data server cluster, the metadata server cluster is further included：One master metadata server and
Multiple remote metadata servers, wherein, the master metadata server is used for the index node of all newly-built catalogues
Inode is recorded in parent directory, and the position letter of the remote metadata server is embedded in the index node inode
Breath, is recorded and is safeguarded to the positional information of the remote metadata server, and the remote metadata server is used to create
Long-range subdirectory is built, to realize the metadata access of the long-range subdirectory；
One client, for according to the location information of the metadata server cluster safeguarded, determining target metadata
Server, sets up the connection with the target metadata server, and sends access request to the target metadata server.
Above-mentioned remote directory branch point maintenance system, it is characterised in that the call number ino bag of the index node inode
Contain：Partial indexes node in sequence number seqid and separate file system of identification index node i node place meta data server
Number.
Above-mentioned remote directory branch point maintenance system, it is characterised in that the master metadata server is described remote with each
Journey meta data server is all further included：
Directory service module：For receiving the request of the client, and build and parse file identification filehandle；
Index node maintenance module：For the maintenance of inode number ino, by the position of the remote metadata server
Information is embedded in inode number ino.
Above-mentioned remote directory branch point maintenance system, it is characterised in that the file identification filehandle is included：File
System Number fsid, inode number ino, the index node inode version numbers generation domains.
Above-mentioned remote directory branch point maintenance system, it is characterised in that the master metadata server also includes：
Directory entry maintenance module：For the item that adds and deltree, and by the information of the newly-built index node inode
In being added to parent directory, and the information of the index node inode to be deleted is deleted from the parent directory.
Above-mentioned remote directory branch point maintenance system, it is characterised in that the client also includes：
Meta data server address mapping module：For being mapped by the positional information of the metadata server cluster
Table, inquires about the index node inode and is located according to sequence number seqid of identification index node i node place meta data server
The target metadata server position；
Catalog request module：For inquiring about the target metadata clothes by the meta data server address mapping module
The position of business device, sets up the connection with the target metadata server and sends request.
Present invention also offers a kind of remote directory branch point maintaining method is applied to described remote directory branch point dimension
Protecting system, it is characterised in that methods described includes：
Directory entry adds step：For adding directory entry in the metadata server cluster；
Directory entry accessing step：For completing the access of the metadata server cluster.
Above-mentioned remote directory branch point maintaining method, it is characterised in that the directory entry addition step also includes：
Application local index node step：For distributing local index node i node in the index node maintenance module,
By inode number ino and the index node inode version numbers generation domains, the main metadata clothes are sent to
Business device；
Addition sequence number step：For the master metadata server by the index node maintenance module by transmit come
Sequence number seqid for adding the remote metadata server in inode number ino is identified；
Sequence number judges step：If being 0 for the seqid in inode number ino, target directory is local mesh
Record, according to the original directory entry addition manner of system the directory entry of target directory is added, if the seqid is non-zero, the mesh
Heading record is remote directory, and the generation domains are increased on the basis of original directory entry；
File identification foundation step：For building file according to inode number ino and the generation domains
Filehandle is identified, and the filehandle for building is returned to into the client and preserved.
Above-mentioned remote directory branch point maintaining method, it is characterised in that the directory entry accessing step also includes：
Client request forwarding step：For inquiring about the target element by the meta data server address mapping module
The positional information of data server, the client sends to the target metadata server and asks；
Ask receiving step in meta data server end：The client is parsed and processed for the target metadata server
The request that end sends.
Above-mentioned remote directory branch point maintaining method, it is characterised in that ask receiving step in the meta data server end
Also include：
Request analysis step：The client is received by the directory service module for the target metadata server
After the request that end is sent, carry out parsing the file identification filehandle；
Request processing step：The file identification filehandle that the request analysis step is obtained, according to institute
Judgement of the request positioned at the master metadata server or the remote metadata server is stated, the file identification is completed
The process of filehandle, and result is fed back to into the client.
Above-mentioned remote directory branch point maintaining method, it is characterised in that the request analysis step also includes：
Lookup request analysis steps：After receiving the request that the client sends, the institute for sending is parsed
The filehandle of parent directory is stated, inode number ino of the parent directory is inquired about, the directory entry file of the parent directory is read
Obtain the directory entry of file destination；
Getattr request analysis steps：The filehandle is obtained in the request sent from the client, and is parsed
The seqid in inode number ino, the seqid is compared with local seqid.
Above-mentioned remote directory branch point maintaining method, it is characterised in that the request processing step also includes：
Lookup request processing steps：The directory service module in the Lookup request analysis step according to getting
Directory entry described in inode number ino and the generation domains build filehandle, and will be described
Filehandle returns to the client；
Getattr request processing steps：The seqid for getting is converted into into local seqid, local index section is built
Period ino, and using the local index node number ino from locally reading the index node inode and its attribute information.
Compared with prior art, the beneficial effects of the present invention is, by increase directory entry information, extend directory index section
Point implication, eliminates index node and wastes, and eliminates the operation bidirectional that newly-increased branch point causes, and reduces across meta data server operation
Implementation complexity.
Description of the drawings
Fig. 1 is the structural representation of remote directory branch point maintenance system of the present invention；
Fig. 2 is the inode number structural representation of the present invention；
Fig. 3 is the schematic flow sheet of remote directory branch point maintaining method of the present invention；
Fig. 4 is one embodiment of the invention remote directory branch point foundation step schematic diagram；
Fig. 5 is the directory entry physical record mode of the present invention；
Fig. 6 is one embodiment of the invention remote directory branch point accessing step schematic diagram；
Fig. 7 is another embodiment of the present invention remote directory branch point accessing step schematic diagram.
Wherein, reference：
The client of 1 metadata server cluster 2
The remote metadata server of 11 master metadata server 12
The directory entry maintenance module of 111 directory service module 112
The directory service module of 113 index point maintenance module 121
122 index point maintenance modules
The catalog request module of 21 meta data server address mapping module 22
S1～S2, S11～S14, S300～S303, S310～S312, S321～S324：The execution of various embodiments of the present invention
Step
Specific embodiment
The specific embodiment of the present invention is given below, detailed description is made that to the present invention with reference to diagram.
The present invention proposes a kind of new metadata cluster medium-long range directory branches point maintaining method, by the storage of branch point
Separate with record, the inode number (ino) and index node of branch point is recorded in the meta data server that parent directory is located
Version number (generation), without the need for increasing system space expense.And, meta data server is embedded in inode number
Positional information, without the need for client the operation of remote directory branch point place target metadata server location, and energy are additionally obtained
Effectively reduce the complexity that across meta data server operation is realized.
Fig. 1 is the structural representation of remote directory branch point maintenance system of the present invention.As shown in figure 1, what the present invention was provided
A kind of remote directory branch point maintenance system, including：
Metadata server cluster 1, metadata server cluster 1 is further included：Master metadata server 11 and multiple
Remote metadata server 12, wherein, master metadata server 11 is used to remember the index node inode of all newly-built catalogues
Record in parent directory, and the positional information of remote metadata server 12 is embedded in index node inode, to remote meta number
Recorded and safeguarded according to the positional information of server 12, remote metadata server 12 is used to create long-range subdirectory, with reality
The existing metadata access of long-range subdirectory；
Client 2 is used for the location information according to the metadata server cluster 1 safeguarded, determines target metadata service
Device, sets up the connection with target metadata server, and sends access request to target metadata server.
The system of the present invention is including at least two meta data server (MDS) ends and a client.For sake of convenience will
The meta data server that parent directory is located is designated as master metadata server, MMDS (Master MDS), remote directory branch point institute
Meta data server be designated as remote metadata server, RMDS (Remote MDS).Wherein, when necessary main metadata takes
The remote metadata server of business device and the interchangeable role of remote metadata server, i.e. script, can also be created in subdirectory
On the master metadata server of script, to disperse load.
Master metadata server 11 also includes：
Directory service module 111：For receiving the request of client 2, and build and parse file identification filehandle.
Directory service module 111 is used to receive the request of client, builds, parses filehandle.Filehandle is
The mark of a file in system is uniquely represented, file identification filehandle is included：File system numbering fsid, index section
Period ino and inode version number generation domains.This module is built using No. ino in inode structure and generation
filehandle.Wherein, index node inode is included：Inode number ino and identification index node version number generation
Domain.Fig. 2 is the inode number structural representation of the present invention, as shown in Fig. 2 inode number ino is included：Identification index node
Partial indexes node number in sequence number seqid and separate file system of inode places meta data server.For long-range inode,
Its ino (seqid containing RMDS) and its generation can be used directly to build filehandle；For local inode then
Need to be the seqid of the MDS that inode is located in its ino addition, and read local inode's in MDS metadata disk
Generation, builds filehandle using its ino and its generation afterwards.That is the ino in filehandle begins
The seqid of the MDS being really located comprising inode eventually.Filehanle is built by using the unified ino comprising seqid, is made
Obtaining filehandle can be resolved at MMDS and RMDS ends, and need not be in MMDS ends additional allocation inode and RMDS
Inode correspondences aiding in completing load transfer.During parsing filehandle, in the ino and generation that obtain inode
Afterwards, ino is sent to into inode maintenance modules further to process, if the seqid in ino is identical with the seqid of this MDS, table
Local ino is shown as, remote directory branch point ino is otherwise expressed as.
Directory entry maintenance module 112：For the item that adds and deltree, and by the information of newly-built index node inode
In being added to parent directory, and the information of index node inode to be deleted is deleted from parent directory.
Directory entry maintenance module 112 is used to add and deltree item, and this module is createing directory or during file, will be newly-built
The information of inode be added in the directory entry file of its parent directory；Deltreeing or during file, by inode to be deleted
Information delete from the directory entry file of its parent directory.The directory entry of system medium-long range directory branches point is added to positioned at MMDS
On parent directory directory entry file in, and increasing comprising on the basis of remote directory inode number (ino)
The record in generation domains so that the directory service module at MMDS ends can independently build filehandle, without with RMDS
Interaction；And local directory then continues to keep the directory entry maintenance mechanism of original system.
Index node maintenance module 113：For the maintenance of inode number ino, by the position of remote metadata server 12
Confidence breath is embedded in inode number ino.
Index node inode maintenance modules 113 are for No. ino maintenance.The present invention is the embedded index node of MDS location informations
Number ino, it is to avoid the expense of inode positions is identified using extended attribute.No. ino is divided into seqid domains and independent file system
Partial indexes node number domain in system, wherein seqid domains take the top N in No. ino.If long-range inode, then seqid is marked
Know the sequence number (seqid) of the actual place MDS of inode；If local inode, then by clear 0, local inode is still pressed seqid
The original resource management mode of lighting system is organized.By the location information for being embedded in MDS in No. ino, client need not make
Operated to obtain the position at the actual place of remote directory branch point with extra Get_fslocations, just can directly be positioned simultaneously
Initiate access request.
Remote metadata server 12 includes remote metadata server 1, remote metadata server 2... remote meta numbers
According to server n-1, remote metadata server n, each remote metadata server 12 also includes：
Directory service module 121：For receiving the request of client 2, and build and parse file identification filehandle.
Index node maintenance module 122：For the maintenance of inode number ino, by the position of remote metadata server 12
Confidence breath is embedded in inode number ino.
Wherein, client 2 also includes：
Meta data server address mapping module 21：For passing through the positional information mapping table of metadata server cluster 1,
According to the target element that sequence number seqid search index node i node of identification index node i node place meta data server is located
The position of data server；
Meta data server address mapping module 21, i.e. mdsmap modules, the seqid and MDS of all MDS in maintenance system
The mapping table of particular location, according to sequence number the MDS that certain inode is really located is inquired about.
Catalog request module 22：For inquiring about target metadata server by meta data server address mapping module 21
Position, set up with the connection of the target metadata server and send request.
Catalog request module 22 calls mdsmap modules 21 to inquire about the position of target MDS, sets up the connection with target MDS,
And transmit the request to target MDS.
Fig. 3 is referred to, Fig. 3 is a kind of schematic flow sheet of remote directory branch point maintaining method of the invention, such as Fig. 3 institutes
Show, the method includes：
Directory entry adds step S1：For adding directory entry in metadata server cluster；
Directory entry accessing step S2：For completing the access of metadata server cluster.
Wherein, directory entry addition step S1 also includes：
Application local index node step S11：For distributing local index node i node in index node maintenance module,
By inode number ino and generation domains, master metadata server is sent to；
Addition sequence number step S12：For master metadata server by index node maintenance module by transmit come index
Add remote metadata server sequence number seqid in node number ino to be identified；
Sequence number judges step S13：If being 0 for the seqid in ino, target directory is local directory, according to system
Original directory entry addition manner adds the directory entry of target directory, if seqid is non-zero, target directory is remote directory,
Increase generation domains on the basis of original directory entry；
File identification foundation step S14：For building file identification according to seqid and generation domains
Filehandle, and the filehandle for building is returned to into client preserved.
Wherein, directory entry accessing step S2 also includes：
Client request forwarding step S21：For inquiring about target metadata by meta data server address mapping module
The positional information of server, client sends to target metadata server and asks；
Ask receiving step S22 in meta data server end：Client is parsed and processed for target metadata server to send out
The request for going out.
Wherein, request receiving step S22 in meta data server end also includes：
Request analysis step S221：Receive what client was sent by directory service module for target metadata server
After request, resolution file mark filehandle is carried out；
Request processing step S222：The file identification filehandle that request analysis step S221 is obtained, according to asking
The judgement positioned at master metadata server or remote metadata server is asked, the process of file identification filehandle is completed, and
Result is fed back to into client 2.
Wherein, request analysis step S221 also includes：
Lookup request analysis steps S2211：After receiving the request that client sends, the parent directory for sending is parsed
Filehandle, inquire about inode number ino of parent directory, and the seqid in the ino for passing through analysis judgment parent directory is whether
For 0, local index node i node or long-range index node inode are set up, read the directory entry file of parent directory, and obtain mesh
The directory entry of mark file.
Getattr request analysis steps S2212：Filehandle is obtained in the request sent from client, and parses rope
Draw the seqid in node number ino, seqid is compared with local seqid.
Wherein, request processing step S222 also includes：
Lookup request processing steps S2221：Directory service module is according to getting in Lookup request analysis steps
Ino and generation domains in directory entry build filehandle, and filehandle is returned to into client；
Getattr request processing steps S2222：The seqid for getting is converted into into local seqid, local index is built
Node number ino, and read index node inode and its attribute information from local using local index node number ino.
Below in conjunction with diagram, the specific embodiment of the present invention is illustrated, the invention mainly comprises directory entry addition step
Rapid and client accessing step.
Fig. 4 is one embodiment of the invention remote directory branch point foundation step schematic diagram, as shown in figure 4, the one of the present invention
Specific embodiment remote directory branch point creates operation, illustrates the adding procedure of directory entry.
RMDS applies for local inode steps S300：Inode maintenance modules on RMDS distribute local inode, by ino and
Generation is sent to MMDS.Ino therein is the ino at RMDS ends, the top N (seqid) clear 0 of ino.
Addition mark seqid steps S301：The ino addition marks that inode maintenance modules on MMDS send for RMDS
Know sequence number seqid of RMDS, and set up the inode structure at MMDS ends.By being embedded in seqid in ino, MMDS can be distinguished locally
Inode and long-range inde；Client can extract the seqid for wherein including after ino is obtained, so as to navigate to RMDS, without the need for again
The position of RMDS is obtained using Get_fslocations operations；Meanwhile, all of inode, can letter by unifying identifier in system
Change the realization of the operation (such as across rename, hardlink of meta data server) across meta data server.
Addition directory entry step S302：The directory entry maintenance module addition directory entry at MMDS ends.If directory entry to be added
Catalogue ino in seqid be equal to 0, then illustrate the catalogue for local directory, only need to carry out according to the original directory entry structure of system
Addition.Otherwise, if the seqid in ino is not 0, illustrate that the catalogue is remote directory branch point, be that its directory entry increases mark
Know the igen domains of the generation of inode, and igen domains are placed on into the end of directory entry structure to reduce to local directory
The impact of maintenance process.Directory entry increase generation domains for remote directory branch point can enable MMDS ends stand alone as far
Journey directory branches point builds filehandle, and without the need for interacting with RMDS ends.Fig. 5 is the directory entry physical record side of the present invention
Formula, directory entry physical record mode shown in Figure 5.
Build filehandle steps S303：The directory service module of MMDS using comprising seqid long-range ino and
Generation builds filehandle.If above-mentioned catalogue is remote directory branch point, the ino in catalogue inode is
The seqid of the RMDS that included list of identifications is really located；If local directory inode, then need to add manually for its ino
Plus the seqid of current MDS.Subsequently, the filehandle for building is returned to client by directory service module.
Fig. 6 is one embodiment of the invention remote directory branch point accessing step schematic diagram, as shown in fig. 6, the one of the present invention
Specific embodiment remote directory branch point lookup is operated, and illustrates the access process of directory entry.
Lookup：The present embodiment is with the entitled parameter of the file of catalogue, it is therefore an objective to obtain the filehandle of catalogue.
Client request forwarding step S310：The catalog request module of client obtains the ino of parent directory inode.Call
The position of the corresponding MDS of seqid in mdsmap module polls ino.Subsequently, catalog request module transmits the request to MDS.Such as
Fruit target directory is remote directory branch point, asks the MMDS by parent directory place is sent to.
MDS request analysis steps S311：The directory service module at MDS ends is received after request, parses parent directory
filehandle.The directory entry file of parent directory is read, the ino of the file of the entitled name of file is inquired about, and analyzes therein
seqid.If the seqid in ino is not 0, the subdirectory is illustrated for remote directory branch point, continuation reading directory entry acceptance of the bid
Know the igen domains of the generation of long-range inode, the ino for getting and generation recorded as remote directory branch
In the inode structure that point is set up；Otherwise, if the seqid in ino is equal to 0, illustrate that the catalogue is local directory, without the need for reading
Igen domains are taken, using ino corresponding inode in local physical store is read, set up complete inode structure, including
generation。
MDS request processing steps S312：Directory service module is built using ino and generation comprising seqid
Filehandle, and filehandle is returned to into client.In the filehandle building process of remote directory branch point,
The ino in inode structure can be used directly；Should be first its ino addition marks place MDS position for local directory
Seqid, carries out again afterwards filehandle structures.
Fig. 7 is another embodiment of the present invention remote directory branch point accessing step schematic diagram, as shown in fig. 7, the present invention
Another specific embodiment remote directory branch point Getattr is operated, and illustrates the access process of directory entry.
Getattr：This example is with the filehandle of catalogue as parameter, it is therefore an objective to obtain the attribute of catalogue.
Client request forwarding step S321：The catalog request module of client obtains the inode of target directory, takes out it
In ino.Call the position of the corresponding MDS of seqid that mdsmap module polls ino include.Subsequently, catalog request module please
Ask and be sent to MDS.If target directory is remote directory branch point, the RMDS by target directory place is sent to is asked.
MDS request analysis steps S322：Ino is obtained in the filehandle that MDS sends from client and it is extracted
In seqid, seqid is compared with the seqid of book server.If both are equal, illustrate that target directory is local mesh
Record；Otherwise, i.e., both are unequal, illustrate that corresponding catalogue is remote directory branch point.
MDS request processing steps S323：If target directory is local directory, the ino for getting is removed into seqid corresponding
Position, be converted into local ino.Using amended ino, inode and its attribute information are obtained from physical store, including
generation.It is that ino therein adds upper mark book server position again when attribute is returned to into client
seqid.Otherwise, then it is the error of client restoring to normal position if it is determined that target directory is remote directory branch point.
Return to step S324：Client directory request module updates local after request is returned according to the attribute that MDS is returned
The attribute (seqid information is included in wherein ino) of inode.
Certainly, the present invention can also have other various embodiments, ripe in the case of without departing substantially from spirit of the invention and its essence
Know those skilled in the art and work as and various corresponding changes and deformation, but these corresponding changes and change can be made according to the present invention
Shape should all belong to the protection domain of appended claims of the invention.
Claims (12)
1. a kind of remote directory branch point maintenance system, it is characterised in that the system includes：
Meta-data server cluster, the metadata server cluster is further included：One master metadata server and multiple
Remote metadata server, wherein, the master metadata server is used to remember the index node inode of all newly-built catalogues
Record in parent directory, and the positional information of the remote metadata server is embedded in the index node inode, to institute
The positional information for stating remote metadata server is recorded and safeguarded, the remote metadata server is used to create long-range son
Catalogue, to realize the metadata access of the long-range subdirectory；
One client, for according to the location information of the metadata server cluster safeguarded, determining target metadata service
Device, sets up the connection with the target metadata server, and sends access request to the target metadata server.
2. remote directory branch point maintenance system according to claim 1, it is characterised in that the index node inode
Call number ino include：In sequence number seqid and separate file system of identification index node i node place meta data server
Partial indexes node number.
3. remote directory branch point maintenance system according to claim 1, it is characterised in that the master metadata server
Further include with remote metadata server each described：
Directory service module：For receiving the request of the client, and build and parse file identification filehandle；
Index node maintenance module：For the maintenance of inode number ino, by the positional information of the remote metadata server
In being embedded into inode number ino.
4. remote directory branch point maintenance system according to claim 3, it is characterised in that the file identification
Filehandle is included：File system numbering fsid, inode number ino, the index node inode version numbers
Generation domains.
5. remote directory branch point maintenance system according to claim 1, it is characterised in that the master metadata server
Also include：
Directory entry maintenance module：For the item that adds and deltree, and the information of the newly-built index node inode is added
To in parent directory, and the information of the index node inode to be deleted is deleted from the parent directory.
6. remote directory branch point maintenance system according to claim 1, it is characterised in that the client also includes：
Meta data server address mapping module：For by the positional information mapping table of the metadata server cluster, root
Inquire about described in the index node inode places according to sequence number seqid of identification index node i node place meta data server
The position of target metadata server；
Catalog request module：For inquiring about the target metadata server by the meta data server address mapping module
Position, set up with the connection of the target metadata server and send request.
7. a kind of remote directory branch point maintaining method, is applied to the remote directory as any one of claim 1-6 and divides
Fulcrum maintenance system, it is characterised in that methods described includes：
Directory entry adds step：For adding directory entry in the metadata server cluster；
Directory entry accessing step：For completing the access of the metadata server cluster.
8. remote directory branch point maintaining method according to claim 7, it is characterised in that the directory entry adds step
Also include：
Application local index node step：For distributing local index node i node in the index node maintenance module, by institute
Inode number ino and index node inode version number generation domains are stated, the master metadata server is sent to；
Addition sequence number step：To be transmitted come described in by the index node maintenance module for the master metadata server
Sequence number seqid for adding the remote metadata server in inode number ino is identified；
Sequence number judges step：If being 0 for the seqid in inode number ino, target directory is local directory,
Add the directory entry of target directory according to the original directory entry addition manner of system, if the seqid is non-zero, the target
Catalogue is remote directory, and the generation domains are increased on the basis of original directory entry；
File identification foundation step：For building file identification according to inode number ino and the generation domains
Filehandle, and the filehandle for building is returned to into the client preserved.
9. remote directory branch point maintaining method according to claim 8, it is characterised in that the directory entry accessing step
Also include：
Client request forwarding step：For inquiring about the target metadata by the meta data server address mapping module
The positional information of server, the client sends to the target metadata server and asks；
Ask receiving step in meta data server end：The client is parsed and processed for the target metadata server to send out
The request for going out.
10. remote directory branch point maintaining method according to claim 9, it is characterised in that the meta data server
End request receiving step also includes：
Request analysis step：The client is received for the target metadata server by the directory service module to send out
After the request for coming, carry out parsing the file identification filehandle；
Request processing step：The file identification filehandle that the request analysis step is obtained, foundation is asked to described
The judgement positioned at the master metadata server or the remote metadata server is asked, the file identification is completed
The process of filehandle, and result is fed back to into the client.
11. remote directory branch point maintaining methods according to claim 10, it is characterised in that the request analysis step
Also include：
Lookup request analysis steps：After receiving the request that the client sends, the father for sending is parsed
The filehandle of catalogue, inquires about inode number ino of the parent directory, reads the directory entry file acquisition of the parent directory
The directory entry of file destination；Getattr request analysis steps：Obtain in the request sent from the client described
Filehandle, and the seqid in inode number ino is parsed, the seqid is compared with local seqid
Compared with.
12. remote directory branch point maintaining methods according to claim 11, it is characterised in that the request processing step
Also include：
Lookup request processing steps：The directory service module is according to the mesh got in the Lookup request analysis step
Inode number ino and the generation domains build filehandle described in record item, and the filehandle is returned
Back to the client；
Getattr request processing steps：The seqid for getting is converted into into local seqid, local index node number is built
Ino, and using the local index node number ino from locally reading the index node inode and its attribute information.
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 CN103761256A (en) | 2014-04-30 |
| CN103761256B true 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) |
Families Citing this family (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10223378B2 (en) * | 2015-11-02 | 2019-03-05 | Microsoft Technology Licensing, Llc | 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 |
| CN108021472B (en) * | 2017-11-28 | 2021-02-02 | 厦门市美亚柏科信息股份有限公司 | Format recovery method of ReFS file system and storage medium |
| CN113111034B (en) * | 2021-04-07 | 2023-08-04 | 山东英信计算机技术有限公司 | Index pre-allocation method and device |
| CN117149708A (en) * | 2023-08-31 | 2023-12-01 | 中电云计算技术有限公司 | File access method, device, equipment and storage medium |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102075581A (en) * | 2011-01-25 | 2011-05-25 | 中国科学院计算技术研究所 | 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
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102075581A (en) * | 2011-01-25 | 2011-05-25 | 中国科学院计算技术研究所 | Data transmission method and device oriented to distributed file system |
Non-Patent Citations (2)
| Title |
|---|
| 《对象存储系统中自适应的元数据负载均衡机制》;陈涛 等;《软件学报》;20130228(第2期);第331-340页 * |
| The Metadata Management Algorithm Based on Hash Postfix Table;Xiujuan Li;《2010 International Colloquium on Computing,Communication, Control, and Management》;20101231;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103761256A (en) | 2014-04-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103761256B (en) | Maintenance system and method of branch points of remote directories | |
| US6681227B1 (en) | Database system and a method of data retrieval from the system | |
| CN101729442B (en) | Method and device for realizing content sharing | |
| US8782096B2 (en) | Virtual repository management | |
| CN105787091B (en) | Support the content delivering system and method for multiple terminals | |
| JP4278299B2 (en) | Communication system and method | |
| US20140358859A1 (en) | File sharing system and file sharing method | |
| US6363375B1 (en) | Classification tree based information retrieval scheme | |
| CN104516974B (en) | A kind of management method and device of file system directories item | |
| WO2018036324A1 (en) | Smart city information sharing method and device | |
| CN101611399A (en) | Webpage, website modeling and generation | |
| CN106874383A (en) | A kind of decoupling location mode of metadata of distributed type file system | |
| CA2636429A1 (en) | Presenting digitized content on a network | |
| CN102984299B (en) | Domain name registration, the method for parsing and service system is realized based on domain name group | |
| US20110282868A1 (en) | Search method, integrated search server, and computer program | |
| CN1295636C (en) | An efficient index structure to access hierarchical data in a relational database system | |
| EP2184690A1 (en) | Federated search system based on multiple search engines | |
| CN107918638A (en) | Information processor, document display method, file display system and medium | |
| JP5557824B2 (en) | Differential indexing method for hierarchical file storage | |
| CN102750370A (en) | Method and device for remotely submitting archives based on B/S (Browser/Server) structure | |
| CN109271871A (en) | Sample store path generation method, device, computer equipment and storage medium | |
| JPH11213014A (en) | Data base system, data base retrieving method and recording medium | |
| CN101873342A (en) | Data access method, data access system and disk array storage system | |
| CN114528473A (en) | Websocket-based information integration release method and system | |
| CN102087650B (en) | Method and device for displaying electronic document |
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 |