JP3489153B2 - File system - Google Patents

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a file system which takes out a file holding document data together with attributes and stores the document data together with attributes as a file, and more particularly to a file system capable of dynamically adding the attributes. .

[0002]

2. Description of the Related Art Conventionally, a file system has been provided with an attribute corresponding to document data, and this has been managed as a file unit.

Here, the attribute is information about a file such as a file name, a creation date and time, and a modification date and time, and the document data A and the document data AA have the file name attribute "a" and the attribute "a", respectively.
It is managed by being identified by "a". If the document data AA is the document data obtained by partially modifying the document data A, new document data is obtained based on the attribute “1993/10/20” and the attribute “1993/10/22” of each modification date and time. To identify and manage.

Generally, in a file system,
The attributes used by the user were specific to the file system.

[0005]

As described above, in the conventional file system, an attribute that is usually used is set, and this attribute is unique to the file system. The special attribute when using is set by the application itself and managed independently.

Therefore, there is a problem in that the search function or the like of the file system itself cannot be effectively used, and the function of the file system is not effectively used.

In addition, when the attributes of the file system itself are to be changed, it is necessary to manage the conversion of all the files to the changed attributes.

The conversion work in this case takes a lot of time, and the use of the file system is interrupted during the conversion work, so that the file system cannot be effectively used.

Therefore, the present invention eliminates such problems,
The load on the application that uses the file system is reduced, the interruption time of the file system due to the addition of the new attribute is eliminated, and the new attribute can be added even during the operation of the file system. The purpose of the present invention is to provide a file system that can be effectively used.

[0010]

In order to achieve the above object, the invention of claim 1 comprises a file storing means for storing a file and an attribute holding means for holding attribute information in which a value corresponds to an attribute identifier. A file attribute management means for managing the file of the file storage means and the attribute information held by the attribute holding means in association with each other; If there is no attribute, the attribute holding means is provided with attribute control means for performing attribute registration processing. According to the invention of claim 2, a file storage means for storing a file, an attribute holding means for holding attribute information in which a value corresponds to an attribute identifier, and an attribute management in which an attribute name and a type correspond to the attribute identifier. An attribute management information holding unit that holds information, a file attribute that manages the file of the file storage unit, the attribute information held by the attribute holding unit, and the attribute management information held by the attribute management information holding unit in association with each other When the management means and the attribute holding means are not searched for the attribute identifier when reading the attribute of the file and the attribute management information holding means is searched for by the attribute identifier and the attribute identifier is present, the attribute holding is held The means is provided with an attribute control means for performing registration processing.

[0011]

According to the invention of claim 1, the file storage means stores the file, the attribute holding means holds the attribute information in which the attribute identifier is associated with a value, and the file attribute management means is the file storage means. Of the file and the attribute information held by the attribute holding means are managed in association with each other, and the attribute control means searches the attribute holding means with an attribute identifier when reading the attribute of the file, and if the attribute identifier does not exist, the attribute is held. Attribute registration processing is performed in the holding means. According to the invention of claim 2, the file storing means stores the file, the attribute holding means holds the attribute information in which the attribute identifier is associated with a value, and the attribute management information holding means holds the attribute in the attribute identifier. The attribute management information holding the name and the type in correspondence is held, and the file attribute management means holds the file of the file storage means, the attribute information held by the attribute holding means, and the attribute management held by the attribute management information holding means. The information is managed in association with the information, and the attribute control unit searches the attribute holding unit with the attribute identifier when reading the attribute of the file and does not have the attribute identifier, and the attribute management information holding unit searches with the attribute identifier to search the attribute. When there is an identifier, the attribute holding means performs the registration process.

As a result, a new attribute can be added without interrupting the file system and without requiring conversion work for registration by the user.

[0013]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will be described below with reference to the drawings.

FIG. 1 is a diagram showing the configuration of a file system which is an embodiment of the present invention.

