JPH04107750A - File managing system - Google Patents

Abstract

PURPOSE:To effectively use a storage device as reducing managing man-hours and keeping the high speed access performance of a file by hierarchizing file configuration, and automatically transferring the file when insufficient capacity exists in a designated storage device and the generation of the file is impossible for the generation of the file by a user. CONSTITUTION:The process 31 of a process part 30 inputted to a computer system designates a threshold value to set the file as a transfer target to a file generating procedure 41 in the list form of the lower limit value and the upper limit value of the number of times of access, and outputs a request to generate the file 111. The file generating procedure 41 refers to a device group comprising information table 20, and satisfies the size of the file 111 requested to generate from the class of the storage device to be selected and the one with rank lower by one, and also, selects the storage device with largest null space, respectively. Thereby, it is possible to reduce the arrangement managing man-hours of the file and to effectively use the space of a storage device group.

Description

Detailed Description of the Invention [Field of Industrial Application] The present invention relates to a file management system, and particularly to a file management system for a computer system having multiple types of storage devices.

(Conventional technology) The conventional file management method is to select an appropriate storage device by the user himself or herself depending on the increase or decrease in the frequency of file use, and then run a utility program to change the storage location of the file to the corresponding storage device. was running.

Furthermore, in conventional file management systems, when duplicating files, the duplicated files are placed in the same type of storage device.

[Problem to be solved by the invention]

The conventional file management method described above makes it difficult for users who have a large number of files to manage all of them, leading to increased management costs. Since the files are placed on the copy side, it has the disadvantage that the same cost is incurred for the files on the copy side.

[Means for Solving the Problems] The file management method of the present invention improves access speed, storage capacity,
In a file management method for a computer system having multiple types of storage devices with different costs per hit, each of the storage devices is classified into one of multiple classes and hierarchized as specified by a system administrator,
means for registering the classification information in a device group configuration information table; and when a file creation request is issued to one of the storage devices, the file is duplicated in the two storage devices whose hierarchical levels differ by one class. means for reading from a storage device of a higher class when reading a duplexed file, and writing to the storage devices of both of the duplexed files when writing a duplexed file; When either one of the files is corrupted, a method is provided to restore the failed file to a normal file by copying the other file, and a method is provided in which the specified storage device does not have enough capacity to allow the user to create a file. If it is not possible to create a file, it automatically moves infrequently used files that exist in the same class in which the file was created to the storage device one class lower, and A file that registers information for controlling file transfer and access, including the frequency of use of the file and the name of the device where the file is placed, for each file. The information table is configured to include means for registering and updating the information table.

〔Example〕

Next, embodiments of the present invention will be described with reference to the drawings.

FIG. 1 is a block diagram showing an embodiment of the file management method of the present invention.

As shown in FIG. 1, in this embodiment, a device configuration group information table 20 that defines the class classification of storage devices that can be used in a computer system and a device configuration group information table 20 are created according to the specifications of the computer system operator. A system configuration information definition section 10 that creates and a process section 3 that creates files.
0, a file management unit 40 that processes requests for files from the process unit 30, a file information table 50 that is created for each file and that registers file transfer information, and a plurality of storage devices. Then, the file management unit 40 executes the file creation procedure 41
, file information table operation procedure 42.

It consists of a file access procedure 43, a file deletion procedure 44, and a file transfer procedure 45. Furthermore, the storage device group 60 is composed of many storage devices, and is hierarchically divided into three classes 61, 62, and 63.

Note that at the time of startup of the computer system, the system configuration information definition unit 10 registers information on the glass classification of the storage devices in the computer system in the device group configuration information table 20 in advance.

Therefore, the process 31 of the process unit 30 input into the computer system specifies the threshold value for the file to be transferred in the form of a list of the lower limit and upper limit of the number of accesses to the file creation procedure 41. and file 1
11 request for creation.

