JP3707400B2 - Recording method and recording apparatus - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a recording method for recording data on a rewritable recording medium using a hierarchical file system. In particular, the present invention restores the information when a failure occurs in information indicating the actual data recording location of the file. The present invention relates to a recording method. The present invention also relates to a recording apparatus that uses the recording method.
[0002]
[Prior art]
In recent years, development of high-density optical disks represented by DVD (Digital Versatile Disc) has progressed, and standardization has been promoted. As a result, UDF (Universal Disk Format) is designed to absorb as much as possible the differences in various physical storage formats depending on the media type and to construct a logical structure that provides highly common information storage units for applications. Was formulated. A rewritable DVD-RAM (DVD-Random Access Memory) uses a logical format according to this UDF. The UDF can be applied to a writable CD-R and a rewritable CD-RW.
[0003]
The UDF is configured by a hierarchical file system, and sub-directories and substantive files are referred to from information stored in the root directory. The UDF is further referred to a sub directory or a substantial file from information stored in the sub directory. Hereinafter, the directory is abbreviated as “Dir.”.
[0004]
The recording area on the disk is accessed with a sector as a minimum unit. For example, in a DVD-RAM, access is made from the inside to the outside of the disk. From the innermost side, a system area in which volume information is written is arranged following the lead-in area, and here, VRS (Volume Recognition Sequence), MVDS (Main Volume Descriptor Sequence), LVIS (Logical Volume Integrity Sequence) and AVDP (Anchor Volume Descriptor Pointer) is written.
[0005]
Route Dir. The position of the recording area where the file entry (File Entry, hereinafter abbreviated as “FE”) is written is recognized by sequentially referring to MVDS and FSD from AVDP. The FE includes file and directory attribute information and an allocation descriptor (hereinafter abbreviated as “AD”). AD is information on the logical address and size (length) of a file or directory, and a recording area in which actual data (actual data) of the file is recorded or a recording area in which the actual directory is recorded. Is shown.
[0006]
Route Dir. Root of Dir. The logical address and size are indicated. Route Dir. Includes one or more file identifier descriptors (hereinafter abbreviated as “FID”), and the root Dir. The sub-Dir. FE and file FE are referenced. By these FEs, the corresponding sub-Dir. The file entity is referenced by each AD. Sub-Dir. The entity may further include one or more FIDs. That is, in the UDF, the root Dir. Sub-Dir. Recorded on the disc except for. A file is accessed and recognized in the order of FID, FE, and entity using FID and FE as pointers. In UDF, the FID, FE, and entity may be written anywhere in the recordable area.
[0007]
[Problems to be solved by the invention]
By the way, when the disc is being used, a failure occurs in the FE of the file indicating the recording area (location) where the actual data of the file is recorded, and the drive device cannot read the FE of the file. There is a case. In such a case, since the FE of the file cannot be read even if there is no failure in the actual data of the file, for example, moving image data or audio data, the actual data cannot be accessed. was there.
[0008]
SUMMARY OF THE INVENTION Accordingly, an object of the present invention is to provide a recording method and apparatus capable of restoring a FE of a file by referring to the backup when a failure occurs in the FE of the file by backing up the FE of the file. Is to provide.
[0009]
[Means for Solving the Problems]
In the present invention, a recording method for recording data on a recording medium based on a hierarchical file system records management information for managing the hierarchical structure of the file system in a specific area of the recording medium, and stores the management information in the specific area. The use area is treated as a special file, and information indicating the location where the actual data of the file is recorded is recorded twice as regular information and preliminary information on the recording medium, thereby reducing the size of the special file. Thus, the designation information indicating the place where the regular information and the preliminary information are recorded is recorded in a portion vacated in the specific area.
[0010]
In the present invention, a recording apparatus for recording data on a recording medium based on a hierarchical file system includes means for recording management information for managing the hierarchical structure of the file system in a specific area of the recording medium, Means for treating the unused area of the file as a special file, means for dually recording information indicating the location where the actual data of the file is recorded on the recording medium as regular information and preliminary information, and the special file. And means for recording designation information indicating the location where the normal information and the preliminary information are recorded in a portion vacated in the specific area.
In such a recording method and recording apparatus, information indicating the location where the actual data of the file is recorded is recorded twice, so that the safety of the information can be improved.
[0011]
According to the present invention, in such a recording method and recording apparatus, when the regular information becomes unreadable due to a failure or the like, the regular information can be newly restored on the recording medium using the preliminary information. For this reason, even if regular information cannot be read, the actual data of the file can be read. In addition, when the regular information can no longer be read, the spare information is used to restore the regular information each time, so that the actual data of the file can be read unless the regular information and the spare information cannot be read simultaneously. .
[0012]
In the present invention, in the recording method described above, the entire specific area is copied as it is to another area and the entire copied specific area is handled as one backup file, so that a part of the management information cannot be read. If the data corresponding to the part of the backup file is used to reduce the size of the special file, the management information that cannot be read into the vacant part generated in the specific area is stored. Restore the department.
[0013]
In such a recording method, the original management information can be restored using the backup file, so that even if a failure occurs in a part of the management information, the actual data recorded on the recording medium is surely reproduced. can do. Since the data to be restored is placed in the specific area where the original management information is placed, the management information can be put together in the specific area even after the restoration. For this reason, even after restoration, the hierarchical structure of the file system can be read at a high speed, and the reproduction start time can be shortened compared to the conventional case.
[0014]
Further, according to the present invention, in the recording method described above, information on the initial location and size in the special file and information on the current location and size in the special file are recorded in the specific area.
[0015]
In such a recording method, information on the initial location and size in the special file and information on the current location and size in the special file are recorded in the specific area. The size can be reliably recognized.
[0016]
DETAILED DESCRIPTION OF THE INVENTION
Hereinafter, embodiments of the present invention will be described with reference to the drawings. In addition, in each figure, the same code | symbol is attached | subjected about the same structure.
[0017]
FIG. 1 is a schematic diagram showing the logical format of a disk-shaped recording medium in association with the disk shape.
[0018]
In FIG. 1, the logical format of the disk-shaped recording medium 10 conforms to UDF (Universal Disk Format). In the disk-shaped recording medium 10, a lead-in area 11 is arranged on the innermost periphery. A logical sector number (hereinafter abbreviated as “LSN”) is assigned from the outside of the lead-in area 11, and in order, a volume information area 12, an RSA (Reserved Space Area) 15, and an SMA (Space Management Area) 16. , An FSA (Free Space Area) 17 and a volume information area 13 are arranged, and a lead-out area 14 is arranged on the outermost periphery. The logical sector number is based on the reference “0” at the head sector of the volume area 12. On the other hand, RSA15, SMA16, and FSA17 are assigned logical block numbers (hereinafter abbreviated as “LBN”) with the leading sector of RSA15 as reference “0”.
[0019]
In the volume information area 12, VRS, MVDS, and LVIS are written based on the UDF rules. AVDP is placed in the LSN 256 in the volume information area 12. Furthermore, the AVDP is also written in the sector of the last logical sector number and the sector of (final logical sector number -256). The contents of the MVDS are written twice as a RVDS (Reserve Volume Descriptor Sequence) in the volume information area 13 inside the lead-out area 14.
[0020]
A partition area is provided between logical sector numbers 272 and (final logical sector number -272). RSA15, SMA16, and FSA17 are arranged in this partition area. The RSA 15 provided on the innermost periphery side of the partition area is composed of an FSDS (File Set Descriptor Sequence) and an SBD (Space Bitmap Descriptor) based on the UDF regulations. Descriptor). The SBD stores information indicating the entire free recording area of the disk-shaped recording medium 10 and expresses this by setting a flag for each sector. FSD is the root Dir. In the hierarchical structure of the file system. The logical address and size of the FE for are shown.
[0021]
SMA 16 is the root Dir. FE, root Dir. , BOS (Backup Of Space Management File) FE, SMF (Space Management File) FE, and SMF entity. In the SMA 16, as described later, the necessary amount of the SMF entity is reduced as necessary, so that the sub-Dir. FE, sub-Dir. Is placed. That is, the FID and the directory FE are recorded together in the SMA 16.
[0022]
The SMF is composed of two entities, each pointed to by AD [0] and AD [1] in the SMF FE. The first entity of the SMF is an area that is indicated by AD [0] and is reserved for describing the logical address and size information of the area that is initially reserved as the second entity of the SMF. The second entity of the SMF is indicated by AD [1], and is reserved for use for the FID or directory FE created during recording of data on the disk-shaped recording medium 10 after the formatting process. It is an area.
[0023]
In this way, the SMF is divided into two entities, and information on the initial location and size of the second entity is described in the first entity, so that the location where the SMF FE is recorded, the route Dir. The SMA 16 can be defined regardless of where the FE is recorded. Further, sub-Dir. Deletion or root Dir. It is possible to flexibly deal with deletion of files below.
[0024]
In such an SMF, an unused area of the SMA 16 is secured with a predetermined capacity in advance as a file with a specific attribute. By treating the unused area as a file as an SMF, it is possible to prevent the unused area from being recognized as a free recording area in the SBD described above.
[0025]
Here, the route Dir. FE, root Dir. 1 and the SMF FE may be stored at any location in the SMA 16, but from the viewpoint of performing high-speed access to these, it is desirable to record them continuously as shown in FIG.
[0026]
As already described in the conventional example, the FE indicates the logical address and size of a file or directory entity. This information is recorded by AD in FE. The FID indicates the logical address and size of the FE by the name of the file or directory and the ICB (Information Control Block) in the FID.
[0027]
The FSA 17 is an area in which the FE of the file and the actual data (data) of the file are placed, and the BOS entity (actual data of the BOS) is also placed here. The BOS entity is a file for backing up management information collectively recorded in the SMA 16, and is a complete copy of the SMA 16 obtained by referring to the SMF AD [0] entity. The BOS FE indicating the logical address and size of the BOS entity is recorded in the SMA 16 and backed up in the BOS entity.
[0028]
In the FSA 17, it is preferable that the FE of the file and the actual data of the file corresponding to the FE are continuously arranged in address. When adding a file, it is preferable that the FE of the file to be added is arranged continuously with respect to the existing file, and further, the file data is arranged continuously with respect to the address. In this way, by arranging the file FE and the actual data of the file continuously in terms of addresses, the file can be accessed at high speed.
[0029]
Next, an example of the formatting method of the disc-shaped recording medium 10 will be described. It is assumed that the lead-in area 11 and the lead-out area 14 have already existed before the formatting process, for example, created in advance during the pressing process in the manufacturing process of the disc-shaped recording medium 10. The formatting process proceeds from the inner circumference side to the outer circumference side of the disc-shaped recording medium 10.
[0030]
When the formatting process is started, AVDP is first written to a plurality of predetermined addresses, and the above-described VRS, MVDS, and LVIS are written from outside the lead-in area 11.
[0031]
Next, a partition is created. In the partition, first, RSA 15 is created, FSDS is written, and root Dir. Is determined. Then, an SBD is created. At this time, the SMF area is secured by making the SMF area described above a used area in the SBD.
[0032]
When the SBD is created and the RSA 15 is created, the SMA 16 is created from the outside of the RSA 15 next.
[0033]
In creating the SMA 16, first, based on the FSD written by the RSA 15, a route Dir. Sector and root describing FE of Dir. Sectors describing the entities of the Dir. FE and entity are written.
[0034]
Route Dir. The entity of the parent Dir. FID, SMF FID, and BOS FID. The SMF FID specifies the location of the SMF FE, and the BOS FID specifies the location of the BOS FE.
[0035]
At this time, the attributes of SMF and BOS are specified in each FID. The attributes of the designated SMF and BOS are for preventing the SMF and BOS from being erased, rewritten, moved, etc. by other devices or OS (Operating System). For example, “hidden file attribute” is designated as an attribute of SMF and BOS, respectively. The “hidden file attribute” is an attribute that makes it impossible to browse a file with this attribute set by a normal method.
[0036]
Next, a BOS FE is created and an AD that specifies the location and size of the BOS entity is placed here. Here, the size of the BOS entity is such a size that the BOS entity can completely copy the information of the SMA 16.
[0037]
Next, an SMF FE is created. In the formatting process, the SMF FE uses AD [0] for specifying the location and size in the first entity file, and AD [1] for specifying the location and size in the second entity file. It is configured with.
[0038]
Since the file exists only by specifying the FE, the area for placing the SMF entity and the area for placing the BOS entity are secured by creating the BOS FE and the SMF FE, respectively.
[0039]
In addition, a “read-only file attribute” and a “system file attribute” are specified for each FE of BOS and SMF, respectively. The “read-only file attribute” is an attribute indicating that a file in which this attribute is set is read-only, and change or deletion is prohibited by the system. The “system file attribute” is an attribute indicating that the file in which this attribute is set is a file necessary for the system. By designating these three attributes to BOS and SMF, respectively, it is possible to prevent processes such as erasure, rewriting, and movement on BOS and SMF other than intentional operations. These attributes can be canceled by a well-known predetermined method.
[0040]
Next, the route Dir. The first SMF entity is created so as to be contiguous with the sector describing the actual entity, and the initial logical address and size of the second SMF entity are described therein. That is, the logical address and size in the second entity of the SMF secured during the format process are described in the first entity of the SMF. The format of this description is described in AD format following UDF, and in this specification, this pseudo AD is expressed by [AD]. Since there is a possibility that the second entity of the SMF is expanded and there are a plurality of [AD], in order to indicate this number, it is described in the format of AED (Allocation Extentor) following UDF. This pseudo AED is expressed as [AED] in this specification.
[0041]
Thus, by making SMF exist in SMA 16, the free area of SMA 16 can be secured by SMF. After the formatting process, the sub-Dir. FE and entity are written, the area in the second SMF entity is deleted, and these sub-Dir. FEs and entities are created in SMA 16.
[0042]
In this way, the SMA 16 is created. The outside of the SMA 16 is an FSA 17. In the FSA 17, a BOS entity is created using a part thereof. The substance of the BOS is actual data in which management information for managing the hierarchical structure of the file system recorded in the SMA 16 is filed. That is, at the time of formatting, the BOS entity is the root Dir. FE, root Dir. , BOS FE, SMF FE, and SMF entities. The entity of the parent Dir. FID, SMF FID, and BOS FID.
[0043]
The FSA 17 excluding the BOS entity area is an unused area in which actual file data is recorded after the formatting process. Then, the RVDS is created by skipping the area designated as the FSA 17. The RVDS is created and the formatting process of the disc-shaped recording medium 10 is completed.
[0044]
Next, after the formatting process, the sub-Dir. How to add files and files.
[0045]
First, sub-Dir. 1, ..., sub-Dir. A case where X,... Are added will be described.
[0046]
Route Dir. Sub-Dir. An FID indicating 1 is added. At this time, the route Dir. If there is a vacancy in the sector in which the entity is stored, the sector is added. On the other hand, if there is no vacancy in the sector, after the area size (size) in the second entity of the SMF is reduced, the Dir. 1 FID is added.
[0047]
Next, sub-Dir. In order to add 1 FE, the size of the area in the second SMF entity is reduced.
[0048]
Next, sub-Dir. In order to add one entity (for example, the FID of the parent Dir., The FID of the child file), the size of the second entity of the SMF is further reduced.
[0049]
Next, the AD [1] information in the SMF FE is updated to reflect the size change in the second SMF entity so far.
[0050]
Next, the BOS entity is rewritten to reflect the change of the SMA 16. That is, the contents of the SMA 16 are read and written in the area allocated to the BOS entity as it is. The entity of the BOS is the root Dir. FE, root Dir. , BOS FE, SMF FE, SMF AD [0] pointed to, sub-Dir. 1 FE and sub-Dir. 1 and the root Dir. The entity of the parent Dir. FID, SMF FID, BOS FID and sub-Dir. 1 FID, sub-Dir. 1 entity is the parent Dir. FID and the FID of the child file.
[0051]
Such an operation is performed by sub-Dir. 2, Sub-Dir. 3, ..., sub-Dir. X,...
[0052]
In the above-described processing, every time the content of the SMA 16 is changed, the content of the BOS entity that backs up the content of the SMA 16 is changed. However, the present invention is not limited to this. The timing (timing) when the content of the BOS entity is changed is counted when the disk-shaped recording medium 10 is inserted into or removed from the drive device, every predetermined period of time, or the FID added to the root / Dir entity. It may be a predetermined number, for example, every third time, or a user instruction.
[0053]
On the other hand, in the above description, the case of adding a directory has been described, but the case of adding a file is as follows.
[0054]
Route Dir. The FID indicating the new file is added to the entity. At this time, the route Dir. If there is a vacancy in the sector in which the entity is stored, the sector is added. On the other hand, if there is no free space in the sector, the size of the area in the second entity of the SMF is reduced, and then the FID of the new file is added to the free area due to the reduction. In this case, since the size of the second entity of the SMF is changed, the AD-1 information in the SMF FE is updated. Next, the FE of the new file is added to the FSA 17 area. Next, the entity of the new file is added to the FSA 17 area. In this way, the FE and entity of the file are arranged in the FSA 17.
[0055]
As a result of such an operation, the new file is transferred to the root Dir. In addition, information related to the added new file is collectively recorded in the SMA 16 together with information related to the already recorded directory.
[0056]
By the way, for example, the route Dir. Below many sub-Dir. Or a new file is added, the root Dir. FID and sub-Dir. FE, Sub-Dir. A large number of FIDs of new files in the entity will be added. As a result, the SMA 16 may become full due to the added FE or FID.
[0057]
In such a case, when there is a free space in the FSA 17, the free space is used, and the FSA 17 is further assigned to a plurality of SMA areas, so that the second SMA 16-2 that is an extended area of the SMA 16 and the data The second FSA 17-2 corresponding to the FSA for recording the file is newly created outside the position in the FSA 17 where the file exists.
[0058]
Next, the sub-Dir. An operation for backing up the FE of a file when a file is created will be described.
[0059]
FIG. 2 is a schematic diagram for explaining the structures of SMA and FSA before creating a backup for a file entry of a child file.
[0060]
FIG. 3 is a diagram showing a file identification descriptor.
[0061]
FIG. 4 is a schematic diagram for explaining creation of a backup for a file entry of a child file.
[0062]
FIG. 5 is a diagram showing a format of implementation use.
[0063]
2, FIG. 2 is a schematic diagram expressing the recording areas arranged concentrically or spirally on the disk-shaped recording medium 10 in a straight line, and FIG. 2A mainly represents the SMA 16 and FIG. Represents FSA17.
[0064]
In the disk-shaped recording medium 10 shown in FIG. 2, the route Dir. A plurality of sub-Dir. Is created and sub-Dir. Is further sub-Dir. And files are created. For example, a plurality of sub-Dir. Sub of Dir. X is the root Dir. Created under the sub-Dir. A child file (child file) is created in X.
[0065]
Sub-Dir. And the file has been created, the SMA 16 determines that the root Dir. FE, root Dir. , BOS FE, SMF FE, SMF AD [0] entity, multiple sub-Dir. FE, these sub-Dir. And SMF AD [1] are recorded. Route Dir. The entity of the parent Dir. FID, SMF FID, BOS FID and multiple sub-Dir. FID.
[0066]
As shown in FIG. 2B, the FSA 17 includes a BOS entity, a file FE, file actual data, and a free recording area (a recording area in which no meaningful information is recorded). For example, sub-Dir. The FE location of the child file in X is sub-Dir. It is stored in the ICB of the FID of the child file in the entity of X, and the location of the actual data of the child file is stored in AD [0] in the FE of this child file.
[0067]
In the UDF, as shown in FIG. 3, the FID includes a descriptor tag, a file version number, a file character, a length of file identifier, and an ICB. , Length Of Implementation Use, Implementation Use, File Identifier, and Padding.
[0068]
The details will be given in the UDF standard, but briefly described. The Descriptor Tag is an identifier for identifying a descriptor, and the Descriptor is determined by the Tag Identifier. File Version Number is the version number of the file. File Characteristics is a file attribute such as whether it is a hidden file or a directory. Length Of File Identifier is the size (length) of the file ID. As described above, the ICB stores the logical address and size of the FE. Length Of Implementation Use is the size of implementation use. Implementation Use will be described later. File Identifier is an identifier of a file. Since the FID has a variable length, Padding is inserted in order to arrange the FID into an integral multiple of 4 bytes (bytes).
[0069]
Then, as shown in FIG. 4, a BFE (Backupped File Entry) for backing up the FE of the child file is created in the FSA 17. The creation of the BFE as a spare is performed when the FE of the regular child file is created.
[0070]
In FIG. 4, BFE is recorded following the actual data indicated by BFE, but may be recorded in any recording area of FSA 17.
[0071]
The BFE has the same contents as the FE to be backed up, and the logical address and size of the actual data of the child file to be backed up are stored in AD [0].
[0072]
In order to indicate BFE, Implementation Use in the FID of the child file is expanded.
[0073]
As shown in FIG. 5, Implementation Use includes Flag, Identifier, OS Class, OS Identifier, Implementation Use Area, and Logical Block Number Of Backup.
Consists of BFE.
[0074]
Flag, Identifier, OS Class, OS Identifier, and Implementation Use Area are based on the UDF standard, and Logical Block Number Of Backup BFE is an extended part in this embodiment.
[0075]
The details will be given to the UDF standard, but briefly explained. The OS Class and OS Identifier are used in conjunction with each other, and the operating system (OS) on which the implementation (the entire device including the drive device) is operating. Show. The Implementation Use Area is an area where the implementation can be used freely.
[0076]
The Logical Block Number Of Backup BFE stores the location of the BFE that backed up the regular FE, and this location is indicated by a logical block number.
[0077]
The Logical Block Number Of Backup BFE is also described in the Implementation Use of the FID of the child file in the BOS entity.
[0078]
The UDF standard is published on, for example, the OSTA (Optical Storage Technology Association) homepage (http://www.osta.org/html/ostaudf.html), and anyone can download it from this homepage. Can do.
[0079]
Next, a description will be given of the recovery operation when the FE of the regular child file placed in the FSA 17 cannot be read.
[0080]
FIG. 6 is a schematic diagram for explaining processing for recovering a file entry of a child file in which a failure has occurred.
[0081]
FIG. 6 is a schematic diagram expressing the recording areas arranged concentrically or spirally on the disk-shaped recording medium 10 in a straight line. FIG. 6A mainly represents the SMA 16, and FIG. 6B represents the FSA 17. Represent.
[0082]
In FIG. 6, sub-Dir. X's FID is the root Dir. The sub-Dir. X FID sub-Dir. The FE of X is indicated. This sub-Dir. Sub-Dir. The entity of X is pointed to. Sub-Dir. The entity of X is the parent Dir. The FID of the child file is indicated by the ICB in the FID of the child file.
[0083]
In such a case, if the FE of the child file cannot be read due to a failure, Implementation refers to Implementation Use in the FID of the child file.
[0084]
Next, Implementation checks the Logical Block Number of Backup BFE of Implementation Use, and acquires the logical block number of the BFE that is a backup.
[0085]
Next, the Implementation refers to the BFE from the logical block number of the BFE and copies the contents to the free recording area of the FSA 17 to restore the FE as the FE of the regular child file.
[0086]
Next, Implementation rewrites the contents of the ICB in the FID of the child file in SMA 16 in order to point to the FE of the restored child file.
[0087]
Next, the Implementation rewrites the contents of the FID of the child file in the BOS entity in the SFA 17 in order to reflect that the contents of the ICB have been rewritten.
[0088]
As a result, a new link is established to the FE of the restored child file, the restored FE of the child file is referenced from the FID of the child file, and the actual data of the child file can be read. Even if some failure occurs in the FID of the child file, the FID of the child file is restored by referring to the FID of the child file in the BOS entity, and the FID of the restored child file is restored. Point to the FE of the child file.
[0089]
In addition, every time the FE of the regular child file cannot be read, the FE of the regular child file is restored using the spare BFE, so that both the FEs cannot be read at the same time. Real data can be read.
[0090]
Here, when there are a plurality of files, there are a plurality of BFEs corresponding to the files, but these BFEs may be handled as one file. In this case, the FID of this BFE file is the root Dir. The FE is created in the SMA 16 and is created in the SMA 16. By treating the BFE as a file in this way, an operating system that does not support BFE cannot use the function of backing up the FE of the file. Can be treated as a medium. When setting BFE file attributes, “hidden file attributes” are specified in the BFE FID, and “read-only file attributes” and “system file attributes” are specified in the BFE FE.
[0091]
Next, drive devices that can be applied to the present invention will be described.
[0092]
FIG. 7 is a diagram illustrating a configuration of an example of the drive device.
[0093]
Here, the above-described disk-shaped recording medium 10 is a recording medium using a phase change metal material for the recording layer, and the drive device 50 controls the temperature applied to the recording layer by adjusting the output of the laser to control the crystal / Data is recorded on the disk-shaped recording medium 10 by a phase change technique for changing the state to amorphous.
[0094]
7, the drive device 50 includes a spindle motor 51, an optical pickup 52, a laser driver 53, a recording equalizer 54, a buffer memory 55, and an encoder / decoder circuit 56 (hereinafter abbreviated as “ENC / DEC circuit”). 56, a thread mechanism 57, an RF signal processing circuit 58, an address extraction 59, a drive control microcomputer 60, an interface (hereinafter abbreviated as “I / F”) 61, a servo circuit 62, and a memory 63.
[0095]
The spindle motor 51 rotates the chucked disk-shaped recording medium 10, and the rotation speed is servo-controlled by a servo circuit 62.
[0096]
Data recording / reproduction with respect to the disk-shaped recording medium 10 is performed by the optical pickup 52. The optical pickup 52 is thread-transferred in the radial direction of the disc-shaped recording medium 10 by the thread mechanism 57.
[0097]
Data from the external digital device 71 is supplied to the drive device 50 via an I / F 61, for example, a SCSI (Small Computer System Interface). Here, the digital device 71 may be any digital device as long as it can input and output digital signals and the interface is suitable. Further, it may be built in these devices.
[0098]
An ENC / DEC circuit 56 and a drive control microcomputer are connected to the I / F 61. The ENC / DEC circuit 56 includes a buffer memory 55, a recording equalizer 54, an RF signal processing circuit 58, a servo circuit 62, and a drive control microcomputer. 60 is connected.
[0099]
The memory 55 is a buffer memory that holds write data or read data. Write data is supplied from the digital device 71 to the ENC / DEC circuit 56 via the I / F 61. The ENC / DEC circuit 56 generates data in the above-described format at the time of recording, and then encodes the data according to the format. Then, the ENC / DEC circuit 56 performs a decoding process at the time of reproduction, and outputs digital data to the digital device 71 via the I / F 61.
[0100]
For example, the address is added as a subcode in the ENC / DEC circuit 56, and is also added to the header in the data.
[0101]
Data from the ENC / DEC 56 is supplied to the laser driver 53 via the recording equalizer 54. The laser driver 53 generates a drive waveform having a predetermined level necessary for recording data on the disc-shaped recording medium 10. The output of the laser driver 53 is supplied to the laser in the optical pickup 52, the laser beam having an intensity corresponding to the output is irradiated onto the disk-shaped recording medium 10, and data is recorded. Further, in the laser driver 53, the intensity of the laser beam is appropriately controlled by APC (Automatic Power Control) in the RF signal processing circuit 58 as described above.
[0102]
On the other hand, the signal generated by the optical pickup 52 due to the return light from the disc-shaped recording medium 10 is supplied to the RF signal processing circuit 58. The address extraction circuit 59 extracts address information based on the signal supplied from the RF signal processing circuit 58. The extracted address information is supplied to the drive control microcomputer 60.
[0103]
In addition, the RF signal processing circuit 58 generates a tracking error signal TE and a focus error signal FE when the matrix amplifier calculates the detection signal of the photodetector in the optical pickup 52. A tracking error signal TE and a focus error signal FE are supplied to the servo circuit 62.
[0104]
The drive control microcomputer 60 controls the seek operation using the address, and controls the laser power using the control signal. The drive control microcomputer 60 includes a CPU (Central Processing Unit), a RAM (Random Access Memory), a ROM (Read Only Memory), and the like, and includes an I / F 61, an ENC / DEC circuit 56, an RF signal processing circuit 58, a servo circuit 62, and the like. Control the entire drive. Therefore, the drive control microcomputer 60 is connected to the sub-Dir. Various processes described above are performed when adding / deleting files and adding / deleting files. Further, the memory 63 can be connected to the drive control microcomputer 60.
[0105]
Further, an RF signal obtained by reproducing the disc-shaped recording medium 10 is supplied to the ENC / DEC circuit 56. The ENC / DEC circuit 56 demodulates the modulation process performed at the time of recording and decodes the error correction code (ie, error correction code). Decoding according to a predetermined format such as error correction). When the ENC / DEC circuit 56 stores the reproduction data in the buffer memory 55 and receives a read command from the digital device 71, the read data is transferred to the digital device via the I / F 61.
[0106]
The frame synchronization signal from the RF signal processing circuit 58, the tracking error signal TE and the focus error signal FE, and the address information from the address extraction circuit 59 are supplied to the servo circuit 62. The servo circuit 62 performs tracking servo and focus servo for the optical pickup 52, spindle servo for the spindle motor 51, and thread servo for the thread mechanism 57.
[0107]
In the above description, the format data for the disc-shaped recording medium 10 has been described as being generated by the ENC / DEC circuit 56, but this is not limited to this example. The format data can be generated by the drive control microcomputer 60. Further, the format data may be supplied from the digital device 71.
[0108]
In the above description, the case where the present invention is applied to a replaceable rewritable disc-shaped recording medium drive device such as an optical disk drive device or a magneto-optical disk drive device has been described. However, the present invention is not limited to this. It is not applicable. The present invention can also be applied to a drive device of a recording medium in which data recorded on the recording medium is managed by predetermined management information existing on the recording medium, for example, a fixed drive device such as a hard disk drive device. It is.
[0109]
【The invention's effect】
As described above, in the present invention, the information indicating the location where the actual data of the file is recorded is recorded twice, so that the safety of the information can be improved.
[0110]
In the present invention, when the regular information cannot be read due to a failure or the like, the regular information can be newly restored on the recording medium using the preliminary information. For this reason, even if regular information cannot be read, the actual data of the file can be read.
[0111]
Furthermore, in the present invention, when the regular information can no longer be read, the regular information is restored using the spare information each time. Can be read.
[Brief description of the drawings]
FIG. 1 is a schematic diagram showing a logical format of a disk-shaped recording medium in association with a disk shape.
FIG. 2 is a schematic diagram for explaining the structures of SMA and FSA before creating a backup for a file entry of a child file.
FIG. 3 is a diagram illustrating a file identification descriptor.
FIG. 4 is a schematic diagram for explaining creation of a backup for a file entry of a child file.
FIG. 5 is a diagram showing a format of implementation use in the present embodiment.
FIG. 6 is a schematic diagram for explaining processing for restoring a file entry of a child file in which a failure has occurred.
FIG. 7 is a block diagram showing a configuration of an example of a drive device.
[Explanation of symbols]
DESCRIPTION OF SYMBOLS 10 Disc-shaped recording medium 15 Reserved space area 16 Space management area 17 Free space area 21 File entry of root directory 22 Entity of root directory 23 File entry of space management file

