JPH06290095A - File managing device - Google Patents

Abstract

PURPOSE:To make it possible to simply confirm the state of a file afterwards when the accessing can not be made to the file due to the erasing, movement or name change of the file by using a specific file managing device having a file management table. CONSTITUTION:The file management table 51 for describing the erasing, movement and name change of a file is prepared at every directory of the file managing device 5. The device 5 is also provided with a table registering means 52 for securing an area for storing file information in the table 51, a table updating means 53 for describing information relating to the file in the table 51 at the time of executing erasing or the like, a table referring means 54 for extracting data from the table 51 when the accessing can not be made to the file, and a table deleting means 55 for periodically deleting the information relating to the file from the table 51 when deletion or the like is executed. Consequently file processing can be smoothly advanced.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a process of a file management device when a directory structure is changed in the file management device.

[0002]

2. Description of the Related Art A file management device (here, a typical operating system UNIX (registered trademark))
The files handled by the above file management device) are objects (data on disk, magnetic tape, memory) that have common operations (read, write, position, stretch, etc.) for processes to exchange information with the outside world. , Networks, devices, etc.). To request an operation on this object, the file must first be uniquely identified. The UNIX file itself is managed by a structure called an inode, and the inode identifier is the basic element for identifying the file. Information such as (Table 1) is written in the inode.

[0003]

[Table 1]

There is always one inode for every file in the tree structure of the UNIX file management device. Then, it is identified by a uniquely determined number. The file management device uses a hierarchical directory structure to
A symbolic name is defined for the node, and a namespace for distinguishing from higher levels is constructed. The conversion from this symbolic name (path name) to the inode number is done by UNIX.
It is done by the kernel of and the directory holds the correspondence table. FIG. 10 shows the internal structure of the directory file of the file management device in the conventional example.

There are three typical types of UNIX files. Ordinary files that are handled as a sequence of bytes on secondary storage, directory files in which file names and inode numbers that are structures that store information about the substance of the files are paired, and hardware devices These are the three special files that are supported. And the file management device of UNIX is a tree structure from the user.
A directory file appears to have a (hierarchical structure) and forms this entity. A set of entries as shown in FIG. 11 is written in the directory file. The file is named by the path name based on this tree structure. That is, the target file is specified by separating directories with "/" like "/ vmunix / a". As a result, the file management device in UNIX is managed so that its name is uniquely determined. Here is an example of how the file management device actually searches for a target file.

For example, the directory "/" is shown in FIG.
The following procedure is required to search for / vmunix here (explained in conjunction with FIG. 13).

(A) Look at the inode of "/". Since the inode number of "/" is predetermined to be 2, the location can be known.

(B) Since the type of the file, the access right, the location of the substance, etc. are described in the inode, the following can be understood. That is, "/" is a directory and the location of its entity.

(C) Since "/" is a directory, its entity is viewed. Then the name and i
Since the node pair is described, i corresponding to / vmunix
Get node number 10.

(D) Look at the vnode's inode. Then you will find the following. That is, / vmunix is an ordinary file and its location.

(E) Look at the substance.

When a file existing in a deeper directory is viewed, it can be searched by repeating (b), (c), (d), (c), ....

The features of the file management device are summarized as follows. The UNIX file management device plays a role of giving a unique name to a resource managed by UNIX. The resources include hardware resources as well as software resources as ordinary files stored on the disk. The access method to all those resources can be handled uniformly by the method specified by the program and the command.
You are free to create new files. That is, you can freely name new resources.

[0014]

However, in the conventional file management apparatus, as long as access (read, write, execute) to a directory and files in the directory is permitted, anyone can freely use the path name. You can create, delete, move, and rename the file, but once the file is deleted, moved, or renamed, the management information in the file management device is changed and you can access the file with the previous path name and file name. I can not do it. For this reason, when one user arbitrarily deletes, moves, or renames a file that can be accessed by multiple users, other users cannot access the file, and what happens to the file? There was a problem that I didn't know (whether it was erased, moved, or the name changed). The present invention solves the above problems by deleting, moving, and deleting files.
It is an object of the present invention to provide a file management device that allows another user to easily check what happened to a file after a name change.

[0015]

