JPH06332769A - File control system - Google Patents

Abstract

PURPOSE:To improve processing speed by storing node information on a file in use in a node control part and unnecessitating the reading of the node information of the file, a directory or control information each time. CONSTITUTION:When the request for a file is generated, an instruction is transmitted from a main control part 15 to a node control part 11. When it is the use start request of the file, the node information on the file is read to the high speed memory arranged within a node control part 11 from a large capaciry storage device. When the request for the file is not the use start request of the file, that is the requests are the open and close of the file, the reading and writing of data to the file and the use termination of the file, etc., the node information on the designated file is retrieved by referring to the node information on the file of the high speed and the processing for the request it executed. Thus, as for the node information on the file in use, the necessity of the reading from the large capacity storage device can be eliminated.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a file management system capable of writing and reading information to and from a mass storage device with high reliability and at high speed.

[0002]

2. Description of the Related Art FIG. 14 is an explanatory diagram showing a conventional file management system. In the figure, 1 is a root node which is the beginning of the directory, 2 is a node under the root node 1, and 3 is node information of a file under the node 2. Reference numeral 4 is a file whose storage location in the mass storage device can be obtained from the node information 3 of the file at the bottom of this directory.

Next, the operation will be described. Generally, in an information processing device, information to be held is stored in a mass storage device in a unit called a file 4, a file name is given to each file 4, and the file 4 required by the program is assigned to the file name. I manage it so that I can access it. Therefore, node information corresponding to each file 4 is provided to store the storage location of the file 4 and necessary management data, file name, etc., and a tree structure directory is provided as shown in FIG. Node information, that is, the node information 3 of the file can be searched.

That is, the directory starts from the root node 1 and sequentially designates the node information, for example, the lower node 2 according to the node number, and further the node information 3 of the file. Here, there is the node information 3 of the file at the bottom of this directory, and by searching the node information 3 of this file from the root node 1, the storage location of the desired file 4 in the mass storage device is obtained. In addition, each node information, the parent node number that indicates the parent node immediately above the node,
It has child node names and child node numbers of one or more child nodes immediately below.

Therefore, if the file name of the file 4 is made up of this column of node names and the node information 3 of the file is searched from the root node 1 of the directory, the corresponding file 4 can be obtained. it can.

Note that, as a document in which a technique related to such a conventional file management system is described, there is, for example, JP-A-3-67344.

[0007]

Since the conventional file management system is constructed as described above, the file 4
Whenever a processing request for a directory and a directory is made, the node information and directory of the file 4 are read from the mass storage device to the high-speed memory each time. , It is necessary to read the information from the mass storage device into the high-speed memory again, and manage the use / unuse of the file 4 when the file 4 is created or deleted. The management information for this purpose must be read from the mass storage device into the high-speed memory each time, which requires a considerable amount of processing time. There was also a problem that the contents of the file would be destroyed if it stopped.

The present invention has been made to solve the above problems, and the inventions described in claims 1, 3 and 4 each include a node information, a directory, or management information of a file each time. It is an object to obtain a file management system that does not need to be read from a mass storage device.

It is another object of the present invention to provide a file management system in which the contents of the file are not destroyed even if the mass storage device is stopped.

[0010]

According to a first aspect of the present invention, there is provided a file management system including an area management unit for managing the use / unuse of blocks, a node management unit for managing file node information, and directory contents. A node management unit that manages a node, an input / output management unit that manages file reading / writing, and a main control unit that controls the entire system such as control of each management unit and division of a mass storage device, and a node The management unit has a high-speed memory that stores node information regarding files in use.

A file management system according to a second aspect of the present invention is an area management unit that manages the use / unuse of blocks, a node management unit that manages file node information, and a directory that manages the contents of a directory. A management unit, an input / output management unit that manages reading / writing of files, and a main control unit that controls the entire system such as control of each management unit and division of a mass storage device, and
The main control unit has a function of controlling the order of commands to the node management unit, the directory management unit, and the area management unit when creating / deleting a file.

A file management system according to a third aspect of the invention is an area management unit that manages the use / unuse of blocks, a node management unit that manages file node information, and a directory that manages the contents of directories. A management unit, an input / output management unit that manages reading / writing of files, and a main control unit that controls the entire system such as control of each management unit and division of a mass storage device, and
The directory management unit has a high-speed memory that stores a certain amount of directories used in the past.

A file management system according to a fourth aspect of the present invention is an area management unit that manages the use / unuse of blocks, a node management unit that manages file node information, and a directory that manages the contents of directories. A management unit, an input / output management unit that manages reading / writing of files, and a main control unit that controls the entire system such as control of each management unit and division of a mass storage device, and
The area management unit has a high-speed memory for reading and storing management information for managing the use / non-use of blocks at the time of initialization.