Claims (5)

In a recording method for recording data on a recording medium based on a hierarchical file system,
Management information for managing the hierarchical structure of the file system is recorded in a specific area of the recording medium,
The unused area in the specific area is treated as a special file,
The information indicating the location where the actual data of the file was recorded is recorded twice on the recording medium as regular information and preliminary information,
A recording method characterized in that designation information indicating a place where the regular information and preliminary information are recorded is recorded in a portion vacated in the specific area by reducing the size of the special file. The recording method according to claim 1, wherein when the regular information cannot be read, the regular information is restored to the recording medium using the preliminary information. The entire specific area is copied as it is to another area and the entire copied specific area is handled as one backup file,
When a part of the management information cannot be read, the empty part generated in the specific area by reducing the size of the special file using data corresponding to the part in the backup file 2. The recording method according to claim 1, wherein a part of the management information that can no longer be read is restored. 2. The recording according to claim 1, wherein information regarding an initial location and size of the special file and information regarding a current location and size of the special file are recorded in the specific area. Method. In a recording apparatus for recording data on a recording medium based on a hierarchical file system,
Means for recording management information for managing the hierarchical structure of the file system in a specific area of the recording medium;
Means for allowing an unused area in the specific area to be treated as a special file;
Means for dually recording information indicating the location where the actual data of the file is recorded on the recording medium as regular information and preliminary information;
A recording apparatus, comprising: means for recording designation information indicating a place where the regular information and the preliminary information are recorded in a portion vacated in the specific area by reducing the size of the special file.

Images