In FIG. 1, the file system is roughly composed of a storage unit 1, an attribute control unit 2 and an instruction unit 3.

The storage unit 1 stores a file such as document data in a file storage unit 4 and manages extended attribute management information that can be freely extended by a user by using the extended attribute identifier 5a and the extended attribute management information 5b. The extended attribute management information holding unit 5 that holds the attached management information, the extended attribute holding unit 6 that holds the extended attribute, and the management information and the extended attribute that the file and extended attribute management information holding unit 5 in the file storage unit 4 hold The file extension attribute management unit 7 manages the extension attributes held by the holding unit 6 in association with each other.

Here, in this embodiment, the attributes are managed by being divided into basic attributes and extended attributes. The basic attributes are basic attributes held by the file system in the initial state, and the extended attributes are attributes that can be newly added by the user.

The attribute control unit 2 is instructed by searching a file attribute access unit 11 for accessing a file attribute, a basic attribute access unit 8 for accessing a basic attribute, and an extended attribute based on an instruction from the instruction unit 3. Expanded attributes are stored in storage unit 1
If not stored, the extended attribute registration unit 9 requests the extended attribute registration unit 9 to register the extended attribute, and the extended attribute registration unit performs the extended attribute registration process. Have nine.

Next, the storage state of files and their attributes in each unit of the storage unit 1 will be described.

FIG. 2 is a diagram showing the structure of files in the file storage unit 4.

In FIG. 2, each file is composed of a file identifier, basic attributes, and an electronic document which is document data. Here, the file identifier FID1, the basic attribute A1, and the electronic document D1 are the file identifier, the basic attribute, and the electronic document of the file (1), respectively, and the file identifier FID2, the basic attribute A2, and the electronic document D2 are respectively The file identifier (2), basic attributes, and electronic document. In this way, a plurality of files are successively stored in the file storage unit 4, and in this file storage unit 4, only basic attributes are stored as attributes.

FIG. 3 is a diagram showing the structure of the management information of the file extension attribute management unit 7.

FIG. 3A shows a format of management information. One management information is a file identifier of a file stored in the file storage unit 4, an identifier of the extended attribute management information holding unit 5, and an extended attribute holding. It is composed of the identifier of the part 6 and the following address. FIG. 3B shows a specific configuration of management information, and one management information M1 is
File identifier FID1, identifier MID1 of extended attribute management information holding unit 5, identifier EID1 of extended attribute holding unit 6,
The next management information M2 is sequentially constructed from the start address "0010". Then, the next management information M2 is composed of the file identifier FID2, the identifier MID2 of the extended attribute management information holding unit 5, the identifier EID2 of the extended attribute holding unit 6, and the start address "0020" of the next one management information M3. It The next piece of management information M3 includes a file identifier FID3 and an identifier MI of the extended attribute management information holding unit 5.
D1 and the identifier EID3 of the extended attribute holding unit 6, and the start address "0030" of the next management information M4 are sequentially configured. In this way, the management information is stored in the file storage unit 4 shown in FIG.
D1), the identifier (MID1 etc.) for the extended attribute management information holding unit 5, and the identifier (EID1 etc.) for the extended attribute holding unit 6 are associated as one management information (M1 etc.). One management information (M1 and the like) has a list structure with the address of the next one management information.

FIG. 4 is a diagram showing the structure of the extended attribute management information in the extended attribute management information holding section 5.

FIG. 4A shows the format of the extended attribute management information. The extended attribute management information is the extended attribute identifier,
It is composed of the attribute name, the type of the attribute used to calculate the size of the area holding the attribute value and interpret the value on the computer, the attribute initial value, and the start address of other attribute management information.

FIG. 4B shows specific extended attribute management information. One extended attribute management information EM1 forming the extended attribute management information MM1 is "EXID1" as an extended attribute identifier and an attribute name. "Administrator", type "character string", attribute initial value "miyawaki",
The configuration is such that the next address is "0110", and one extended attribute management information EM2 indicated by the next address of this one extended attribute management information EM1 has "EXID2" as the extended attribute identifier and "size" as the attribute name. , “Number” as the type, “0” because there is no attribute initial value, and “0” is set because there is no next extended attribute management information.