[0014]

According to the first aspect of the present invention, the node management unit stores the node information relating to the file being used in the built-in high speed memory, and when changing the target node information, the node information in the high speed memory is stored. By changing, it becomes unnecessary to newly read the node information from the mass storage device each time.

Further, the main control unit in the invention described in claim 2 controls the order of the commands to the node management unit, the directory management unit, and the area management unit at the time of file generation / deletion so that the file is being written. Even if the mass storage device is stopped, the contents of the file are prevented from being destroyed.

The directory management unit according to the third aspect of the present invention stores a certain amount of directories used in the past in a built-in high speed memory,
When reading a directory, if the target directory is in the high-speed memory, it is not necessary to read it newly from the mass storage device.

Further, the area management unit in the invention described in claim 4 uses / uses the block at the initialization of the file management.
By reading the management information for managing unused and storing it in the built-in high-speed memory, when using the management information when creating / deleting files, it is newly stored in the mass storage device. No need to read.

[0018]

【Example】

Example 1. Embodiment 1 of the present invention will be described below with reference to the drawings. FIG. 1 is a block diagram showing a file management system according to an embodiment of the present invention. In the figure, reference numeral 11 denotes a node management unit for managing node information of a file (directory) having file (directory) size, file storage location (block number) on the mass storage device, date and time information, and the like. Reference numeral 12 is an input / output management unit for managing reading / writing of files, 13 is a directory management unit for managing a directory having a file name, and 14 is management information for managing use / unuse of blocks. An area management unit for managing the node information area bitmap and the file (directory) area bitmap. A main control unit 15 controls the node management unit 11, the input / output management unit 12, the directory management unit 13, and the area management unit 14, and also controls the entire file management system such as dividing the mass storage device. It is a department.

FIG. 2 is a block diagram showing the structure of a high-speed memory arranged inside the node management unit 11 in the file management system according to the first embodiment of the present invention. In the figure, 21 is the high speed memory, and 201 to 216 are the storage location (block number) in the mass storage device of the node information of the file stored in the high speed memory 21, the storage location in the high speed memory, etc. Memory information of a file that stores information that does not need to be written to the mass storage device, and 221 to 236 are file node information that includes information such as the file size, file storage location (block number), and date and time information.

FIG. 3 is an explanatory diagram showing logical division of the mass storage device. In the figure, 301 is a storage location for storing a node information area bitmap logically managed by the area management unit 14, and 302 is a storage location for storing a file (directory) area bitmap. Reference numeral 303 is a storage location in which node information of a file (directory) managed by the node management unit 11 is stored, and 304 is a file (directory) whose reading / writing is managed by the input / output management unit 12.
Is a storage location where the node information of is stored. The mass storage device is divided into each of these storage locations 301-304.

FIG. 4 is an explanatory diagram showing details of the directory. In the figure, reference numerals 401, 402, ... Show storage locations (block numbers) of node information of files (directories), and 411, 412, ... Show file (directory) names. .. and file (directory) names 411, 412, ... Are written in this directory. The storage locations (block numbers) 401, 402 ,.

FIG. 5 is an explanatory diagram showing details of node information of a file (directory). In the figure, 5
01 is file (directory) size information, 50
2 is information of storage location of file (directory), 50
Reference numeral 3 is date and time information regarding date and time, and 504 is information regarding the number of lower nodes. The node information of this file (directory) has these pieces of information 501 to 504.

FIG. 6 is an explanatory diagram showing the relationship between directory node information and file node information, and shows a logical access route of a file. In the figure, 5 is node information of the root directory, and 6 is a root directory whose storage location is designated by the node information 5 of this root directory. Reference numeral 7 is the node information of the directory obtained from the root directory 6 by searching the directory name of the necessary directory, and 8 is the directory whose storage location is designated by the node information 7 of this directory. Three
Is the node information of the file obtained from this directory 8 by searching the file name of the required file, and 4 is the file whose storage location is indicated by the node information 3 of this directory. Here, the node information 3 of this file and the same reference numeral as those of the conventional file 4 are given.

Next, the operation will be described. FIG. 7 is a flow chart showing the flow of processing when a file is stored in the high speed memory, which will be described below. Now, when a request for a file occurs, a command is sent from the main control unit 15 to the node management unit 11 (step S
T1). The request for this file includes the use start and end of the file, the reading and writing of data, the opening and closing of the file, and the like. Next, it is determined whether or not the request is a request to start using the file (step ST2). As a result, if it is a file use start request, the node information 221 to 2 of the file of the high-speed memory 21 arranged in the node management unit 11
A vacant one is selected from 36, and the node information of the file is read from the mass storage device there (step ST3), and the vacant place in the memory information 201 to 216 of the file of the high-speed memory 21. Various information is set in (step ST4), and the process ends.