In order to achieve the above object, in the file management apparatus of the present invention, information associated with erasing, moving and renaming of files in a directory is described for each directory of the file management apparatus. Prepare a file management table for Then, the file management table registration means that secures an area for storing information about the file in the file management table when the file is created, and the information about the file when erased, moved, or renamed are described in the file management table. A file management table updating means for updating the file, a file management table referring means for extracting information from the file management table when the file cannot be accessed, and information about the file when the file is deleted, moved, or renamed periodically. A file management table deleting means for deleting from the file management table is provided.

[0016]

Therefore, according to the present invention, when the user cannot access the target file because the file has been deleted, moved, or renamed, who, when, and what did the inaccessible file do? Can be easily confirmed later, and by confirming the transition to the next operation smoothly, file processing can proceed smoothly.

[0017]

DESCRIPTION OF THE PREFERRED EMBODIMENTS The present invention will be described below with reference to the drawings showing its embodiments. FIG. 1 is a block diagram of a computer including a file management device according to the present invention. In FIG. 1, 1 is a central processing unit for processing requested information, 2 is a display device for displaying windows, graphics, characters, etc., 3 is an input device for inputting characters, numerical values, etc., 4 is an operating system, window system. A main storage device for storing a program being executed, 5 is a file management device in the present embodiment, and 6 is a secondary storage device for storing the file management device 5. The file management device 5 is used in the present invention, and has a file management table 51 for registering the current information of the file and an area for storing information about the file in the file management table 51 when the file is created. File management table registering means 52 for securing, file management table updating means 53 for describing information on files when deleted, moved or renamed in the file management table 51, information when files cannot be accessed file management table The file management table reference means 54 for extracting from the file 51, and the file management table deletion means 55 for periodically deleting the information about the file when it is deleted, moved, or renamed from the file management table 51.

An embodiment of the file management device 5 of the present invention in the computer configured as described above will be described below. First, before explaining the means according to the present invention,
File management table prepared by the file management device 5
51 will be explained. The structure of the file management table 51 is shown in FIG.
Each item has the meaning as shown in (Table 2).

[0019]

[Table 2]

The file management table 51 is created at the same time when the directory is created by the file management device 5, and conversely, at the same time when the directory is deleted, the file management table 51 is also deleted. Therefore, one file management table 51 exists for each directory.

Next, regarding the means of the present invention, the file management table registration means 52 and the file management table update means 5
3, the file management table reference means 54, and the file management table deletion means 55 will be described in this order. The file management table registration means 52 will be described with reference to the flowchart of FIG. First, if there is a change in the directory structure,
The file management table registration means 52 is executed. The file management table registration means 52 first checks how the directory structure has changed. If a new file was created in the directory (YES in S1),
Was the file moved from another directory? (Y in S2
S), or if the file name has been changed (YES in S3),
It is confirmed whether the file name is already registered in the file management table 51 (S4). If it is not registered, an area for storing information on the newly created file is secured in the directory (S5). Next, the file name is written in that area, and "new" is written in the other items (S6). If already registered, overwrite that area. The procedure for overwriting is the same as (S6). For example, when the file name Tamura is newly created in the directory A, the contents of the file management table 51 are as shown in FIG. Finally, the file management table deleting means 55 (this description will be described later) is executed (S7).

The file management table updating means 53 will be described with reference to the flowchart of FIG. First, when there is a change in the directory structure, the file management table updating means 53 is executed. The file management table updating means 53 first checks how the directory structure has changed. If the file existing in the directory is deleted (YES in S11), moved to another directory (YES in S12), or renamed (S13).
If YES, the corresponding file name is registered and the area is searched from the file management table 51 (S14). After that, the items other than the file name in the area are updated (S15). Update is performed for each item (operation, date, user, result) in order. For example, the file name Tamura newly created in directory A is 1993.
When the user Umezu (user ID = 100) moves to directory B as file name Fujiyama at 11:50 on September 25, 2013, the contents of the file management table 51 are as shown in FIG. Finally, the file management table deleting means 55 (this explanation will be described later) is executed (S16).