In this way, the extended attribute management information MM1
Has a list structure in which one next extended attribute management information EM2 is connected by the next address of one extended attribute management information EM1. If the next address is "0", there is no next extended attribute management information as described above, that is, it indicates the end of the list, and "0".
The address of does not exist on the file system.

Extended attribute management information MM1 of this list structure
To MMn correspond to the identifiers (MID1 and the like) of the extended attribute management information holding unit 5 shown in FIG. For example, the identifier MID1 shown in FIG. 3 is shared by the file having the file identifier FID1 and the file having the file identifier FID3, and the extended attribute management information indicated by the identifier MID1 is the extended attribute management information shown in FIG. It is stored as MM1. Further, as shown in FIG. 3, the identifier MID2
Corresponds to the file with the file identifier FID2,
The extended attribute management information indicated by this identifier MID2 is stored as the extended attribute management information MM2 shown in FIG. That is, the extended attribute management information holding unit 5 is stored as the extended attribute management information MM1 to MMn having a list structure corresponding to each of the identifiers (MID1 etc.) in the file extended attribute management unit 7.

FIG. 5 is a diagram showing the structure of the extended attribute information in the extended attribute holding unit 6.

FIG. 5A shows the format of the extended attribute information, which includes the extended attribute identifier, the attribute value,
And the start address of other extended attribute information.

FIG. 5B shows concrete extended attribute information. One extended attribute information EV1 forming the extended attribute information V1 is "EXD1" as an extended attribute identifier and "java" as an attribute value. , As the next address "021
0 ”, and this one extended attribute information EV1
One extended attribute information EV2 indicated by the address next to is "EXID2" as the extended attribute identifier and "1" as the attribute value.
000 "and there is no next extended attribute information, so the next address is set to" 0 ".

As described above, the extended attribute information V1 has a list structure in which the next extended attribute information EV2 is connected by the address next to one extended attribute information EV1.

Extended attribute information V1 to Vn of this list structure
Is an identifier (EID1 of the extended attribute holding unit 6 shown in FIG.
Etc.). For example, the identifier EI shown in FIG.
D1 is a file (1) having a file identifier FID1
The extended attribute information indicated by this identifier EID is stored as extended attribute information V1 shown in FIG. That is, the extended attribute holding unit 6 is stored as the extended attribute information V1 to Vn of the list structure corresponding to each of the identifiers (EID1 and the like) in the file extended attribute management 7.

The extended attribute identifiers EXID1 and EXID2 shown in FIGS. 4 and 5 are the same identifier and correspond to each other.

Then, as described above, the file extended attribute management unit 7 stores the file in the file storage unit 4, the extended attribute management information in the extended attribute management information holding unit 5, and the extended attribute information in the extended attribute holding unit 6. The relationship is managed by management information. Further, the extended attribute management information and the extended attribute information are associated with each other by the extended attribute identifier.

Next, the operation of the attribute controller 2 will be described with reference to the flowchart.

FIG. 6 is a flowchart showing the operation of the attribute controller 2.

In FIG. 6, the file attribute access unit 1
1 determines whether the type of attribute input from the instruction unit 3 is a basic attribute or an extended attribute (step 100).

When it is determined in step 100 that the file has the extended attribute, the file attribute access unit 11 obtains the extended attribute management information / extended attribute information identifier (MID, EID) of this file from the file extended attribute management unit 7. It is acquired (step 101). Then, it is determined whether the operation type is attribute registration or attribute reading (step 1
02) In the case of attribute registration, the extended attribute registration unit 9 performs registration setting of the attribute value (step 103), and returns the registered and set value to the instruction unit 3 (step 105). On the other hand, in step 102, in the case of attribute reading, the extended attribute search unit 10 acquires the attribute value (step 104) and returns the acquired value to the instruction unit 105 (step 105).

