JP2689116B2 - Optical disk storage management method - Google Patents

Description

Description: TECHNICAL FIELD The present invention relates to a storage management method for an optical disc that stores a data file and search information set in each data file. [Prior Art] In recent years, an optical disk apparatus using an optical disk in which an optical storage medium is formed in a disk shape as a storage medium has been put into practical use, and an image data filing apparatus which handles a large amount of data, or a large capacity It is applied to auxiliary storage devices and the like. The track pitch is 1-2 on the surface of this optical disc.
A μm recording track is formed, and data is stored by changing the state (eg, reflectance) of the surface of this recording track in accordance with the data to be recorded. In many cases, when data is recorded, the surface of the recording track is destroyed, so that the recorded data cannot be directly updated on the recording track. In addition, on the optical disc, data is recorded / reproduced in sector units of a predetermined length (for example, 2048 bytes), which increases the degree of freedom of file access and improves error correction processing for correcting data errors. You can do it well. Each file contains information about the contents of the file, such as the creator, the creation date, and the file, so that the desired file can be quickly found (searched) from the large number of files stored on the optical disk. Type, file format, file attributes, and
Search information (secondary information for management) including a title and the like is added. Here, the attribute of the file indicates, for example, whether the data forming the file is image data or character code data, and in the case of image data, indicates the number of bits per pixel. Information etc. are included. By the way, conventionally, a file management system for recording / reproducing data on / from an optical disk centrally manages files and search information, which causes the following inconveniences. That is, since the search data are dispersed in the data file that occupies most of the storage area of the optical disc, when a plurality of search data are continuously accessed, most of the movement of the head crosses the data file and it takes time. Cause Further, since the search data is also updated every time the record is updated, the search data is distributed in the data file in which the record is frequently updated, and therefore, seek operations frequently occur during access and the access time increases. Cause [Purpose] The present invention has been made in order to solve the disadvantages of the prior art, and an object of the present invention is to provide a storage management method for an optical disk, which allows a file management system to operate files and search information in different systems. . [Structure] According to the present invention, in a storage management method of an optical disc for storing a data file and search information set in each data file, the search information is stored in an area of a predetermined size, and the search information is added. If there is no free space in the area at the time point, a new area is secured, and the search information of the necessary data file among the data files and the search information to be added are written in the new area and thereafter. The search information is added to the new area. Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings. FIG. 1 shows an optical disk system according to one embodiment of the present invention. This system includes a host device HST and an optical disk device ODE. In the host device HST, the central processing unit 1 is for performing various data processing such as processing for the file system according to the present invention, the processing program is stored in the program memory 2, and the work area is the work memory 3 Is formed. The CRT display device 4 and the keyboard 5 form a man-machine interface with the host device HST, and the magnetic disk control device 6 and the magnetic disk drive device 7 are auxiliary storages mainly used in the host device HST. Make up the device. The optical disk interface 8 is for exchanging data between the host device HST and the optical disk device ODE.
This is for exchanging data with an external device such as an image reading device or an image recording device. Then, these central processing unit 1, program memory 2, work memory 3, CRT display device 4, keyboard 5,
Data is exchanged between the magnetic disk controller 6, the optical disk interface 8, and the external interface 9 via the system bus 10. In the optical disk device ODE, the optical disk control device 11
Is for exchanging data with the host device HST and recording / reproducing data on / from the optical disk driven by the optical disk drive device 12. As is well known, an optical disc has a physical format for recording / reproducing data in units of a predetermined length of sector, and a sector address is set for each sector. In this embodiment, one sector is
It consists of 2048 bytes (2K bytes). 2 (a) to 2 (e) exemplify a divided state of a storage area of an optical disk. The storage area of the optical disk is divided into two areas: a data area AD for storing a data file and a management information area AM for storing management information for accessing the data file. It is divided into a header area HD, a system area SM, and a search data area KY. In this case, the sector address O matches the head of the management information area AM, and the tail of the data area AD matches the last sector address accessible from the outside. The system area SM is a file for efficiently accessing the system area link information for indicating a secondary system area (not shown) that is secured when the system area SM is full, and a file header (described later). FID in which an identifier (hereinafter referred to as FID) directory (described later) is stored
It is composed of a directory area and a file header area in which a file header that registers the recording state in the data area AD or the search data area KY of each data file or search data file is stored. The search data area KY includes search data area link information for indicating a secondary search data area (not shown) that is secured when the search data area KY is full, and search data. It consists of a search data file area in which files are stored. The header area HD includes a volume mark for displaying characteristics and the like of the optical disc, a data area last sector number indicating a last sector number (sector address) of the data area AD,
A header area last sector number indicating the last sector number of the header area HD, a volume name for identifying the optical disc,
Start logical block address of the system area SM (hereafter, LB
A), the system area size indicating the size of the storage area allocated to the area in sector units, various control flags, the FID directory area start LBA indicating the FID directory area start LBA, and the like. Indicates the size of the storage area allocated to the area in sector units
FID directory area size, file header area LBA that indicates the head LBA of the file header area, file header area size that indicates the size of the storage area allocated to the area in sector units, and head LBA of the search data area KY It is composed of a search data area start LBA, a search data area size indicating the size of the storage area allocated to the area in sector units, and a data area start LBA indicating the start LBA of the data area AD. Therefore, based on the contents of the header area HD, the identification of the optical disk and the allocation status of each area can be known. Here, in general, the LBA and the sector address (sector number) are the same, but a physically defective sector is replaced by another good sector by the optical disk device ODE, so that not all the sectors are identical. Note that the replacement sector area is set further outside the data area AD. The system area link information is at the beginning of the next system area.
The first LBA of the next system area that indicates the LBA, the next system area size that indicates the size of the storage area allocated to the same area in sector units, a control flag for displaying the presence or absence of the next system area, the FID directory in the next system area Next FID directory area showing the first LBA of the area First LBA of the area, next FID directory area size showing the size of the storage area allocated to the same area in sector units, next file header showing the first LBA of the file header area in the next system area Area head LBA, next file header area size that indicates the size of the storage area allocated to the area in sector units, and file header number (hereinafter referred to as FNO; described later) assigned to the first file header in the next file header area Indicates the next file header beginning FNO and the end in the next file header area Next file header final FNO showing the FNO allocated to the file header
Consists of Therefore, based on the system area link information, the presence or absence of the next system area and the allocation status of each area in the next system area can be known. The search data area link information includes a next search data area start LBA indicating the next search data area start LBA, a next search data area size indicating the size of the storage area allocated to the area in sector units, And a control flag for displaying the presence or absence of the next search data area. Therefore, based on the search data area link information, the presence / absence of the next search data area and the allocation status of the next search data area can be known. When the system area SM and the search data area KY are full, the next system area and next search data area link information is secured in the empty area of the data area AD at that time, and at the same time, the system area link Information and search data area link information are respectively formed and stored. In the FID directory area, as shown in FIG. 3 (a), FID directory blocks are stored in sector units. Each FID directory block has a block header, a predetermined number, as shown in FIG. 3 (b). FID
It consists of a directory and a block header backup. The contents of the block header and the block header backup are the same, and the first FNO of the next FID directory block indicating the first FNO of the next FID directory block is stored as shown in FIG. One FID directory is made up of an FID, a version number (hereinafter, referred to as VNO), and an FNO, as shown in FIG. Here, FID is set for the host device HST to identify the file (data file or search data file; the same applies below), and VNO and FNO are set to the optical disk device ODE when the file header is generated / updated. Is set automatically. Note that VNO is set to 1 when a file is generated, and thereafter, is incremented with updating. For example, if the size of the block header and the backup of the block header is 24 bytes and the size of the FID directory is 10 bytes, 200 FID directories are stored in one FID directory block. Therefore, in that case, every time 200 new file headers are formed, 200 FIDs corresponding to those file headers are created.
The directory is recorded in a new FID directory block. At the time of this recording, the 200 FID directories
Sorted in ascending order using FID and VNO as keys. In the file header area, as shown in FIG. 4A, a file header block is stored in sector units.
For example, 16 file headers are stored in one file header block as shown in FIG. In this case, the size of one file header is 128 bytes. There are two types of file headers, a basic file header FDN as shown in FIG. 4 (c) and an extended file header FDE as shown in FIG. 4 (d). The basic file header FDN includes a basic file header management information section FDNa for identifying each basic file header FDN, and a mapping data section MPNa for registering a recording state of a file managed by the file header. The extended file header FDE includes an extended file header management information section FDEa for identifying each extended file FDE, and a mapping data section MPEa for registering a file recording state. The basic file header management information section FDNa is a file header identifier with a value "1" that indicates that the file header is a basic file header FDN, and the number of consecutive file headers that indicates the number of extended file header FDEs that follow this basic file header FDN. , FNO, FID, VNO, the file type for identifying whether the file managed by this file header is a data file or a search data file, the generation date indicating the date when the file was generated, the file The update date that represents the date when the file was updated, the file size that represents the total data size of the file, the maximum record size that represents the size of the largest record (described later) when the file is a data file, and after the file is created / updated. End of empty area of data area when closed It consists of a data area current pointer representing the head LBA, and a search data file area current pointer representing the head LBA of the current search data file when the file is closed after being generated / updated. Here, the file header number FNO is set as follows. That is, when generating one file header, using the LBA of the file header block in which the file header is stored and the offset (order number starting from 0) of the file header in the file header block, the following expression is used. Is calculated. FNO = LBA × 16 + (offset) The extended file header management information section FDEa is registered in the mapping data section MPEa of the file header identifier, FNO and the extended file header FDE having the order in which the sequence is continuous with the basic file header FDN. It consists of an extended file type that indicates the type of record that is present. The FNO has the same value as the FNO of the corresponding basic file header FDN. Here, the configurations of the data file and the search data file will be described. As shown in FIG. 5 (a), one data file is made up of a plurality of records each having a variable length and composed of a set of data. For example, when the data file is image data, one record corresponds to one page of image data. However, a plurality of records constituting one data file are not always recorded in a continuous area. Since data recording / reproduction on the optical disk is performed in units of sectors (SC), the data of each record is recorded on the optical disk in units of sectors. Also,
If there is an empty area in the last sector where the record is recorded,
The empty area is filled with “0”. In addition to the types of records that are recorded in the continuous area, there are divided records that are divided into a plurality of segments and recorded as shown in FIG. 5B. Also in this case, each record segment is recorded in sector units, and if there is an empty area in the last sector in which the record segment is recorded, the empty area is filled with "0". The area of one search data file is shown in FIG.
As shown in (1), a plurality of blocks having the same size as a sector are secured in a continuous area. This area is secured when the search data file is generated, and thereafter, the contents of the search data file are recorded in the empty blocks of the secured area as required by the host system. Also in this case, recording / reproduction of data is performed in units of blocks (sectors), and each block is designated by an order number from the head of the area. Therefore, in the mapping data part MPNa of the basic file header FDN and the mapping data part MPEa of the extended file header FDE, records such as those shown in FIGS. 6 (a) to 6 (d) depending on the type of each file and record. Definition data NSR, split record definition data SDR, split record map data SDM, and search data file definition data KYM are arranged. The record definition data NSR includes a record type taking a value “0” representing a non-divided record, a record identifier for identifying each record in the file, a record size representing a record size, and a head LBA of the record. It consists of the LBA at the head of the record. The divided record definition data SDR includes a record type, a record identifier, and a value that take a value “1” representing the divided record.
Record size, the number of segments that represent the number of record segments that make up the record, and the divided record map data that registers data about the first record segment of that divided record in the mapping data section MPEa of the next extended file header FDE It consists of a segment map offset indicating the order of SDM. The divided record map data SDM is composed of a segment number indicating the order of the record segments in the divided record, a record identifier, a segment length indicating the size of the segment, and a record segment start LBA indicating the start LBA of the record segment. The search data file definition data KYM is a search data block size that indicates the size of the area allocated to the search data file, and the head of the search data file that indicates the head LBA of the area allocated to the search data file. Consists of LBA. Therefore, a data file consisting of the records 1 to 4 shown in FIGS. 5A and 5B, and FIG.
The file header indicating the search data file shown in FIG. 7 is as shown in FIGS. 7A and 7B, respectively. That is, the file header of the data file includes the basic file header FDN1 and the extension file header FDE1, and the file header of the search data file includes the basic file header FDN2. In the mapping data part of the basic file header FDN1,
The record definition data NSR1 to NSR3 of the records 1 to 3 and the divided record definition data SDR4 of the record 4 are arranged in the record order, and the mapping data part of the extended file header FDE1 includes the divided record map data SDM1 of the record segment of the record 4. , SDM2 are arranged in segment order. Note that the record identifiers of the divided record map data SDM1 and SDM2 have the same value as the record identifier of the divided record definition data SDR4. In the mapping data part of the basic file header FDN2,
Search data file definition data KYM1 corresponding to the area allocated to the search data file is arranged. FIG. 8 shows a general format of a file header of a data file. However, if the file header fits only in the basic file header, no extended file header is added, and if it does not include a divided record, no extended file header having a divided record definition part is added to the mapping data part. With the above configuration, the central processing unit 1 records / reproduces data on / from the optical disk as follows. In this case, a control process for recording / reproducing data on the optical disc (hereinafter, referred to as an optical disc file system) and a control process for a higher-order file system (hereinafter, referred to as a file system), that is, setting of FID for a file , Data file configuration (for example, record configuration, etc.),
The configuration of the search data file and processing such as file search are performed by the central processing unit 1. When the optical disk is set in the optical disk device ODE, first, the optical disk file system transfers the contents of the FID directory area of the system area SM to the magnetic disk device (consisting of the magnetic disk control device 6 and the magnetic disk drive device 7; the same applies hereinafter). read out. At this time, if there is a file header that is not registered in the FID directory, the file header is read and a FID directory (hereinafter referred to as the current directory) for the file header of the unregistered portion is formed on the magnetic disk device. At this time, change the FID directory data in the current directory to FID and VNO.
Sort in ascending order using as a key. In addition, the file header is generated /
When updated, the corresponding FID directory data is formed, and the FID directory data in the current directory is rearranged on the magnetic disk device in the same manner as described above. Then, when 200 pieces of FID directory data (that is, FID directory blocks) are formed in the current directory, the 200 pieces of FID directory data are recorded in a new FID directory block of the optical disc. Now, in the file system, with the FID of the search data file that registers the necessary search information specified,
Requests the optical disk file system to open a file. As a result, the optical disc file system refers to the F
The FNO of the file header with the ID is found, the target search file data is read by referring to the file header, and the contents are transferred to the file system. Thereby, the file system searches for the target data file based on the contents of the search data file,
Get the FID for that data file. When the file system completes reading the search data file, it instructs the optical disk file system to close the search data file. When reading the data file, the optical disk file system is requested to open the file with the FID of the data file specified. Therefore, the optical disk file system finds the FNO of the file header having the designated FID by referring to the FID directory, reads out the target file data by referring to the file header, and transfers the contents to the file system. When a desired data file is obtained in this way, the file system performs a process according to the type of the data file. For example, the contents of the data file are displayed on the CRT display device 4 so that the operator can confirm the contents and the operator can perform desired processing. When the operator closes the data file without any operation on the data file, the file system requests the optical disk file system to close the file. Thereby, the optical disk file system closes the opened data file. When the operator performs any operation on the data file, for example, deletes or adds a record, the file system transmits a command and data for updating the data file corresponding to the operation to the optical disk file system. Output to As a result, the optical disk file system updates the data corresponding to the command and creates a new file header in the work memory 3 with the update,
Further, the current directory is updated based on the file header. Then, when closing the accessed data file, the optical disk file system records the file header formed by the access in the temporary buffer formed in the magnetic disk device. When updating the content of the search data file in conjunction with the creation / update of the data file, the file system records the FID attached to the search data file, the block number indicating the block for recording the update content, and the update data. The update data is transferred to the optical disk file system with the number of blocks to be specified specified. Thereby, the optical disk file system obtains the FNO corresponding to the designated FID by referring to the FID directory, and reads the file header. Then, the target search data file is found, and the data transferred from the file system is sequentially recorded from the designated block. When the recording is completed, the file system instructs the optical disc file system to close the search data file. When a series of operations is completed and the operator instructs to remove the optical disk, the optical disk file system stores the file header created in the temporary buffer of the magnetic disk device at that time in a new file header block. , Optical disk drive
The optical disk is ejected from 12. In this manner, the data file and the search data file can be recorded on the optical disc and read out. FIG. 9 shows an example of processing performed by the optical disk file system when a request for inputting / outputting data from / to the optical disk is received from the file system. First, when an input / output request to the optical disk is received from the file system (process 101), whether the command is open data file, register data in data file, close data file, or close search data file. Check whether it is generation, open search data file, close search data file, or other processing (decision 102, 103, 10)
4,105,106,107,108). When the result of determination 102 is YES, a file header for the data file is created in the work memory 3 so as to be continuous at the end of the file header registered in the current directory at that time (process 109). When the result of the determination 103 is YES, the data transferred at that time is recorded in the empty area of the data area AD, and the file header with the same FID and VNO increased by 1 is recorded corresponding to the recorded state. Then, the current directory is updated corresponding to the file header (process 110). When the result of determination 104 is YES, and when the file header related to the opened data file is updated, the file header is recorded in the empty area of the temporary buffer formed in the magnetic disk device (Process 11).
1). When the result of judgment 105 is YES, the area of the search data file having the specified FID is secured for the number of blocks specified in the empty area of the search data file area, and the new search data file is related. A file header is formed in the work memory 3 (process 112). When the result of determination 106 is YES, the FID directory is referred to based on the designated FID, the corresponding FNO is obtained, and the file header of the target search data file is read based on the FNO (process 113). When the result of determination 107 is YES, the transferred search data file is recorded in the specified block of the search data file that has already been opened (process 11).
Four). When the result of determination 108 is YES, and when the search data file opened at that time is newly created, the file header corresponding to it is recorded in the temporary buffer of the magnetic disk device (process.
115). When the result of determination 108 is NO, other designated processing is performed (processing 116). By the way, if you add a new area to the area reserved in the search data file so that there is no empty area, or change the contents of the search data file that has been used up to that point, Can be upgraded as follows. One method is to add a new area K to the area KF1 reserved in the search data file as shown in FIG. 10 (a).
It is to add F2. In this case, the file header has an area in the map data section.
From the FD1 (VNO is 1) where only the FK1 search data file definition data KYM1 is located, the area FK1 in the map data section
FD in which the search data file definition data KYM1 and the search data file definition data KYM2 in area FK2 are sequentially arranged
Updated to 2 (VNO is 2). When designating a block in the area FK2, the sequence number passed from the first block of the first area FK1 is used. If an empty area exists in the area FK1, the empty area in the area FK1 can be accessed even after the area FK2 is added. The second method is, as shown in FIG. 6B, that the recording data of the area FK3 reserved in the search data file is appropriately selected from the beginning of the area FK4 in which only necessary data is newly reserved. It is to rearrange in order. In this case, the file header has an area in the map data section.
From FD3 (VNO is 1) where search data file definition data KYM3 for FK3 is located, to FD4 (V where search data file definition data KYM4 for area FK4 is located in the map data section
NO is updated to 2). In this case, the data to be moved from the area FK3 to the area FK4 is selected by the host system of this optical disk file system (in this case, the file system). Of these methods for upgrading the search data file, the latter method can reduce the access time when reading the search data file because only the necessary data remains in the upgraded search data file. There are advantages. Moreover, the host system of this optical disk file system can select one of the version upgrade methods. FIG. 11 shows a processing example when the optical disk file system upgrades the search data file. First, when a request is input from the host system to update the search data file (process 201), the FID directory is referenced based on the FID specified at that time to obtain the corresponding FNO, and the search data is retrieved. The file header of the file is read (process 202). Next, set an area of the size specified by the host system in the empty area of the search data file area (Process 20
3), it is checked whether the request at that time is addition of a region (decision 204). When the result of determination 204 is YES, the FNO, VNO, etc. of the read file header are corrected, and the file header in which the search data file definition data KYM of the area set in process 203 is added to the mapping data section is formed ( Processing 205), it is recorded in the temporary buffer of the magnetic disk device. When the result of the judgment 204 is NO, the FNO and VNO of the read file header are corrected, and the file header is formed by replacing the contents of the mapping data section with the search data file definition data KYM of the area set in step 203. (Process 206), and records it in the temporary buffer of the magnetic disk device. In this way, the search data file is upgraded. Thereafter, the host system records the data in the area secured as the new version search data file. As described above, according to the present embodiment, the data file and the management secondary information (search data file) for searching / managing the data file can be recorded / managed in different systems. Information can be accessed efficiently. Further, since one piece of management secondary information is recorded in the continuous area, the access time for reading can be shortened. Further, since the size of the management secondary information can be arbitrarily set according to the search system of the host system, it can be easily applied to various search systems. In the above-described embodiment, the data set in the management secondary information is only the search data, but in addition to that,
It is also possible to include data representing the format and attributes of the file. [Effect] As described above, according to the present invention, in the optical disk storage management method for storing the data file and the search information set in each data file, the search information is stored in an area of a predetermined size. In addition to storing, when there is no space in the area at the time of adding the search information, a new area is secured, and the search information of the necessary data file among the data files and the search information to be added are added to the new area. Since the search information is added to the new area thereafter, the search information is added to the new area, so that only the necessary search information is sequentially stored in the newly secured search information storage area. Is saved, and the access time for reading out the search information can be significantly shortened.

BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is a block diagram showing an optical disc system according to an embodiment of the present invention, and FIGS. 2 (a) to 2 (e) are schematic diagrams illustrating division states of storage areas of an optical disc. Fig. 3 (a)
4A to 4D are schematic diagrams showing a configuration example of a file identifier directory area, FIGS. 4A to 4D are schematic diagrams showing a configuration example of a file header, and FIGS. 5A to 5C. Is a schematic diagram showing a configuration example of recording data, and FIGS. 6 (a) to (d).
Is a schematic diagram illustrating the data arranged in the mapping data part, FIGS. 7A and 7B are schematic diagrams illustrating the file header, and FIG. 8 is a schematic diagram illustrating a general example of the file header. FIG. 9 is a flow chart showing an example of processing performed when a data input / output request is received from a host system, FIG.
FIGS. 11A and 11B are schematic diagrams showing an example of upgrading the search data file, and FIG. 11 is a flowchart showing an example of processing when upgrading the search data file. HST: Host device, ODE: Optical disk device.

Claims (1)

(57) [Claims] In an optical disk storage management method for storing a data file and search information set in each data file, the search information is stored in an area of a predetermined size, and there is a space in the area when the search information is added. If not, a new area is secured, the search information of the necessary data file among the data files and the search information to be added are written in the new area, and thereafter, in the new area. On the other hand, a storage management method for an optical disk, characterized in that search information is added.