If the result of determination in step ST2 is that the request for the file is not a file use start request, that is, the file is opened, closed,
If the request is to read or write data to a file or finish using the file, the high-speed memory 21
The node information 221 to 236 of the file is searched to search the node information of the designated file (step ST5), and then the process for the request is executed (step ST6). By determining whether or not the request is a file use end request (step ST7), if the request is a use end request, the high-speed memory 21 is released and the process ends (step ST8). ),
If the request is other than that, the process is terminated.

In this case, however, the number of nodes that can be used is limited to n, and if an attempt is made to use more than that, an error will be returned. With the above procedure, for the node information of the file being used, it is not necessary to read the node information of the file from the mass storage device.

Example 2. Next, a second embodiment of the present invention will be described with reference to the drawings. The system configuration of the file management system according to the second embodiment is the same as that shown in FIG. FIG. 8 is a flow chart showing the flow of processing in one embodiment of the invention described in claim 2, and is from the main control unit 15 to each processing unit at the time of writing to the mass storage device in file generation / deletion or the like. 11 shows the order of commands sent to 11 to 14.

Next, the operation will be described. When a file generation / deletion request is generated (step ST11),
It is determined whether or not the request is a file generation request (step ST12). If the result of the determination is that it is a file generation request, the main control unit 15 sends a command to the region management unit 14 to search for an unused region of the block, and changes the number of requested blocks to the used region (step ST
13). Next, the node management unit 11 is caused to send a command to create the node information of the file to be generated, and the input / output management unit 12 writes it in the mass storage device (step ST
14). Next, the command is sent again to the area management unit 14,
The area changed in step ST13 is written in the mass storage device by the input / output management unit 12. After that, the command is sent to the directory management unit 13, and in the high speed memory,
After writing the storage location and the file name of the node information of the generated file to the directory and changing the date and time information of the node information of the directory, the input / output management unit 12 increases them in the order of the node information of the directory and the directory. Write to the capacity storage device (step ST
15), the process ends.

On the other hand, if the result of determination in step ST12 is that the request is not a file generation request,
That is, in the case of a file deletion request, a command is sent from the main control unit 15 to the directory management unit 13 to delete the node information of the file to be deleted in the directory on the high speed memory and change it. The input / output management unit 12 writes the directory in the mass storage device (step ST16). Then, similarly, the date and time information of the node information of the directory is changed on the high-speed memory, and the input / output management unit 12 writes it in the mass storage device (step ST17). Thereafter, a command is sent to the area management unit 14 to change the area management information on the high speed memory, and the changed area management information is written to the mass storage device by the input / output management unit 12 (step S
(T18), the process ends.

Here, for example, when generating a file, in step ST15, when the mass storage device is stopped after the process of writing the directory to the mass storage device is finished, the node information of the directory is still updated. There will be no. Therefore, in the node information of the directory shown in FIG. 5, an error occurs in the date / time information 503, but the information 504 of the number of lower nodes is the lower layer in the directory written in it before the mass storage device is actually stopped. You can know it by counting the number of nodes. Therefore, the file is registered (generated) in the directory, and the content of the file is guaranteed.
The above procedure can prevent the contents of the file from being destroyed even when the mass storage device such as a disk stops at the time of generating / deleting the file.

Example 3. Next, a third embodiment of the present invention will be described with reference to the drawings. FIG. 9 is a block diagram showing the configuration of a high-speed memory arranged in the directory management unit 13 in the file management system according to the third embodiment of the invention. In the figure, 22 is the high-speed memory. is there. Further, 601 to 605 are storage locations (block numbers) of node information of directories existing on the high-speed memory 22.
And memory information of a directory having a storage location (block number) of the directory, which is node information of the directory existing in the high-speed memory 22 and information indicating the directory. Reference numerals 611 to 615 are node information of directories having date and time information and the like, and reference numerals 621 to 625 are directories having storage locations (block numbers) of file node information and file names. Also in this case, the system configuration is the same as that shown in FIG.

Next, the operation will be described. Here, FIG.
0 is a flow chart showing the flow of processing when a directory is stored in the high speed memory 22. When a request for a directory occurs (step ST21), the memory information 601 to 60 of each directory on the high-speed memory 22.
By referring to the storage location (block number) of the node information of the directory which 5 has and searching for the storage location (block number) of the node information of the requested directory, the node information of the requested directory is stored in the high-speed memory. 22 is searched (step ST)
22). Next, it is determined whether or not the node information of the requested directory can be found (step ST23), and if it exists in the high speed memory 22, the high speed memory 2
The requested processing is executed for the node information of the directory on the upper side (step ST26). On the other hand, if the node information of the requested directory does not exist in the high speed memory 22, the node information of the requested directory is read from the mass storage device into the high speed memory 22 (step ST24). Next, after setting the storage location (block number) of the node information of the directory to one of the memory information 601 to 605 of the directory on the high-speed memory 22 (step ST25), the node information of the directory is requested. The processing is executed (step ST26).