On the other hand, when it is judged in step 100 that the attribute is the basic attribute, the file attribute access unit 11
Acquires the basic attribute instructed by the basic attribute access unit 8 from the file storage unit 4 (step 106) and returns the value to the instruction unit 3 (step 105).

In this manner, the attribute values of the basic attribute and the extended attribute can be registered and read.

Next, the extended attribute search unit 1 in step 104
An attribute value search process based on 0 will be described with reference to a flowchart.

FIG. 7 is a flow chart showing an attribute value search processing procedure of the extended attribute search unit 10.

In FIG. 7, first, the extended attribute search unit 10
Performs a search process on the extended attribute holding unit 6 using the extended attribute identifier (step 200). Then, it is determined whether there is an extended attribute identifier based on this search result (step 201).

If there is an extended identifier in step 201, the storage unit 1 is accessed by the address of the search result, the attribute value is acquired (step 202), and the acquired attribute value is returned (step 205), The process ends.

On the other hand, in step 201, if there is no extended identifier, the extended attribute registration unit 9 is requested to perform processing without specifying the attribute registration value (step 203), and the return value from the extended attribute registration unit 9 is returned. As an attribute value (step 20
4) Then, this attribute value is returned (step 205), and the process ends.

Next, the extended attribute registration section 9 in step 103.
The registration process of the attribute value by will be described based on a flowchart.

FIG. 8 is a flowchart showing an attribute value registration processing procedure of the extended attribute registration unit 9.

In FIG. 8, first, the extended attribute registration unit 9
The extended attribute holding unit 6 is searched by the extended attribute identifier (step 300). Then, it is determined whether or not there is an extended attribute identifier based on this search result (step 301).

If there is an extended attribute identifier in step 301, the address of the search result is set as the start address of the extended attribute (step 305), and the process proceeds to step 306.

On the other hand, when there is no extended attribute identifier in step 301, the extended attribute management information holding unit 5 is further added.
For the extended attribute identifier (step 3
02), based on this search result, it is judged whether or not there is an extended attribute identifier (step 303).
An error is returned (step 313) and the process is terminated. If there is any, attribute type information is further obtained based on the search result, an area is created in the storage unit 1, an extended attribute identifier and Is set to "0", and the address of the area is set as the start address of the extended attribute (step 30
4) The process moves to step 306.

In step 306, it is judged whether or not the registered value is further received (step 306), and if it is received, it is further judged whether or not the type of this attribute is matched (step 314). Step 31
If it does not exist, the error is returned (step 315) and the process ends.

On the other hand, when the registered value is not received in step 306, the extended attribute management information holding unit 5 is searched by the extended attribute identifier (step 307), and if there is no registered value as a result of this search, The error is returned (step 313) and the process ends. If there is, an attribute initial value is obtained and this value is set as a registered value (step 309), and the process proceeds to step 310.

In step 310, after setting the registered value in the area created in step 304, the address of this area is set to the next address at the end of the extended attribute holding unit (step 311), and this set value is set. The return value is set (step 312), and the process ends.

Next, a search process of the extended attribute management information holding unit 5, the extended attribute holding unit 6, and the file extended attribute management unit 7 will be described based on a flowchart.

FIG. 9 is a flow chart showing a search processing procedure common to the extended attribute management information holding unit 5, the extended attribute holding unit 6, and the file extended attribute management unit 7.

In FIG. 9, first, the start address is acquired from the extended attribute management information holding unit 5, the extended attribute holding unit 6, or the file extended attribute management unit 7 (step 40).
0). Then, it is judged whether or not this head address is "0" (step 401), and if it is "0", the address "0" indicating that there is no identifier is returned (step 405), and the processing is executed. finish.

