JPH05143419A - Processor for filing system - Google Patents

Abstract

PURPOSE:To improve performance and to effectively utilize a space when a logical volume is composed of plural volumes in a processor for a filing system for managing the filing system constructed on the logical volume composed of the plural volumes. CONSTITUTION:In respect to a volume integrating request 11, a volume integrating means 16 adds an arbitrary designated file title (b) to the route directory of a volume 19y to be integrated and the volume is linked from the master directory (a) of the basic filing system by using the file title (b). In respect to a volume separating request 12, a volume separating means 17 cancels the link from the master directory in which the route directory of the volume to be separated is linked.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention manages a file system constructed on a logical volume composed of a plurality of volumes, and incorporates / disconnects a volume in the same manner as adding / deleting a name to a file. The present invention relates to a processing device of a file system capable of performing.

[0002]

2. Description of the Related Art FIG. 12 shows an example of a file system constructed on a volume for explaining the prior art.
In the computer system, for example, as shown in FIG. 12A, a file system having a hierarchical structure in which a directory file that manages a file name is a node and an arbitrary file is a leaf is used.

When such a file system is constructed on one logical volume composed of a plurality of volumes (hereinafter referred to as a logical volume), the root directory of the file system constructed in each volume ( (Represented by "/") is virtually superposed on a directory having a basic file system. The operation of virtually overlapping these directories is called mounting.

In FIG. 12B, 18 is a logical volume and 19, 19a and 19b are volumes. In this example, the volume (hp0a) is added to the directory (sys) in the file system on volume (hp00) 19.
The root directory of 19a is virtually overlapped, and the root directory of the volume (hp0b) 19b is virtually overlapped with the directory (usr), thereby forming one logical volume 18 as a whole.

[0005]

The above-mentioned conventional methods have the following problems. (a) When resolving a path name, it is necessary to judge whether or not the directory is a mount point, and if it is a mount point, the entry of the root directory of the mounted volume is searched instead of the actual directory. Careful consideration is required. The mount point is a directory that is superimposed on the root directory of another volume, such as the sys and usr directories shown in (b) of FIG.

The path name is a name for uniquely identifying a file in the file system. The relationship between the file and the path name is 1 to n (n ≧ 1). Path name resolution refers to identifying a file in the file system from the path name.

(B) The directory entry of the mount point becomes invisible to the user. Therefore, in order to make all the files on the basic file system visible to the user (can be specified as a processing target by specifying the path name), an empty directory for mount points must be
Required for each mounted volume.

The directory entry is information that links a file name and a file, and is information stored in the directory. What is a file name?
This is a name for uniquely identifying files managed in a certain directory (these files are referred to as files under the directory).

For example, in the case of FIG. 12B, the user
Specify the path name of "/ sys / klib" to specify the volume (hp0
0) Files in 19 cannot be processed. Therefore, in order to eliminate such files, it is necessary to use a directory (free directory) that has no files under it as a mount point.

When a large number of volumes are mounted to form a huge logical volume, the more volumes that make up the logical volume, the more directories for mount points and the space consumed by the volume.

(C) In the conventional mount, since the directories are virtually overlapped, the relationship between the mount point and the volume disappears when the system stops. For this reason, it is necessary to perform the mount process for each IPL, so when mounting many volumes, the performance of the IPL is affected, and it takes a long time to start the system and start the service.

The present invention solves the above problems and eliminates the need for special consideration of mount points even when a logical volume is composed of a plurality of volumes, and even if a user does not use an empty directory, all of the users can use The purpose is to make the files visible and to eliminate the need for a mount operation the next time the system is started after the system has stopped.

[0013]

FIG. 1 is a block diagram showing the principle of the present invention. In FIG. 1, 10 is a processing device including a CPU and a memory, 11 is a volume incorporation request, 1
Reference numeral 2 is a volume disconnection request, 13 is a request reception mechanism from the user for the file system, 14 is a volume embedding request receiving means for accepting and processing the volume embedding request 11, and 15 is a volume disconnection request for accepting and processing the volume detachment request 12. Reception means, 16 is volume incorporation means, 17 is volume disconnection means, 1
Reference numeral 8 represents a logical volume, and 19x and 19y represent volumes that are units in which a root directory is provided.

The volume embedding request receiving means 14 performs processing for receiving a volume embedding request 11 that requests that a certain volume (for example, volume 19y) be incorporated in the directory (for example, a) of the basic file system. is there. In the volume incorporation request 11, the volume name (vol
y) and the path name (/ a / b) including the file name given to the root directory are specified.

When a volume incorporation request 11 is made, the volume incorporation means 16 determines the root directory of the file system in the volume 19y constituting the logical volume from the designated directory (a) in the basic file system. The linking process is performed with the designated file name (b).

A link means a relationship between a file and a directory created by adding a directory entry to the directory, and adding a directory entry of a file in a certain directory is called linking a file from the directory. It is possible to add multiple links to one file. When the number of links that a file has becomes 0, the space of the file is reclaimed if there is no process that has the file open. However, this space collection is suppressed only in the root directory.

The volume disconnection request receiving means 15 receives a volume disconnection request 12 requesting disconnection of a volume (for example, volume 19y) that constitutes a logical volume.

The volume detaching means 17 detaches the volume 1 when the volume detaching request 12 is issued.
The parent directory (a) to which the root directory of 9y is linked is updated and the link is released.

In the processing of the volume disconnecting means 17, the link is deleted only in the root directory of the volume even if there is an entry in the directory. In addition, even if the root directory of the volume is empty, space recovery is suppressed by deleting the link.

A file serial number is used as an identifier for identifying a file in such a file system.
There is a one-to-one relationship between file serial numbers and files. The file serial number is composed of a volume name that uniquely identifies the volume and a number that uniquely identifies the file in the volume. With such a configuration, according to the present invention, it is possible to obtain information for identifying the volume in which the file exists by the file serial number.

[0021]

[Action]

(l) The file name (b) is added to the root directory of the volume 19y that constitutes the logical volume, and the directory entry is added to the directory in the basic file system. This eliminates the special mount point directory and enables pathname resolution in a file system consisting of multiple volumes as in the case of a single volume.

(2) Other directory entries (for example, c) of the directory which becomes the parent directory (a) of the root directory of the volume 19y which constitutes the logical volume also appear in the directory tree. This eliminates the need to create a free directory for mount points.

(3) When the system is stopped by adding the file name (b) to the root directory of the volume 19y constituting the logical volume and adding the directory entry to the directory in the basic file system However, the link information does not disappear and it is not necessary to reconfigure the logical volume each time the system is restarted.

(4) Since the file system in the volume is retained even after the volume 19y constituting the logical volume is separated, it can be easily re-installed.

[0025]

EXAMPLE The volume incorporation request 11 is a command (command name = condir) of the following format, for example. “Condir path name Volume name to be incorporated” Here, the path name is a path name added to the root directory of the volume. As shown in FIG.
The command "/ a / b voly" instructs to link the root directory of the volume 19y with the volume name "voly" to the directory "/ a" of the basic file system with the file name "b". is doing.

The volume disconnection request 12 is, for example, a command of the following format (command name = discondi
r). "Discondir pathname" The command "discondir / a / b" as shown in Fig. 1 is used for "/" of the basic file system.
It is instructed to update the directory "a" and separate the root directory of the volume 19y having the file name "b" from the basic file system.

FIG. 2 is an explanatory diagram of a file management mechanism according to the embodiment of the present invention. For example, a file management mechanism 21 as shown in FIG. 2 constructs a file system on the logical volume 18 composed of a plurality of volumes. The file management mechanism 21 is composed of the following components.

(1) Request reception mechanism 13 from user Using the mechanism of volume incorporation / disconnection means 22,
Process requests from users. (2) Path name resolution mechanism 23 This mechanism uniquely identifies a file in the file system from the path name. The file access mechanism 26 is used to retrieve the directory appearing in the path name while acquiring the file serial number of the corresponding file.

(3) Path name operation mechanism 24 This is a mechanism for adding / deleting a directory entry to / from a directory when creating, deleting, renaming a file and adding a link to a file. The file access mechanism 26 is used when a directory entry is added to or deleted from a directory. The components of the directory entry are a file name, a file serial number, etc.

(4) File operation mechanism 25 This mechanism secures and recovers the file space on the volume. The file operation mechanism 25 reclaims the space of a file when the file is not linked from any file and no process has the file open. However, space is not collected for the root directory of the volume.

(5) File access mechanism 26 is a mechanism for inputting / outputting to / from a file. When writing data to a file, if space expansion is required, the file operation mechanism 25 is requested to secure the space.

FIG. 3 is an explanatory diagram of link information according to the embodiment of the present invention. For example, the volume 19 shown in FIG.
In the directory a of the basic file system of x,
The volume 19y is incorporated.

The directory entry registered in the directory a of the basic file system is (b) in FIG.
The information is as shown in. That is, volume 19y
File name "b" given to the root directory of
The file type (directory) and the file serial number.

The file serial number is composed of the volume name "voly" of the volume 19y and an in-volume file serial number which is a number for uniquely identifying the file in the volume. In the case of this embodiment, the number of the root directory. Is set to "1", the file sequence number of the file b is "voly-1".

The link information that the root directory of the volume 19y has by mounting is the information as shown in (b) of FIG. 3, and the number of links, the assigned file name,
This is the file serial number of the parent directory.

The number of links indicates how many higher-level directories are linked. The file name is determined from the path name specified by the volume mount request command. The file serial number of the parent directory is the file serial number of the directory a in the example of FIG.
From the volume name of x "and the serial number in the volume (5 in this example), it is" volx-5 ".

4 to 7 show the processing of the file management mechanism 21 when processing a volume incorporation request. The processing when the volume is incorporated will be described below.

The volume incorporation request acceptance means 14 in the request acceptance mechanism 13 from the user accepts the volume incorporation request 11. The information notified by the user is
It is the path name added to the root directory of the volume to be embedded and the volume name of the volume to be embedded.

The request reception mechanism 13 from the user requests the path name resolution mechanism 23 by the process 40 shown in FIG.
Get the file serial number of the directory that will be the parent directory of the root directory of the volume to be installed. Also, to prevent double registration, make sure that there is no file referenced by the specified path name.

In response to this request, the path name resolution mechanism 23
The processes 50 to 59 shown in FIG. 5 are executed. That is,
By notifying the file access mechanism 26 of the file sequence number, the operation of referring to the directory entry of the directory appearing in the path name and obtaining the file sequence number of the next directory is repeated to obtain the file sequence number of the parent directory.

The file access mechanism 26 responds to the request from the path name resolution mechanism 23 by processing 53-1 and the like.
File name i from among the files indicated by file serial numbers
Search the data (directory entry) corresponding to
Report the result.

It is an error if there is no directory appearing in the middle of the path name, and it is also an error if there is a directory appearing at the end of the path name.
In cases other than this, the request reception mechanism 1 from the requesting user for the file serial number of the parent directory is processed by processing 59.
Notify 3.

The request receiving mechanism 13 from the user performs processing 4
If the file referred to by the specified path name already exists in the judgment of 1, the process 45 notifies the user of an error.

If there is no error, the file serial number of the root directory of the volume to be incorporated is acquired in process 42, and then the file operation mechanism 25 is requested to update the link information of the volume root directory by process 43. The delivery information at the time of request is the file serial number of the volume root directory, the file name to be added, and the file serial number of the parent directory.

In response to this request, the file operation mechanism 25
Performs processing 60 and processing 61 shown in FIG. First,
The link information is created, and the file access mechanism 26 is requested to update the link information of the file using the file serial number as a key. By the process 62, the file access mechanism 26 includes, in the attribute information of the file specified by the file serial number, the number of links as shown in FIG. 3C, the file name to be added, the file serial number of the parent directory, and the like. Write the data.

Next, the request reception mechanism 13 from the user notifies the path name operation mechanism 24 of the file serial number of the parent directory and the file name of the root directory of the volume by the processing 44, and the file name of the root directory of the volume is notified. Ask to add a directory entry for the root directory.

In response to this request, the path name operating mechanism 24
The processing 70 and the processing 71 shown in FIG. 7 are executed. In process 70, a directory entry is created from the notified information. The file serial number of the root directory of the volume is easily assembled because the file serial number in the volume of the root directory is fixed to "1". By the process 71, the file access mechanism 26 is notified of the file serial number of the parent directory and the directory entry, and the addition is requested.

In response to the request, the file access mechanism 26 adds the directory entry to the file indicated by the file serial number of the parent directory in the process 72.

When the above processing is completed, the request receiving mechanism 13 from the user notifies the user that the volume installation processing is completed by the processing 45, and ends the installation processing.

8 to 11 show the processing of the file management mechanism 21 when processing a volume disconnection request. The processing when the volume is disconnected will be described below.

The volume disconnection request reception means 15 in the request reception mechanism 13 from the user receives the volume disconnection request 12. The information notified by the user is
This is the path name to the root directory of the volume to be detached.

The request acceptance mechanism 13 from the user requests the path name resolution mechanism 23 by the process 80 shown in FIG.
Get the file serial number of the parent directory of the root directory of the volume to be detached. It also verifies that the file referenced by the specified pathname is the root directory of the volume.

In response to this request, the path name resolution mechanism 23
Processing 90 to processing 99 shown in FIG. 9 is executed. That is,
By notifying the file access mechanism 26 of the file sequence number, the operation of referring to the directory entry of the directory appearing in the path name and obtaining the file sequence number of the next directory is repeated to obtain the file sequence number of the parent directory.

In response to the request from the path name resolution mechanism 23, the file access mechanism 26 retrieves the data (directory entry) corresponding to the file name i from the file indicated by the file serial number by processing 93 and the like, and Report the result.

If the corresponding directory entry does not exist, it is an error. If there is, the processing step 99 gives the file serial number of the parent directory and the file serial number of the root directory of the volume to be separated from the requesting user. The request reception mechanism 13 is notified.

The request receiving mechanism 13 from the user performs processing 8
If the file referred to by the specified path name is not the root directory according to the determination of 1, the process 84 notifies the user of an error.

If there is no error, the process 82 requests the path name operation mechanism 24 to delete the directory entry in the parent directory for the root directory of the volume to be detached.

The path name operation mechanism 24 requests the file access mechanism 26 to delete the directory entry for managing the corresponding file name from the parent directory by the process 100 shown in FIG. At this time, since the corresponding entry is the root directory of the volume, the directory is deleted even if there are files under it. The file access mechanism 26 deletes the directory entry by the process 101.

Next, the request reception mechanism 13 from the user instructs the file operation mechanism 25 by the process 83 to link information of the root directory of the volume to be incorporated (file serial number of parent directory, deleted file name, number of links). Ask to update.

The file operation mechanism 25 creates the link information by the processing 110 and the processing 111 shown in FIG. 11, and requests the file access mechanism 26 to update the link information of the corresponding file using the file serial number as a key. Since the corresponding file is the root directory of the volume, even if the number of links is 0 and the number of open processes is 0, space is not collected. The file access mechanism 26 writes the designated data in the attribute information of the file specified by the key in the process 112.

When the above processing is completed, the request receiving mechanism 13 from the user notifies the user of the completion of the volume disconnection processing by the processing 84, and terminates the disconnection processing.

[0062]

As described above, according to the present invention,
It has the following effects. (1) In path name resolution of a path name that includes a link in which a directory and files under it exist on different volumes, as with the case where the directory and files under it exist on the same volume, Since it is only necessary to search the directory entry, the performance of path name resolution equivalent to that in the case of existing in the same volume can be obtained even if the file exists in another volume.

(2) When mounting a volume, it is not necessary to create an empty directory for embedding the volume to show existing files on the directory tree, and the volume space can be used effectively.

(3) Since information regarding volume incorporation is held in the directory, it is not necessary to reconfigure the logical volume every IPL, and the processing performance from IPL to service start is improved accordingly. These effects become more significant as the number of volumes forming the logical volume increases.

[Brief description of drawings]

FIG. 1 is a principle configuration diagram of the present invention.

FIG. 2 is an explanatory diagram of a file management mechanism according to an embodiment of the present invention.

FIG. 3 is an explanatory diagram of link information according to the embodiment of the present invention.

FIG. 4 is an explanatory diagram of a volume embedding process according to the embodiment of this invention.

FIG. 5 is an explanatory diagram of a path name resolution process when incorporating a volume according to the embodiment of this invention.

FIG. 6 is an explanatory diagram of a file operation process when incorporating a volume according to an embodiment of the present invention.

FIG. 7 is an explanatory diagram of a path name operation process when incorporating a volume according to the embodiment of this invention.

FIG. 8 is an explanatory diagram of a volume detaching process according to the embodiment of the present invention.

FIG. 9 is an explanatory diagram of a path name resolution process at the time of volume disconnection according to the embodiment of this invention.

FIG. 10 is an explanatory diagram of a path name operation process when a volume is detached according to the embodiment of this invention.

FIG. 11 is an explanatory diagram of a file operation process when a volume is detached according to the embodiment of this invention.

FIG. 12 is a diagram showing an example of a file system configured on a volume for explaining the conventional technique.

[Explanation of symbols]

 10 Processing Device 11 Volume Embedding Request 12 Volume Detaching Request 13 Request Receiving Mechanism from User 14 Volume Embedding Request Receiving Means 15 Volume Detaching Request Receiving Means 16 Volume Embedding Means 17 Volume Detaching Means 18 Logical Volumes 19x, 19y Volumes

Claims (2)

[Claims] 1. A processing device (10) for managing a file system having a root directory for each volume, the directories having a hierarchical structure, and capable of constituting a logical volume by a plurality of volumes. , Volume embedding request receiving means (14) for receiving an instruction to embed a certain volume in the directory of the basic file system
And a volume embedding means for linking the root directory of the file system in the volume that constitutes the logical volume with the specified file name from the specified directory in the basic file system when there is a volume embedding request ( 16) and a volume disconnection request reception means (1) for receiving an instruction requesting disconnection of volumes constituting a logical volume.
5) and a volume disconnection means (17) for updating the parent directory to which the root directory of the volume to be disconnected is linked and releasing the link when a volume disconnection request is made The processing unit of the system. 2. The processing unit (10) of the file system according to claim 1, wherein the link information set in the directory is a volume name for uniquely identifying a volume and a number for uniquely identifying a file in the volume. A file system processing device characterized in that a file identification information composed of and is used, and the volume in which a directory to be linked exists is identified by the file identification information.