The file management table reference means 54 will be described with reference to the flowchart of FIG. The file management table reference means 54 is executed when a user accesses a file in the directory by a command, a program, or the like, but the file cannot be accessed. This file management table reference means
First, 54 searches the file management table 51 for an area in which the file name is registered based on the file name that could not be accessed (S21). If there is an area registered here
(YES in S22), the content of each item (operation, date and time, user, result) described in the area is extracted for each item (S23).
Then, the extracted contents are returned as a result (S24). The returned contents are displayed on the display device 2 by commands, programs, etc.
By displaying in, even if the target file disappears from the directory, you can easily check what happened to the file from the display results. Finally, the file management table deleting means 55 (this description will be described later) is executed (S25).

The file management table deleting means 55 will be described with reference to the flowchart of FIG. By executing the file management table deleting means 55, information is updated for a certain period of time in the file management table regarding the area updated in the area registered in the file management table 51 (the file does not exist in the directory). After holding in 51, all these areas are deleted from the file management table 51. This allows the file management table 51
Can be prevented from increasing infinitely. The file management table deleting means 55 first extracts the current date and time (S31). Next, search the updated area (the file does not exist in the directory) from the areas registered in the file management table 51, and extract the contents of the date and time item.
(S32). When the file management table 51 is checked to the end, the process ends. The current date and time and the extracted time are for a certain period (one day,
Check if it is open for more than one week, one month) (S33). If it is open, the area is deleted from the file management table 51 (S34). For example, the file management table 51 is shown in FIG.
In the state shown in (a), the file name bbb is stored in directory A.
When a new file is created at 11:00 on June 30, 1993, the file aaa area of the file management table 51 is deleted,
It changes as shown in FIG. 9B (at this time, the file management table registration means 52 is executed). After this, until all areas of the file management table 51 are checked (S35), S
32, S33, S34 are repeated.

[0025]

As is apparent from the above embodiment, by using the file management device of the present invention, what happens to the file when it becomes inaccessible due to deletion, movement, or name change of the file. It becomes possible to easily confirm whether or not the file has been processed, and the file processing can be smoothly performed.

[Brief description of drawings]

FIG. 1 is a configuration diagram of a computer according to an embodiment of the present invention.

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

FIG. 3 is a flowchart of a file management table registration means in one embodiment of the present invention.

FIG. 4 is a diagram illustrating an example of a file management table registration unit according to an exemplary embodiment of the present invention.

FIG. 5 is a flowchart of a file management table updating means in an embodiment of the present invention.

FIG. 6 is a diagram illustrating an example of a file management table updating unit according to an embodiment of the present invention.

FIG. 7 is a flowchart of a file management table reference means in one embodiment of the present invention.

FIG. 8 is a flowchart of a file management table deleting means according to an embodiment of the present invention.

FIG. 9 is a diagram illustrating an example of a file management table deleting unit according to an embodiment of the present invention.

FIG. 10 is a conceptual diagram showing a directory of a file management device in a conventional example.

FIG. 11 is an internal configuration diagram of a directory file of a file management device in a conventional example.

FIG. 12 is an external view showing a method of accessing a file of a file management device in a conventional example.

FIG. 13 is a diagram showing a procedure of how to actually access a file of a file management device in a conventional example.

[Explanation of symbols]

1 ... Central processing unit, 2 ... Display device, 3 ... Input device,
4 ... Main storage device, 5 ... File management device, 6 ... Secondary storage device, 51 ... File management table, 52 ... File management table registration means, 53 ... File management table updating means, 54 ... File management table reference means,
55 ... File management table deleting means.

Claims (1)

[Claims] 1. A central processing unit for processing requested information, a display unit for displaying windows, graphics, characters, etc., an input unit for inputting characters, numerical values, etc.
A file for registering current information of a file in the file management device in a computer including a main storage device for storing a running program such as S and window system and a secondary storage device for storing the file management device A file management table registration means that prepares a management table and secures an area for storing information about the file in the file management table when the file is created, and information about the file when erased, moved, or renamed File management table updating means for describing the file in the file management table, file management table reference means for extracting information from the file management table when a file cannot be accessed, and when deleted, moved, or renamed Information about files in regular File management apparatus characterized by comprising a file management table deletion means for deleting from the file management table.