On the other hand, if it is not "0" in step 401, it is further judged whether the identifier at the head address and the identifier of the search are equal (step 402). If they are not equal, the next address is obtained (step 402). Step 40
3) The process shifts to step 401 and the above-mentioned processing is repeated. If they are equal to each other, the address with the matched identifier is returned (step 404) and the processing is ended.

Next, the process of adding the extended attribute management information and the extended attribute information will be described with a specific example. In addition,
As a premise, it is assumed that the extended attribute management information and extended attribute information shown in FIGS. 4 and 5 have already been set.

FIG. 10 is a diagram for explaining addition of extended attribute management information, and FIG. 11 is a diagram for explaining addition of extended attribute information.

First, in FIG. 10, FIG. 10A shows the extended attribute management information to be added, and the extended attribute identifier is "E".
XID3 ”, the attribute name is“ affiliation ”, the type is“ character string ”, and the attribute initial value is“ KSP ”. And FIG.
As shown in (b), when this extended attribute management information is added as an extended attribute to the file (1),
The identifier MI corresponding to the file identifier FID1 of the file (1) in the management information of the extended attribute management information holding unit 5
One extended attribute management information EM to be added in the extended attribute management information MM1 in the extended attribute management information holding unit 5 indicated by D1.
3 is linked to one extended attribute management information EM2.

That is, one extended attribute management information EM2
Next address "0" is one extended attribute management information EM
3 is set to the value of the start address “0120” of FIG.
The extended attribute management information shown in (a) is stored in a predetermined format. At this time, one extended attribute management information E
Since there is no address corresponding to the next address of M3, this next address is set to "0" to indicate the end of the list structure.

Here, when the reading of the extended attribute added to the file (1) is instructed, the extended attribute information corresponding to the extended attribute management information does not exist in the extended attribute holding unit 6 (see FIG. a)), first, the file attribute access unit 11 instructs the extended attribute search unit 10 to read this extended attribute.

The extended attribute search unit 10 includes an extended attribute holding unit 6
However, since this extended attribute does not exist, the address "0" is returned as the return value. Then, the extended attribute search unit 10 confirms that this extended attribute does not exist from this address “0”, and instructs the extended attribute registration unit 9 to register the extended attribute without specifying the registered value.

On the other hand, the extended attribute registration unit 9 obtains the extended attribute management information EM3 of this extended attribute from the extended attribute management information holding unit 5, and stores it in the storage unit 1 as shown in FIG. One extended attribute information EV3 in which the information regarding the value of is written in a predetermined format is created. Furthermore, the start address "0220" of this created area is
The extended attribute information V1 in the extended attribute holding unit 6 is written to the address next to the one extended attribute information EV2, and one extended attribute information EV3 is linked to one extended attribute information EV2. The address next to the added extended attribute information EV3 is set to "0" to indicate that there is no next extended attribute information. As a result, one extended attribute EV
11 is changed to the extended attribute information V1 including 3 (FIG. 11).
(D)).

As a result, the new extended attribute to be added is
It is registered as an extended attribute of file (1). The extended attribute registration unit 9 returns the registered value as a return value, the extended attribute search unit 10 returns the value as an attribute value, and the reading instruction of the attribute value is completed.

As a result, a new attribute is added at runtime, and the attribute initial value described in the extended attribute management information is returned as the attribute read value.

After that, since the extended attribute is registered in the extended attribute holding unit 6, this value is registered / read as the attribute already defined.

In this case, although the reading process of the attribute that does not exist in the extended attribute holding unit 6 is performed, in the registration process, the file attribute access unit 11 directly gives the extended attribute registration unit 9 a registration instruction, It becomes possible to perform additional processing at the same time with the same attribute. In this case, the value instructed by the instruction unit 3 is used as the registered value instead of the attribute initial value.

[0070]