Next, referring to the memory location (block number) of the directory included in the memory information 601 to 605 of each directory on the high-speed memory 22, search for a memory location (block number) equal to the requested directory. By, it is searched whether or not the requested directory exists in the high speed memory 22 (step ST27). Next, it is determined whether or not the requested directory can be found in the high speed memory 22 (step ST28). If it is found in the high speed memory 22, the directory in the high speed memory 22 is checked. Then, the requested processing is executed (step ST31). On the other hand, if the requested directory does not exist in the high speed memory 22,
The directory requested from the mass storage device is read into the high speed memory 22 (step ST29). Next, the storage location (block number) of the directory is set to 1 of the memory information 601 to 605 of the directory on the high speed memory 22.
Set to one (step ST30), the requested processing is executed for that directory (step ST3).
1).

By the above procedure, it is not necessary to newly read the directory existing on the high speed memory 22 from the mass storage device.

Example 4. Next, a fourth embodiment of the present invention will be described with reference to the drawings. FIG. 11 is a block diagram showing the configuration of a high-speed memory arranged in the area management unit 14 in the file management system according to the embodiment of the invention described in claim 4. In the figure, 23 is the high-speed memory. is there. Further, 701 is a node information area bitmap as management information for managing the use / unuse of blocks existing on the high-speed memory 22, and 702 is also a file (directory) area bitmap. In addition,
Also in this case, the system configuration is the same as that shown in FIG.

Next, the operation will be described. Here, FIG.
2 is a flowchart showing a flow of processing when storing two pieces of management information for managing use / unuse of blocks in the high-speed memory 23. FIG. 13 shows a case where a change request for the two pieces of management information occurs. 3 is a flowchart showing the flow of the processing of FIG. First, the storage of management information in the high-speed memory 23 will be described with reference to the flowchart shown in FIG. When an initialization request for management information for managing the use / unuse of a block occurs (step ST41), the node information area bitmap 701 is first read from the mass storage device onto the high-speed memory 23 (step ST42). Next, in the same manner, the file (directory) area bitmap 702 is read (step ST43), and the processing ends.

Next, the change of each management information on the high speed memory 23 will be described with reference to the flow chart shown in FIG. When a change request for management information for managing the use / non-use of a block is generated (step ST5)
1) After changing the node information area bitmap 701 in the high speed memory 23 according to the request (step ST
52), the changed node information area bitmap 701 on the high-speed memory 23 is written in the mass storage device (step ST53). Next, after changing the file (directory) area bitmap 702 in the high-speed memory 23 according to the request (step ST54), the changed file (directory) in the high-speed memory 23.
The area bitmap 702 is written in the mass storage device (step ST55), and the process ends.

As described above, after the processing for the initialization request is executed according to the flowchart of FIG. 12, the management information change processing is executed according to the flowchart of FIG. 13 so that the management information is used when the file is created / deleted. At this time, it is not necessary to newly read it from the mass storage device.

[0039]

As described above, according to the first aspect of the invention, the area management unit that manages the use / non-use of blocks, the node management unit that manages the node information of a file, and the contents of the directory are managed. It has a directory management unit that manages files, an input / output management unit that manages reading / writing of files, and a main control unit that controls the entire system such as control of each management unit and division of a mass storage device. Since the node management unit has a high-speed memory for storing node information about files,
Storage location (block number) is described in the directory Since the storage location (block number) of the file and the directory itself is described in the node information, the storage location of the file can be hierarchically managed by the directory. Also, when changing the target node information, it is not necessary to newly read the node information from the mass storage device each time by only changing the node information in the high-speed memory. There is an effect that a file management system that can perform the change processing of is quickly obtained.

According to the second aspect of the present invention, the main control unit is provided with a function of controlling the order of commands to the node management unit, the directory management unit, and the area management unit when a file is created / deleted. With this configuration, even if the mass storage device that is writing is stopped due to power failure or reset, the file content is not destroyed and the file management system that can guarantee the file content is provided. There is an effect to be obtained.