As a result, the file creation procedure 41 refers to the device group configuration information table 20 and selects the class of storage device to be selected and the class one level below it that satisfies the size of the file 111 requested to be created and is the most Select each storage device with the most free space. Here, the class of the storage device is explicitly designated by the user or automatically determined by a predetermined value.

If free space exists in both selected storage devices, a file 111 and a file 112, which is a copy of the file 111, are created on the selected storage devices. Furthermore, the file creation procedure 41 includes the file information table operation procedure 4.
2 to register information such as the threshold value, access record (0), file name, original and copy device names, and start address as a registration entry 51 in the file information table 50. . However, file 1
12 is directly visible to the user. After that, the process 32 similarly makes a file creation request by specifying the class of the storage device, and if there is insufficient free space on the corresponding class, the file creation request is made. The creation procedure 41 calls the file transfer procedure 45.

Therefore, in the file transfer procedure 45, the file access record is checked from the file information table 50, and if there is an original file that exists on the relevant class and whose access record is less than or equal to the lower limit of the threshold value, that file is moved. 2
If an attempt is made to move a file to a storage device in a lower class, and if there are files that have been copied more than the upper limit, the original file is copied to a storage device one class above, and the copied file is deleted (the copied file (equivalent to transferring the file to a device two classes higher), the storage device to which the file is to be transferred is similarly checked for free space, and if there is sufficient space, the transfer is performed.

Subsequently, the file information table operation procedure 42 is called, and the result of this migration is reflected in the file information table 50.

For example, when the free space of class 61 is 0, process 32 requests class 61 to create file 121, and if the access record of file 111 is less than or equal to the lower limit of the threshold, file 111 is transferred to file 113. The original information in the registered entry 51 is changed to that of the file 112, and the copied information is changed to that of the file 113. After that, the file creation procedure 41 is
The requested files 121 and 122 are created, and the file information table operation procedure 42 registers them in the file information table 50 as registration entries 52. As a result, it appears to the user as if the class to which the first file belongs has been lowered by one class.

Note that if a storage device is selected based on a default value rather than a user specification, and the file cannot be transferred because the storage device based on the default value does not have enough space, for example, the process 32 explicitly selects a class. If 61 is not specified and the default value is class 61, the file creation procedure 41 lowers the creation class of file 121 by one class, attempts to perform on class 62, and checks the free space again. and, if necessary, perform migration of existing files.

Further, if the file cannot be moved, the file creation request is rejected.

When the process 32 attempts to read the file 121 created in this way and issues a read request to the file access procedure 43, the file access procedure 43 reads only from the original file 121.

Also, if a write request is issued, file 121
, and file 122.

Furthermore, if one of the files is damaged during access, the file access unit 43 calls the file transfer procedure 45 and transfers the damaged file to the storage device where the damaged file existed or to the damaged file due to a failure in the storage device. If the existing storage device is unavailable, copy the other normal file to another storage device in the same class.
Repair by disabling corrupted files.

For example, if a failure occurs in the file 121 and it becomes unreadable, the file transfer procedure 45 copies the file 122 to another location on the abnormal device, calls the file information table operation procedure 42, Information on the start address of the new file is set in the registration entry 52.

On the other hand, when the process 31 requests the file deletion procedure 44 to delete the file 121, the file deletion procedure 4
4 calls the file information table operator [42 to delete the file information table 50 registration entry 52, and then releases the space of the file 121 and file 122 from both the storage devices where the original and the copy exist.

As a result, it is possible to reduce the number of man-hours required for file arrangement management and to effectively utilize the space of the storage device group, while maintaining file reliability and high-speed access performance as much as possible.

FIG. 2 is a flowchart showing an example of the operation of the file creation procedure 41 of this embodiment.

As shown in FIG. 2, in step 210, process 30
issues a file creation request to the file creation procedure 41, in step 211, the file creation procedure 41:
Referring to the device group configuration information table 20, the storage device with the most free space in the corresponding class is selected.

Next, in step 212, it is determined whether the amount of free space on each storage device is sufficient to create the file. If it can be created, step 220 secures space for the file on the relevant storage device, and step 221
Then, the entry is registered in the file information table 50.

If it is determined in step 212 that the free space on the storage device is insufficient for the file creation request and the file cannot be created, the file transfer procedure 45 is called in step 213, and the threshold value is satisfied on the corresponding storage device. A search is made for transportable files, if any, in step 214, the migration of the file one class up or down, and in step 215.
Then, the file information table 50 is changed, and this process is repeated until the requested file size becomes available.

In step 213, if the free space of the file does not meet the creation request and there are no files that can be transported,
In step 216, a check is made to see if the class for creating the file has been explicitly specified by the user, and if it has been explicitly specified by the user, the creation of the file is rejected in step 217.

In step 216, if the class for which the file is to be created is determined by default, in step 218, if the class of the storage device to be created is other than the lowest layer -1, in step 21, the class for which the file is to be created is determined. The class is changed to one lower than the class, and the process returns to step 212 to check the free space again and move the file if necessary.

Furthermore, if it is determined in step 218 that the class of the storage device to be created is the lowest level -1 and the file cannot be created, then in step 217 the file creation is rejected.

FIG. 3 is a flowchart showing an example of the operation of the file access procedure 43 of this embodiment.

As shown in FIG. 3, in step 230, the process section 3
0 issues an access request to the file access procedure 43, in step 231, the file access procedure 43
If the access request is a read, step 232
In step 233, reading is performed from the original file, and if the access request is for writing, writing is performed in both the original file and the copy file in step 233.

Thereafter, in step 234, the access record in the file information table 50 is counted up.

At this time, if an error occurs in either one in step 235, the repair destination is determined in step 237, depending on the type of error, in another location on the relevant storage device or another storage device in the relevant class. After copying the other normal file to the repair destination in step 238, the file information table 50 is rewritten in step 239, and the repair of the file in which the abnormality has occurred is completed.

If the error occurs in both files in step 235, the user is notified of the error in step 236.

FIG. 4 is a flowchart showing an example of the operation of the file deletion procedure of this embodiment.

As shown in FIG. 4, at step 240, process 30
When a file deletion request is issued to the file deletion procedure 44, the file deletion procedure 44 deletes the registered entry from the file information table 50 in step 241, and then deletes the original file and the copy file in step 242. files from storage devices that have
Free up space.

〔Effect of the invention〕

As described above, the file management method of the present invention has the effect of reducing file management man-hours for the user by automatically rearranging files.

In addition, the file management method of the present invention has one class of storage devices in which files with the same content are placed.
Files can be duplicated without wasteful use of storage devices such as using expensive storage devices on the copy side as well, and by using only the original side where file access is as fast as possible. This has the effect of improving the fault tolerance of files, maintaining high-speed access performance, and making effective use of the storage device.

Entry, 60...Storage device group, 61. ~63...
Class, 111. ~122...File.

Claims (1)

[Scope of Claims] In a file management method for a computer system having multiple types of storage devices with different access speeds, storage capacities, and costs per bit, each of the storage devices is divided into a plurality of storage devices according to a system administrator's designation. Classify and hierarchize into any of the classes,
means for registering the classification information in a device group configuration information table; and when a file creation request is issued to one of the storage devices, the file is duplicated in the two storage devices whose hierarchical levels differ by one class. means for reading from a storage device of a higher class when reading a duplexed file, and writing to the storage devices of both of the duplexed files when writing a duplexed file; When either one of the files is corrupted, a method is provided to restore the failed file to a normal file by copying the other file, and a method is provided in which the specified storage device does not have enough capacity to allow the user to create a file. If it is not possible to create a file, it automatically moves infrequently used files that exist in the same class in which the file was created to the storage device one class lower, and A file that registers information for controlling file transfer and access, including the frequency of use of the file and the name of the device where the file is placed, for each file. A file management method comprising: means for registering and updating an information table;