As described above in detail, according to the first aspect of the invention, a file storing means for storing a file,
Attribute holding means for holding attribute information in which a value corresponds to an attribute identifier, file attribute management means for managing the file of the file storage means and the attribute information held by the attribute holding means in association with each other, Since the attribute holding means is searched by the attribute identifier at the time of reading the attribute and the attribute holding means performs the attribute registration processing when the attribute identifier does not exist, the new method is provided even during the operation of the file system. The attributes can be added, the file system interruption time is eliminated, and the file system can be effectively used. According to the invention of claim 2, a file storage means for storing a file, an attribute holding means for holding attribute information in which a value corresponds to an attribute identifier, and an attribute management in which an attribute name and a type correspond to the attribute identifier. An attribute management information holding unit that holds information, a file attribute that manages the file of the file storage unit, the attribute information held by the attribute holding unit, and the attribute management information held by the attribute management information holding unit in association with each other When the management means and the attribute holding means are not searched for the attribute identifier when reading the attribute of the file and the attribute management information holding means is searched for by the attribute identifier and the attribute identifier is present, the attribute holding is held Since the means is equipped with an attribute control means for performing registration processing, new attributes can be added even during operation of the file system. It eliminates the downtime of the file system has the advantage that can be effectively utilized in the file system.

Further, since the addition of a new attribute of a file system is automatically corrected and changed for the entire file system, the correction and change time required for adding a complicated new attribute is shortened and the correction and change are performed. This has the advantage of reducing errors due to.

Further, since the file system search function is effectively used to perform the modification / change processing of the attribute accompanying the addition of the new attribute, it is necessary to add the new attribute to the application using this file system. There is an advantage that it is possible to perform unified file management without providing the function of.

[Brief description of drawings]

FIG. 1 is a diagram showing the configuration of a file system that is an embodiment of the present invention.

FIG. 2 is a diagram showing a configuration of files in a file storage unit 4.

FIG. 3 is a diagram showing a configuration of management information of a file extension attribute management unit 7.

FIG. 4 is a diagram showing a configuration of extended attribute management information in an extended attribute management information holding unit 5.

FIG. 5 is a diagram showing a configuration of extended attribute information in an extended attribute holding unit 6.

FIG. 6 is a flowchart showing the operation of the attribute control unit 2.

FIG. 7 is a flowchart showing an attribute value search processing procedure of the extended attribute search unit 10.

FIG. 8 is a flowchart showing an attribute value registration processing procedure of the extended attribute registration unit 9.

FIG. 9 is a flowchart showing a search processing procedure common to the extended attribute management information holding unit 5, the extended attribute holding unit 6, and the file extended attribute management unit 7.

FIG. 10 is a diagram illustrating addition of extended attribute management information.

FIG. 11 is a diagram illustrating addition of extended attribute information.

[Explanation of symbols]

1 storage unit 2 attribute control unit 3 instruction unit 4 file storage unit 5 extended attribute management information holding unit 5a extended attribute identifier 5b extended attribute management information 6 extended attribute holding unit 7 file extended attribute management unit 8 basic attribute access unit 9 extended attribute registration Part 10 Extended attribute search unit 11 File attribute access unit

Claims (2)

(57) [Claims] 1. A file storage means for storing a file, an attribute holding means for holding attribute information in which a value corresponds to an attribute identifier, a file of the file storage means, and the attribute information held by the attribute holding means. And an attribute control means for performing attribute registration processing on the attribute holding means when the attribute holding means is searched for when reading the attribute of the file and the attribute identifier does not exist. A file system comprising: 2. A file storage means for storing a file, an attribute holding means for holding attribute information in which a value corresponds to an attribute identifier, and attribute management information in which an attribute name and type correspond to an attribute identifier. Attribute management information holding means, a file attribute management means for managing the file of the file storage means, the attribute information held by the attribute holding means, and the attribute management information held by the attribute management information holding means in association with each other, When reading the attribute of the file, if the attribute holding means is searched for by the attribute identifier and the attribute management information holding means is searched for by the attribute identifier, and the attribute identifier is present, registration processing is performed in the attribute holding means A file system comprising: an attribute control unit for performing the following.