According to the third aspect of the present invention, the directory management unit is provided with a high-speed memory for storing a certain amount of directories used in the past. If the target directory already exists in high-speed memory,
Since there is no need to newly read from the mass storage device, there is an effect that a file management system capable of processing a directory at high speed can be obtained.

According to the invention described in claim 4, the area management section is provided with a high-speed memory, and the management information for managing the use / non-use of the block in the high-speed memory at the initialization of the file management. Since it is configured to store the file, it is not necessary to newly read it from the mass storage device when changing the management information at the time of creating / deleting a file, so that the management information changing process is performed at high speed. There is an effect that a file management system capable of being obtained can be obtained.

[Brief description of drawings]

FIG. 1 is a block diagram showing a configuration of a file management system according to first to fourth embodiments of the present invention.

FIG. 2 is a block diagram showing a configuration of a high speed memory included in a node management unit according to the first embodiment of the present invention.

FIG. 3 is an explanatory diagram showing logical division of the mass storage device in the above embodiment.

FIG. 4 is an explanatory diagram showing details of a directory in the above embodiment.

FIG. 5 is an explanatory diagram showing details of node information of a file in the above embodiment.

FIG. 6 is an explanatory diagram showing a relationship between directory node information and file node information in the above embodiment.

FIG. 7 is a flowchart showing a flow of processing according to the above embodiment.

FIG. 8 is a flowchart showing a processing flow according to the second embodiment of the present invention.

FIG. 9 is a block diagram showing a configuration of a high speed memory included in a directory management unit according to a third embodiment of the present invention.

FIG. 10 is a flowchart showing the flow of processing according to the above embodiment.

FIG. 11 is a block diagram showing the configuration of a high-speed memory included in an area management unit according to the fourth embodiment of the present invention.

FIG. 12 is a flowchart showing a flow of processing at the time of initialization in the above embodiment.

FIG. 13 is a flowchart showing the flow of processing when a management information change request is generated in the above embodiment.

FIG. 14 is a block diagram showing a configuration of a conventional file management system.

[Explanation of symbols]

 11 node management unit 12 input / output management unit 13 directory management unit 14 area management unit 15 main control unit 21 high speed memory 22 high speed memory 23 high speed memory

Claims (4)

[Claims] 1. An area management unit for managing use / unuse of the block of a mass storage device in which information is read and written in units of blocks of a fixed size, and stored in the mass storage device. Node management section that manages the node information indicating the attributes of the file to be stored, and has a high-speed memory that stores the node information related to the file in use, and the contents of the directory that describes the storage location of the node information of the file. A directory management unit that manages a file, an input / output management unit that manages reading and writing of the file, the area management unit, a node management unit,
A file management system comprising: a directory management unit; and a main control unit for performing overall control of the file management system such as control of an input / output management unit and division of the mass storage device. 2. An area management unit for managing use / unuse of the block of a mass storage device in which information is read and written in units of blocks of a fixed size, and stored in the mass storage device. A node management unit that manages node information of a file that indicates the attributes of the file, a directory management unit that manages the contents of the directory in which the storage location of the node information of the file is described, and the reading and writing of the file. An input / output management unit that manages the area management unit, the area management unit, the node management unit, the directory management unit, and the input / output management unit, and the mass storage device is divided. When the file is generated, the area management unit, the node management unit, the area management unit, and the directory management unit are sequentially ordered, and the file When deleting a file, a file management system comprising a directory control unit and a main control unit for sending commands to the area management unit in this order. 3. An area management unit for managing use / unuse of the block of a mass storage device in which information is read and written in units of blocks of a fixed size, and stored in the mass storage device. The node management unit that manages the node information of the file that represents the attributes of the file and the contents of the directory that describes the storage location of the node information of the file are managed, and a certain amount of the previously used directory is stored. A directory management unit having a high-speed memory for storage, an input / output management unit that manages reading and writing of the file, and control of the area management unit, node management unit, directory management unit, and input / output management unit And a main control unit that controls the entire file management system, such as dividing the mass storage device. 4. Use / unuse of the blocks read at initialization by managing use / unuse of the blocks of a mass storage device in which information is read / written in units of blocks of a fixed size. An area management unit having a high-speed memory for storing management information for managing usage, a node management unit for managing node information of a file representing attributes of a file stored in the mass storage device, and A directory management unit that manages the contents of the directory that describes the storage location of the node information of the file,
An input / output management unit that manages reading and writing of the file, and the file management such as control of the area management unit, node management unit, directory management unit, and input / output management unit and division of the mass storage device. A file management system that includes a main control unit that controls the entire system.