HK1113433B - Method for allocating areas on information recording medium - Google Patents

Description

Method for partitioning on information recording medium

This application is a divisional application of a patent application having a filing date of 25/5/2005, an application number of 200510072172.0, entitled "information recording medium, recording/reproducing method, and recording/reproducing apparatus".

Technical Field

The present invention relates to a disc, and more particularly, to an information recording medium, and a recording/reproducing method and a recording/reproducing apparatus for re-initializing the medium.

Background

The number of defects in a rewritable information storage medium increases due to scratches, fingerprints, or dust present on the medium during use of the medium. Defective blocks occurring when the medium is used are managed by being registered as defect information, and the host or drive system attempts not to allocate data to the defective blocks but to record data in non-defective blocks. Thus, the number of such defective blocks will increase when the medium is continuously used. Thus, the user will wish to reinitialize the medium.

In this case, the defective block registered in the defect information after the user has removed the fingerprint or dust from the surface of the medium can be determined as a satisfactory non-defective block through verification after recording data. In this way, when re-initialization of the rewritable information storage medium is required, the drive system determines the defect possibility of blocks in the recordable area of the entire medium or defect blocks registered in the defect information through checking after recording.

The following operations may cause inconvenience to the user because it takes too much time to re-initialize the medium: when the rewritable information storage medium is reinitialized, defective blocks registered in the defect information or in the entire medium are recorded and then it is determined whether the blocks are defective through disc verification.

Disclosure of Invention

The present invention provides an information recording medium, and a recording/reproducing method and a recording/reproducing apparatus for rapidly reinitializing the medium.

Additional aspects and/or advantages of the invention will be set forth in part in the description which follows and, in part, will be obvious from the description, or may be learned by practice of the invention.

According to an aspect of the present invention, there is provided an information recording medium including a data area, wherein the data area includes: a user data area for recording user data; and a spare area for recording a replacement block that replaces a defective block occurring in the user data area; the defect list entry includes status information of the defect block and the replacement block; and the state information of the defective block held in the user data area after the spare area is newly allocated during the re-initialization is changed to indicate that the defective block held in the user data area has been re-initialized and has a possible defect.

The defective blocks occurring in the user data area before the spare area is newly allocated may include at least one of a defective block having a replacement block, a defective block having no replacement block, and a possible defective block, or a combination thereof.

According to another aspect of the present invention, there is provided an information recording medium including a data area, wherein the data area includes: a user data area for recording user data; and a spare area for recording a replacement block that replaces a defective block occurring in the user data area; the defect list entry includes status information of the defect block and the replacement block; and the state information of the defective block located in the newly allocated spare area is changed after the newly allocated spare area is allocated during the re-initialization to indicate that the defective block located in the newly allocated spare area has been re-initialized and is not usable as a replacement block.

According to another aspect of the present invention, there is provided an information recording medium including a data area, wherein the data area includes: a user data area for recording user data; and a spare area for recording a replacement block that replaces a defective block occurring in the user data area; the defect list entry includes status information of the defect block and the replacement block; and the state information of the replacement block that is not available to replace the defective block is changed to indicate the defective block that has been reinitialized and has a possible defect in response to the unusable replacement block being located in the spare area before the newly allocated spare area and in the user data area after the reinitialization of the medium.

According to another aspect of the present invention, there is provided an information recording medium including a data area, wherein the data area includes: a user data area for recording user data; and a spare area for recording a replacement block that replaces a defective block occurring in the user data area; the defect list entry includes status information of the defect block and the replacement block; and the state information of the defective block in the user data area is changed, and the state information of the replacement block in the spare area is changed in response to the spare area newly allocated to reinitialize the information recording medium.

The defect list entry may include: physical address information of a defective block or a replacement block; first state information indicating whether the replacement block is usable or unusable or indicating a defect state of the defect block; and second state information indicating whether the information recording medium has been reinitialized.

The defect list entries regarding the defective blocks remaining in the user data area after the spare area is newly allocated during the re-initialization may be changed to include: first state information indicating that a defective block remaining in a user data area has a possible defect; and second state information indicating that the defective block remaining in the user data area has been reinitialized.

The defect list entry regarding the defect block located in the newly allocated spare area after the newly allocated spare area is allocated during the re-initialization may be changed to include: first state information indicating that a defective block located in a newly allocated spare area is not usable as a replacement block; and second state information indicating that the defective block located in the newly allocated spare area has been reinitialized.

The defect list entry of the replacement block unavailable for replacing the defective block may be changed to include first state information indicating a defective block having a possible defect and second state information indicating that the defective block having a possible defect has been reinitialized, in response to the replacement block unavailable for replacing the defective block in the user data area being located in the spare area before the spare area is newly allocated and being located in the user data area after the reinitialization.

The checking of the consecutive blocks may be performed in response to a consecutive defect list entry existing before the allocation of the new spare area with respect to the consecutive blocks including at least two possible defective blocks arranged consecutively, the length of the consecutive blocks being unknown; the consecutive defect list entries may be registered to include first state information indicating a result of the checking and second state information indicating re-initialization in response to consecutive blocks remaining in the user data area after the re-initialization; and the consecutive defect list entry may be registered to include first state information indicating whether the consecutive block is available or unavailable for replacing the defective block and second state information indicating re-initialization in response to the consecutive block being located in a newly allocated spare area after the re-initialization.

A consecutive defect list entry may be maintained in response to the consecutive defect list entry existing before allocation of a new spare area with respect to a consecutive block including at least two possible defective blocks arranged consecutively and whose length is unknown and a first block included in the consecutive block included in the user data area after re-initialization included in the consecutive block before newly allocating the spare area; and the consecutive defect list entry may be registered to include first status information indicating whether the consecutive block is available or unavailable for replacing the defective block according to a checking result of the consecutive block and second status information indicating re-initialization in response to the consecutive block located in the newly allocated spare area after the re-initialization.

According to another aspect of the present invention, there is provided a recording/reproducing method including: newly allocating a spare area when re-initializing an information recording medium in which a user data area for recording user data and a spare area for recording a replacement block for replacing a defective block occurring in the user data area are arranged, wherein the defect list entry includes status information on the defective block and the replacement block; and changing state information of the defective block maintained in the user data area after the spare area is newly allocated to indicate that the defective block maintained in the user data area has been reinitialized and has a possible defect.

According to another aspect of the present invention, there is provided a recording/reproducing method including: newly allocating a spare area when re-initializing an information recording medium in which a user data area for recording user data and a spare area for recording a replacement block for replacing a defective block occurring in the user data area are arranged, wherein the defect list entry includes status information on the defective block and the replacement block; and changing the state information of the defective block located in the newly allocated spare area after the newly allocated spare area is allocated to indicate that the defective block located in the newly allocated spare area has been reinitialized and is not available as a replacement block.

According to another aspect of the present invention, there is provided a recording/reproducing method including: newly allocating a spare area when re-initializing an information recording medium in which a user data area for recording user data and a spare area for recording a replacement block for replacing a defective block occurring in the user data area are arranged, wherein the defect list entry includes status information on the defective block and the replacement block; and changing state information of a replacement block, which is not available to replace the defective block, to indicate the defective block, which has been reinitialized and has a possible defect, to include the unusable replacement block in the user data area after the reinitialization in response to the unusable replacement block being located in the spare area before the spare area is newly allocated.

According to another aspect of the present invention, there is provided a recording/reproducing method including: newly allocating a spare area when re-initializing an information recording medium in which a user data area for recording user data and a spare area for recording a replacement block for replacing a defective block occurring in the user data area are arranged, wherein the defect list entry includes status information on the defective block and the replacement block; and changing state information of the defective block in the user data area and state information of the replacement block in the spare area.

According to another aspect of the present invention, there is provided a recording/reproducing apparatus including: a read/write unit for reading and/or writing data from and/or on an information recording medium having a user data area for recording user data, a spare area for recording a replacement block replacing a defective block occurring in the user data area, and a defect list entry including status information of the defective block and the replacement block; and a control unit for controlling the read/write unit to newly allocate a spare area to reinitialize the information recording medium and to change state information of the defective block maintained in the user data area after the reinitialization to indicate that the defective block maintained in the user data area has been reinitialized and has a possible defect.

According to another aspect of the present invention, there is provided a recording/reproducing apparatus including: a read/write unit for reading and/or writing data from and/or on an information recording medium having a user data area for recording user data, a spare area for recording a replacement block replacing a defective block occurring in the user data area, and a defect list entry including status information of the defective block and the replacement block; and a control unit for controlling the read/write unit to newly allocate a spare area to reinitialize the information recording medium, and to change state information of a defective block located in the newly allocated spare area after the reinitialization to indicate that the defective block located in the newly allocated spare area has been reinitialized and is unavailable as a replacement block.

According to another aspect of the present invention, there is provided a recording/reproducing apparatus including: a read/write unit for reading and/or writing data from and/or on an information recording medium having a user data area for recording user data, a spare area for recording a replacement block replacing a defective block occurring in the user data area, and a defect list entry including status information of the defective block and the replacement block; and a control unit for controlling the read/write unit to newly allocate a spare area to reinitialize the information recording medium and to change state information of a replacement block that is not available to replace the defective block to indicate a defective block that has been reinitialized and has a possible defect, in response to the unusable replacement block being located in the spare area before the reinitialization and being located in the user data area after the reinitialization.

According to another aspect of the present invention, there is provided a recording/reproducing apparatus including: a read/write unit for reading and/or writing data from and/or on an information recording medium having a user data area for recording user data, a spare area for recording a replacement block replacing a defective block occurring in the user data area, and a defect list entry including status information of the defective block and the replacement block; and a control unit for controlling the read/write unit to newly allocate a spare area to reinitialize the information recording medium, and to change the state information of the defective block and the replacement block and then to record the state information.

Drawings

These and/or other aspects and advantages of the present invention will become apparent and more readily appreciated from the following description of the embodiments, taken in conjunction with the accompanying drawings of which:

fig. 1 is a block diagram of a recording/reproducing apparatus according to an embodiment of the present invention;

fig. 2 is a structural diagram of a single record layer disc according to an embodiment of the present invention;

fig. 3 is a structural diagram of a dual record layer disc according to an embodiment of the present invention;

fig. 4 is a diagram of a structure of data of a defect list (DFL) according to an embodiment of the present invention;

fig. 5 is a structural diagram of data of a DFL entry as represented in fig. 4;

fig. 6 illustrates state information of the DFL entry illustrated in fig. 5;

FIGS. 7A and 7B illustrate a method of processing DFL entries for blocks within a newly allocated spare area in a disk after the disk is reinitialized in accordance with an embodiment of the present invention;

fig. 8A illustrates status information of a DFL entry before allocating a new spare area to the data area illustrated in fig. 7A;

fig. 8B illustrates status information of a DFL entry after allocating a new spare area to the data area illustrated in fig. 7B;

FIGS. 9A and 9B illustrate a method of processing DFL entries for blocks within a newly allocated spare area in a disk after the disk is reinitialized in accordance with an embodiment of the present invention;

fig. 10A illustrates status information of a DFL entry before allocating a new spare area to the data area illustrated in fig. 9A;

fig. 10B illustrates status information of a DFL entry after allocating a new spare area to the data area illustrated in fig. 9B;

fig. 11A through 11C illustrate three DFL entries when status information 1 is set to "3" indicating that a block may have a defect according to an embodiment of the present invention;

fig. 12A and 12B illustrate some consecutive defect blocks having a known length of a defect, which exist in a newly allocated spare area, while the rest of the consecutive defect blocks are located in a user data area, according to an embodiment of the present invention;

fig. 13A and 13B illustrate changes of DFL entries of the case illustrated in fig. 12A and 12B;

fig. 14A to 14C illustrate a case in which start addresses of consecutive defective blocks having a length of an unknown defect are located in a spare area or a user data area by newly allocating the spare area according to an embodiment of the present invention;

fig. 15A to 15C show changes of DFL entries in the case shown in fig. 14A to 14C; and

fig. 16A and 16B are flowcharts illustrating a method of reinitializing a disc according to an embodiment of the present invention.

Detailed Description

Reference will now be made in detail to the present embodiments of the present invention, examples of which are illustrated in the accompanying drawings, wherein like reference numerals refer to the like elements throughout. The embodiments are described below in order to explain the present invention by referring to the figures.

Fig. 1 is a block diagram of a recording/reproducing apparatus according to an embodiment of the present invention.

Referring to fig. 1, the recording/reproducing apparatus includes: a read/write unit 2 and a control unit 1.

The read/write unit 2 includes a pickup and writes data on an information recording medium, which is a disc 4 in this embodiment, or reads recorded data from the disc 4.

The control unit 1 writes data on the disc 4 or reads data from the disc 4 according to a predetermined file system. Specifically, the control unit 1 newly allocates a spare area to reinitialize the disc 4, and manages the state information of the defective block in the user data area and the replacement block in the spare area according to the allocation result.

The control unit 1 includes: a system controller 10, a host interface (I/F)20, a Digital Signal Processor (DSP)30, a radio frequency amplifier (RF AMP)40, and a servo 50.

When recording data on the disc 4, the host I/F20 receives a predetermined write command output from the host 3 and transmits the write command to the system controller 10. The system controller 10 controls the DSP30 and the servo 50 to execute a write command received from the host I/F20. The DSP30 adds additional data such as parity encoding to data to be recorded on the disc 4 received from the host I/F20 to correct errors in the data, performs Error Correction Code (ECC) encoding on any ECC block occurring as an error correction block, and then modulates the ECC block in a predetermined method. The RF AMP 40 converts data output from the DSP30 into an RF signal. The read/write unit 2 including the pickup records the RF signal transmitted from the RF AMP 40 on the disc 4. The servo 50 receives a command required for servo control from the system controller 10 and servo-controls the pickup of the read/write unit 2.

Specifically, the system controller 10 manages the defect status of the blocks when a spare area is newly allocated to reinitialize the disc 4.

When it is determined that the physical address of a defective block in the user data area established before disc reinitialization is still included in the user data area after a new spare area is allocated by disc reinitialization, the system controller 10 changes a defect list (DFL) entry of the defective block to a DFL entry having state information indicating the possibility that the defective block is reinitialized and has a defect, and controls the read/write unit 2 to write the DFL entry on the disc 4.

In addition, when it is determined that the physical address of the defective block in the user data area before the disc re-initialization is included in the physical addresses of the replacement block of the new spare area after the new spare area is allocated by the disc re-initialization, the system controller 10 changes the DFL entry of the replacement block to a DFL entry having state information indicating that the replacement block is re-initialized and cannot be used for replacement.

In addition, when it is determined that a physical address of a replacement block, which cannot be used for replacement, in the spare area before the disc re-initialization is included in physical addresses of the user data area after a new spare area is allocated by the disc re-initialization, the system controller 10 changes the DFL entry of the defective block to a DFL entry having state information indicating that the defective block is re-initialized and has a possible defect that has not been checked. The DFL entries and state information will be described in more detail later.

When reproducing data from the disc 4, the host I/F20 receives a read command from the host 3. The system controller 10 performs initialization required for reproduction. The read/write unit 2 emits a laser beam onto the disc 4 and outputs an information signal obtained by receiving the laser beam reflected from the disc 4. The RF AMP 40 converts the information signal output from the read/write unit 2 into an RF signal, and supplies modulated data obtained from the RF signal to the DSP30 and a servo signal for controlling the servo 50 obtained from the RF signal to the servo 50.

The DSP30 demodulates the modulated data and outputs data obtained by applying ECC error correction to the demodulated data. Meanwhile, the servo 50 receives the servo signal output from the RF AMP 40 and the command for servo control output from the system controller 10, and performs servo control on the pickup. The host I/F20 transmits data received from the DSP30 to the host 3.

The structure of the information recording medium according to an embodiment of the present invention will now be described in detail.

Fig. 2 is a structural diagram of a single record layer disc according to an embodiment of the present invention.

Referring to fig. 2, the disc includes: a lead-in area located at an inner circumference of the disc, a lead-out area located at an outer circumference of the disc, and a data area located therebetween in a radial direction of the disc.

The introduction region includes: a Defect Management Area (DMA) #2, a write condition test area, and a DMA # 1. The data area includes: spare area #1, user data area, and spare area # 2. The lead-out area includes: DMA #3 and DMA # 4.

The DMA is an area for recording defect management information of a rewritable information storage medium. The DMA is disposed in an inner area and/or an outer area of the disc.

When a defect occurs in a predetermined area of a user data area of a disc, it is determined by a user or a disc manufacturer at an initialization stage of the data area whether a spare area in which a replacement block for replacing a defect block in which a defect has occurred is written is allocated and the size of the spare area and/or the replacement block is determined. When the disc needs to be reinitialized when using the disc, a spare area may be newly allocated.

The defect management information recorded in the DMA includes: a DFL for defect information; and a Disc Definition Structure (DDS) including information regarding the structure of the data area.

The DFL includes: a DFL header and a DFL entry. The format of the DFL will be described in more detail later with reference to fig. 4.

The write condition test area is used to test various recording powers to obtain an optimum power and a variation for recording data.

Fig. 3 is a structural diagram of a dual record layer disc according to an embodiment of the present invention.

Referring to fig. 3, the recording layer L0 includes a lead-in area #0, a data area, and a lead-out area #0, and the other recording layer L1 includes a lead-in area #1, a data area, and a lead-out area # 1.

The lead-in area #0 of the L0 layer includes: DMA #2, write condition test area, and DMA # 1. The data area of the L0 layer includes: spare area #1, user data area, and spare area # 2. The lead-out region #0 of the L0 layer includes: DMA #3 and DMA # 4.

The lead-in area #1 of the L1 layer includes: DMA #2, write condition test area, and DMA # 1. The data area of the L1 layer includes: spare area #4, user data area, and spare area # 3. The lead-out region #1 of the L1 layer includes: DMA #3 and DMA # 4.

Fig. 4 is a structural diagram of a data format of a DFL 400 according to an embodiment of the present invention.

Referring to fig. 4, the DFL 400 includes: a DFL header 410 and a DFL entry list 420.

The number information for defect management of the block is written in the DFL header 410. The DFL header 410 includes: DFL identifier 411, number of defective blocks with replacement blocks 412, number of defective blocks without replacement blocks 413, number of usable spare blocks 414, number of non-usable spare blocks 415, and number of blocks with possible defects 416.

The number of defective blocks having replacement blocks 412 represents the number of DFL entries having defect status information indicating that the defective blocks have been replaced with replacement blocks within the spare area.

The number 413 of defective blocks having no replacement block represents the number of DFL entries having defect status information indicating a defective block having no replacement block in the spare area.

The number of usable spare blocks 414 indicates the number of DFL entries having defect status information indicating blocks available for replacement among the blocks not replaced in the spare area.

The number of unusable spare blocks 415 indicates the number of DFL entries having defect status information indicating blocks that are not usable for replacement among the blocks that are not replaced in the spare area.

The number of possible defective blocks 416 represents the number of DFL entries having defect status information indicating possible defective blocks that have not been verified as defective among blocks in the user data area.

The DFL entry list 420 is a collection of DFL entries having defect status information on various blocks. The DFL entry list 420 includes a DFL entry #1421, a DFL entry #2422, a.

Fig. 5 is a structural diagram of a data format of the DFL entry # i500 as represented in fig. 4.

Referring to fig. 5, the DFL entry # i500 includes: state information 1510, physical address of defective block 520, state information 2530, and physical address of replacement block 540.

The state information 1510 is information on a defect state of a defective block in the user data area and information on a state of whether a replacement block in the spare area is usable. The status information 1510 will be described in more detail later with reference to fig. 6.

The state information 2530 is information on a state whether a replacement block in the spare area is usable. In this way, by indicating that the disc is reinitialized only in the state information 2530 of the DFL entry # i500 without undergoing a checking operation after reinitializing the disc, reinitialization of the disc can be performed quickly. In addition, when recording data after re-initialization of the disc, if the state information 2530 of the DFL entry # i500 of the block on which data is to be recorded is set to state information indicating that the disc has been re-initialized, the drive system knows that the disc has been re-initialized, and thus, can pack a predetermined amount of data into the remaining portion of the block and record the data without undergoing additional read-modify-write (read-modify-write) processing even if the host 3 commands recording of data in a predetermined area of the block. In addition, when a reproduction command output from the host 3 is received, if the state information 2530 is set to indicate that the disc has been reinitialized, the drive system knows that the data recorded in the block is invalid data, and thus, null data or a check message is immediately transmitted to the host 3.

The physical address 520 of the defective block is a physical address where the defective block is located in the user data area, and the physical address 540 of the replacement block is a physical address where the replacement block is located in the spare area.

Fig. 6 shows the status information 1510 of the DFL entry # i500 shown in fig. 5.

Referring to fig. 6, the state information 1510 includes five states: "1", "2", "3", "4", and "5".

The state information "1" indicates the state of the defective block having the replacement block. In this case, the physical address of the defective block indicates a physical address of the defective block in the user data area, and the physical address of the replacement block is a physical address at which the replacement block replacing the defective block is written in the spare area.

The state information "2" indicates the state of a defective block having no replacement block. In this case, the physical address of the defective block indicates the physical address of the replacement block in the user data area.

The status information "3" indicates the status of a possible defective block. A possible defective block is a block that has not been checked by error correction after recording data when an excessive RF signal or servo signal is detected during disc verification or scanning, has a possibility of being defective, and thus needs to be checked by error correction after recording data in the future. In this case, the physical address of the defective block indicates the physical address of a possible defective block that has not been checked yet.

The status information "4" indicates the status of a usable replacement block in the spare area. In this case, the physical address of the replacement block indicates a physical address of a block that can be used among the unused replacement blocks in the spare area.

The status information "5" indicates the status of an unavailable replacement block in the spare area. In this case, the physical address of the replacement block indicates a physical address of an unusable block among the unused replacement blocks in the spare area.

The status information "1", "2", and "3" indicate the status of blocks in the user data area, and the status information "4" and "5" indicate the status of blocks in the spare area.

The state information 2530 is not represented in fig. 6, but, for example, if the state information 2530 is set to "1", the disc has been reinitialized, if the state information 2530 is set to "0", the disc has not been reinitialized, or is used after reinitialization. If the status information 2530 is set to "0", valid data is recorded in the block. If the status information 2530 is set to "1", valid data is not recorded in the block since the block has been reinitialized.

Fig. 7A and 7B illustrate a method of processing a DFL entry of a block in a newly allocated spare area in a disc after the disc is reinitialized according to an embodiment of the present invention.

Fig. 7A shows data blocks in a single record layer disc in which a spare area #1 is allocated and used before disc re-initialization, and fig. 7B shows data blocks having a new spare area #1 allocated therein after disc re-initialization.

Referring to fig. 7A, the data area has only a spare area #1 allocated therein and includes the spare area #1 and a user data area. Blocks (r), (g), and (c) are recorded at the end of the user data area. The block (r) is a defective block and has a replacement block for replacing the defective block. Block (c) is a defective block having no replacement block for replacing the defective block. Block three is a possible defective block.

Fig. 7B shows the data area when a defective block still exists in the user data area after disc re-initialization in the case where a new spare area #1 is allocated in the data area by disc re-initialization when the disc is used in the current state.

Referring to fig. 7B, DFL entries of a block (r) having a replacement block, a block (r) having no replacement block, and a block (r) having a possible defect are converted into DFL entries having state information having a possible defect and state information in which the blocks (r), and (r) are re-initialized.

Fig. 8A illustrates status information of a DFL entry before allocating a new spare area #1 to a data area according to an embodiment of the present invention illustrated in fig. 7A. Fig. 8B is a diagram of state information of a DFL entry after allocating a new spare area #1 to a data area according to an embodiment of the present invention shown in fig. 7B.

Referring to fig. 8A, the DFL entry of block (r) is the first entry listed in fig. 8A. Since the block (r) is a defective block having a replacement block, the state information 1 is set to "1", the physical address of the defective block is registered as "0010000 h", and the state information 2 is set to "0" since the defective block has not been reinitialized. Since the block (c) is a defective block having no replacement block, the state information 1 is set to "2", the physical address of the defective block is registered as "0010100 h", and the state information 2 is set to "0" since the defective block has not been reinitialized. Since the block (c) is a possible defective block, the state information 1 is set to "3", the physical address of the block is registered as "0010110 h", and the state information 2 is set to "0" since the defective block has not been reinitialized.

The DFL entry list shown in fig. 8A is changed to the DFL entry list as shown in fig. 8B by re-initialization of the newly allocated spare area # 1.

Referring to fig. 8B, the DFL entry of block (r) is the first entry listed in fig. 8B, the DFL entry of block (r) is the second entry in fig. 8B, and the DFL entry of block (r) is the third entry in fig. 8B. The state information 1 of the DFL entries of blocks (r), and (c) are all set to "3", which indicates defective blocks in which they are possible due to the disk re-initialization, and the state information 2 of the DFL entries of blocks (r), and (r) are all set to "1", which indicates that they have been re-initialized.

In this way, a defective block in the user data area after disc re-initialization is a possible defective block. Therefore, when it is intended to record data on these blocks, it is preferable, but not necessary, that the blocks should be checked for defects through a disc verification process after recording data on the disc.

If the block is used again after the state information 2 of the DFL entry is set to "1" indicating that the disc has been reinitialized by reinitializing the disc, the state information 2 needs to be changed to "0". The status information 2 is set to "1" to indicate that the data recorded in the block has become invalid by reinitializing the disc.

Fig. 9A and 9B illustrate a method of processing DFL entries of blocks within a newly allocated spare area in a disc after the disc is reinitialized according to an embodiment of the present invention.

Fig. 9A shows data blocks in a single record layer disc in which a spare area #1 is allocated and used before disc re-initialization, and fig. 9B shows data blocks having a new spare area #2 allocated therein after disc re-initialization.

Referring to fig. 9A, the data area has only a spare area #1 allocated therein, and the data area includes the spare area #1 and a user data area. Blocks (c), and (c) are recorded in the end of the user data area, and block (c) is recorded in the spare area # 1. The block (r) is a defective block and has a replacement block for replacing the defective block. The block (c) is a defective block having no replacement block for replacing the defective block. Block sixty is a possible defective block. Block (c) is a replacement block located in the spare area #1 that cannot be used to replace another block.

Fig. 9B shows a state of a data area in which a spare area #1 is reduced when newly allocated by re-initialization of the disc at the time of using the disc, and a block located in the spare area #1 before re-initialization is located in a user data area after re-initialization. In addition, a spare area #2 is newly allocated in the data area, and blocks (r), (c), and (c) located in the user data area before re-initialization are located in the spare area # 2.

Referring to fig. 9B, if blocks (r), (c), and (c) located in the user data area before re-initialization are included in the spare area #2 after re-initialization, the DFL entries of the blocks (r), (c), and (c) are changed to DFL entries having state information indicating that all of the blocks (r), (c), and (c) have been re-initialized and state information indicating that they are unavailable for replacement. In addition, if block (c) located in the spare area #1 before the re-initialization is located in the user data area after the re-initialization, the DFL entry of block (c) is changed to a DFL entry having state information indicating that block (c) has been re-initialized and state information indicating that it has a possible defect.

Fig. 10A shows status information of DFL entries before allocating new spare areas #1 and #2 to a data area shown in fig. 9A, and fig. 10B shows status information of DFL entries after allocating new spare areas #1 and #2 to a data area shown in fig. 9B.

Referring to fig. 10A, the DFL entry of block (r) is the first entry listed in fig. 9A. Since the block (r) is a defective block having a replacement block, the status information 1 is set to "1", the physical address of the defective block is registered as "0010000 h", and the status information 2 is set to "0" since the defective block has not been reinitialized. Since the block (c) is a defective block having no replacement block, the state information 1 is set to "2", the physical address of the defective block is registered as "0010100 h", and the state information 2 is set to "0" since the defective block has not been reinitialized. Since the block is a possible defective block, the state information 1 is set to "3", the physical address of the block is registered as "0010110 h", and the state information 2 is set to "0" since the block has not been reinitialized.

The DFL entry list shown in fig. 10A is changed to the DFL entry list as shown in fig. 10B by re-initialization of the newly allocated spare areas #1 and # 2.

Referring to fig. 10B, the DFL entry of block (r) is the second entry listed in fig. 10B, the DFL entry of block (c) is the third entry in fig. 10B, the DFL entry of block (c) is the fourth entry in fig. 10B, and the DFL entry of block (c) is the first entry in fig. 10B. The state information 1 of the DFL entries of blocks (r), (c), and (c) are all set to '5', indicating that they become blocks that cannot be used for replacement through the disk re-initialization. The state information 2 indicating the re-initialized state of the blocks (r), (c), and (c) are all set to '1', indicating that they have been re-initialized and that the physical address of the defective block is moved to the location of the physical address of the replacement block. The state information 1 of the DFL entry of block (c) is set to '3', which indicates its possibility of having a defect, the state information 2 is set to '1', and the physical address of the replacement block is moved to the location of the physical address of the defective block.

So far the description has referred to a single record layer disc, but the same method applies to a dual record layer disc.

A method of processing a continuous defective block in which defects sequentially occur will now be described with reference to fig. 11A to 15C.

Fig. 11A to 11C represent three kinds of DFL entries when the state information 1 is set to "3" indicating that a block may have a defect.

Fig. 11A is a diagram of a DFL entry for a single possible defective block.

Referring to fig. 11A, status information 1 of a DFL entry is set to '3' indicating that a block may have a defect, a physical address of the defective block indicates a physical address of the possibly defective block, status information 2 is set to '0' indicating that re-initialization has not been performed, and a physical address of a replacement block is registered as '1' indicating that the block is a single block.

Fig. 11B is a diagram of DFL entries of consecutive defect blocks having known lengths of possible defects.

Referring to fig. 11B, the state information 1 of the DFL entry is set to '3' indicating that the consecutive defective block may have a defect, the physical address of the defective block indicates the starting physical address of the consecutive defective block, the state information 2 is set to '0' indicating that the re-initialization has not been performed, and the physical address of the replacement block is registered as '5' indicating the length of the consecutive defective block.

Fig. 11C is a diagram of DFL entries of consecutive defect blocks having unknown lengths of possible defects.

Referring to fig. 11C, the state information 1 of the DFL entry is set to '3' indicating that the consecutive defective block may have a defect, the physical address of the defective block indicates the starting physical address of the consecutive defective block, the state information 2 is set to '0' indicating that the re-initialization has not been performed, and the physical address of the replacement block is registered as a predetermined value 'FFh' because the length of the consecutive defective block is unknown.

Fig. 12A and 12B illustrate a portion of a continuous defect block having a known length of a defect, which exists in a newly allocated spare area, and the remaining portion of the continuous defect block exists in a user data area, according to an embodiment of the present invention.

Referring to fig. 12A, defective blocks #1 to #5 having possible defects are consecutively arranged in a user data area. The defective blocks #1 to #5 having possible defects form a continuous defective block. The start address of the consecutive defective block is shown as "0001000 h".

In the current state, when a spare area is newly allocated due to re-initialization, a portion of the consecutive defective blocks is included in the newly allocated spare area and the other portion is included in the user data area, as shown in fig. 12B.

Referring to fig. 12B, two blocks (blocks #1 and #2) are included in the spare area and three blocks (blocks #3 to #5) are included in the user data area by newly allocating the spare area. As will be described later, the blocks #3 to #5 (i.e., consecutive defective blocks) included in the user data area may still have defects, and the blocks #1 and #2 included in the spare area become replacement blocks that cannot be used.

Fig. 13A and 13B illustrate changes of DFL entries for the case illustrated in fig. 12A and 12B.

Fig. 13A represents the DFL entries of the consecutive defective blocks as shown in fig. 12A, i.e., the DFL entries of the consecutive defective blocks before re-initialization.

Referring to fig. 13A, status information 1 of the DFL entry is set to '3' indicating that a consecutive defective block may have a defect, a physical address of the defective block is registered therein as '0001000 h' which is a starting physical address of the consecutive defective block, status information 2 is set to '0' indicating that re-initialization has not been performed, and a physical address of a replacement block is registered as '5' indicating the length of the consecutive defective block.

Fig. 13B represents the DFL entries of the consecutive defective blocks as shown in fig. 12B, i.e., the DFL entries of the consecutive defective blocks after re-initialization.

Referring to fig. 13B, defective blocks #3 to #5 having a possible defect included in the user data area remain the first DFL entry even after re-initialization. That is, the first DFL entry has: state information 1 set to '3' indicating that the defective blocks #3 to #5 may have a defect; the physical address of the defective block, registered as "0001010 h" as the starting physical address of the continuous defective block; state information 2 set to "1" indicating that re-initialization has been performed; and the physical address of the replacement block, registered as "3" indicating the length of the continuous defective block.

Blocks #1 and #2 included in the spare area after the re-initialization are the second and third DFL entries shown in fig. 13B. The second DFL entry has: status information 1, set to "5" indicating an unusable block; state information 2 set to "1" indicating that re-initialization has been performed; and the physical address of the replacement block, registered as "0001000 h". The third DFL entry has: status information 1, set to "5" indicating an unusable block; state information 2 set to "1" indicating that re-initialization has been performed; and the physical address of the replacement block, registered as "0001001 h". The consecutive defective blocks in the user data area may be displayed as a single DFL entry, but even if the replacement blocks in the spare area are sequentially arranged, there is a DFL entry for each replacement block.

Fig. 14A to 14C illustrate a case in which start addresses of consecutive defective blocks having a length of an unknown defect are located in a spare area or a user data area by newly allocating the spare area according to an embodiment of the present invention.

There are two methods of handling consecutive defect blocks with unknown defect length by re-initialization.

One method is to check a predetermined block from the start block of a continuous defective block by "check after recording", and generate a DFL entry for each checked block according to where the block exists after a spare area is newly allocated (i.e., in a user data area or a spare area). That is, first, a "check after recording" is performed, and if it is determined that a block in the user data area has a defect even after the spare area is newly allocated, a DFL entry according to the determination is registered. However, if the block is determined to have no defects, the DFL entry for the block need not be registered. Further, if a block in the newly allocated spare area is determined to have a defect, a DFL entry having status information indicating that the block is an unusable replacement block is registered, and if the block is determined to have no defect, a DFL entry having status information indicating that the continuous block is a usable replacement block is registered.

Another method is to generate the DFL entry according to where the start addresses of the consecutive defective blocks are located after the spare area is newly allocated. That is, when the start addresses of consecutive defective blocks are included in the spare area after a new spare area is allocated, a predetermined block starting from the start block of the start addresses is recorded and then checked, and the DFL entry is registered according to the checking result. When the start addresses of consecutive defective blocks are included in the user data area after allocating a new spare area, the original DFL entry is maintained. Here, the status information indicating that the re-initialization has been performed is not indicated in the status information 2 because the purpose of the status information indicating that the re-initialization has been performed is to eliminate unnecessary read-modify-write processing when data is recorded on the above-described block by the host in the future. However, if the length of the continuous block is unknown, even if the state information indicating that the re-initialization has been performed is indicated, the range from which physical address of the continuous block having a possible defect to which physical address has been re-initialized is still unclear. Therefore, the state information indicating that the re-initialization has been performed is not included in the state information 2. This will be described in more detail with reference to fig. 14A to 15C.

Referring to fig. 14A, consecutive defect blocks having unknown lengths are arranged in a user data area. Even if the length of the consecutive defective blocks is unknown, the start address is indicated as "0000100 h".

Referring to fig. 14B, a new spare area is allocated with respect to the case shown in fig. 14A. After allocating a new spare area, the size of the spare area is reduced, but the starting addresses of consecutive defect blocks of unknown length located in the user data area before the new allocation of the spare area remain in the user data area. In the present case, since the start addresses of consecutive defective blocks having unknown lengths remain in the user data area, it is assumed that the consecutive defective blocks are also in the user data area, and the DFL entries are processed accordingly.

Fig. 14C also shows a new spare area allocated with respect to the case shown in fig. 14A. After a new spare area is allocated, the size of the spare area is increased, and start addresses of consecutive defective blocks having an unknown length located in the user data area before the new spare area is allocated are included in the spare area. In the current situation, since the start addresses of consecutive defective blocks having unknown lengths are in the spare area, it is assumed that the consecutive defective blocks are in the spare area, and the DFL entries are processed according to the result of performing "check after recording" on a predetermined block starting from the start addresses of the consecutive defective blocks.

Fig. 15A to 15C show changes of DFL entries in the case shown in fig. 14A and 14B.

Fig. 15A represents DFL entries of consecutive defective blocks before re-initialization shown in fig. 14A.

Referring to fig. 15A, status information 1 of the DFL entry is set to '3' indicating a possible defective block, a physical address of the defective block indicates a physical address of the possible defective block, status information 2 is set to '0' indicating that re-initialization has not been performed, and a physical address of a replacement block registers a predetermined value 'FFh' therein to indicate that the length of the consecutive defective block is unknown.

Fig. 15B represents DFL entries of a consecutive defective block having an unknown length when start addresses of the consecutive defective block are included in the user data area after re-initialization as shown in fig. 14B.

Referring to fig. 15B, the DFL entry remains the same as that of fig. 15A, and the state information 2 also remains set to "0" as described above.

Fig. 15C is a diagram of DFL entries of a continuous defect block having an unknown length when start addresses of the continuous defect block are included in a spare area after re-initialization as shown in fig. 14C.

Referring to fig. 15C, when start addresses of consecutive defective blocks having an unknown length exist in the spare area, a DFL entry is registered according to a result of checking a predetermined block after recording the predetermined block from the start addresses of the consecutive defective blocks. For example, when there are two defective blocks among the consecutive defective blocks after checking the consecutive defective blocks and it is determined by the checking that the first block is a usable block and the second block is an unusable block, two DFL entries as shown in fig. 15C are registered.

Fig. 16A and 16B are flowcharts illustrating a method of reinitializing a disc according to an embodiment of the present invention.

Referring to fig. 16A, the disc 4 is loaded in the drive system, and then the system controller 10 of the drive system receives a disc reinitialization command (1601).

When a disc re-initialization command is received, the system controller 10 allocates a new spare area in the user data area (1602).

Then, the system controller 10 changes the DFL entry according to the allocation of the spare area by determining whether the portion to be changed is a single defect block or a continuous defect block (1603). If it is determined that the portion to be changed is a single defectAt block, processing proceeds to operation 1604. However, if it is determined to be a continuous defective block, the process moves to that shown in fig. 16B

In operation 1604, the system controller 10 determines whether a defective block included in the user data area is still included in the user data area after a new spare area is allocated.

If the determination result shows that the defective block remains in the user data area, the DFL entry of the defective block is changed to a DFL entry indicating that it is a possible defective block that has not been verified and has status information indicating that the defective block has been reinitialized (1605).

If the determination result shows that the defective block does not remain in the data user area, it is then determined whether a defective block included in the user data area is included in the spare area after re-initialization (1606).

If the determination result shows that the defective block included in the user data area is included in the spare area after the re-initialization, the DFL entry of the defective block is changed to a DFL entry indicating that the block is not available for replacement and having status information indicating that the re-initialization has been performed (1607).

Then, when a replacement block, which is not available for replacement in the spare area, is included in the user data area after allocating a new spare area (1608), the system controller 10 changes the DFL entry of the replacement block to a DFL entry indicating that it is a possible defective block that has not been checked yet and has status information indicating that re-initialization has been performed (1609).

In the event that operation 1603 determines that the part to be changed is a continuous defective block, the process proceeds to operation 1610 as shown in fig. 16B (as determined by operation 1610)Shown). In the case of consecutive defective blocks, it is determined whether the length of the consecutive possible defective blocks is known (1610).

In case of a consecutive possible defective block having a known length, status information 2 of a consecutive block in the user data area is set to '1' indicating that the consecutive block has been reinitialized after a new spare area is allocated, and a DFL entry of the consecutive block is changed to a consecutive DFL entry (1611). The DFL entries of the consecutive blocks included in the newly allocated spare area are changed to DFL entries indicating unusable replacement blocks (1612). When a part of consecutive possible defective blocks is included in the user data area and other parts of the consecutive blocks are included in the newly allocated spare area by allocating a new spare area, some of the blocks included in the user data area are processed in operation 1611 and other blocks included in the spare area are processed in operation 1612.

When the length of the consecutive possible defective blocks is unknown, one of the methods 1 and 2 may be used, for example, according to the intention of the drive manufacturer (1613).

In case of the method 1, a predetermined block starting from a start block included in a continuous block is checked by "check after recording", and then, a DFL entry of the continuous block is changed according to the checking result (1614). That is, according to the checking result, the consecutive blocks included in the user data area after allocating a new spare area are registered as DFL entries including status information 1 indicating that it is defective or has a possible defect and status information 2 indicating that they have been reinitialized. Further, according to the checking result, the consecutive blocks included in the newly allocated spare area are identified by the DFL entry including state information 1 indicating usable or unusable replacement blocks and state information 2 indicating that they have been reinitialized.

In case of the method 2, if a start block of a consecutive block is included in the user data area after allocating the spare area, the DFL entry regarding the start block is changed to a consecutive block DFL entry, assuming that other blocks are also included in the user data area. If the start block of the continuous block is included in the newly allocated spare area, it is assumed that other blocks are included in the spare area and the DFL entry regarding the continuous block is changed to a DFL entry indicating a usable or unusable replacement block according to the result of the check performed after the recording (1615).

According to the present invention as described above, by reinitializing the disc by managing defect information without recording data and then checking the data, a reinitialization process is rapidly performed. That is, by indicating in the state information 2 of the defect list entry that the re-initialization has been performed when the disc is re-initialized, the re-initialization can be rapidly performed. Further, if the state information 2 of the defect list entry of the block in which data is to be recorded is set to "1" when data is recorded after the re-initialization, the drive system knows that the re-initialization has been performed, and even if the host issues a command to record data on a portion of the block, predetermined data is immediately padded to the remaining portion of the block without being subjected to a separate read-modify-write process, and data is recorded. In addition, since data recorded on the block is invalid, the drive system immediately transmits null data to the host, or a check message may be transmitted when a reproduction command is received. Accordingly, the present invention can reduce the time taken to reinitialize a disc and prevent unnecessary read-modify-write processes in a rewritable medium.

The recording/reproducing method can also be embodied as computer readable codes on a computer readable recording medium. The computer readable recording medium is any data storage device that can store data which can be thereafter read by a computer system. Examples of the computer-readable recording medium include: read-only memory (ROM), random-access memory (RAM), CD-ROMs, magnetic tapes, floppy disks, information data storage devices, and carrier waves (such as data transmission through the internet). The computer readable recording medium can also be distributed over network coupled computer systems so that the computer readable code is stored and executed in a distributed fashion. In addition, functional programs, codes, and code segments for implementing the recording/reproducing method can be easily deduced by programmers in the art to which the present invention pertains.

Although a few embodiments of the present invention have been shown and described, it would be appreciated by those skilled in the art that changes may be made in these embodiments without departing from the principles and spirit of the invention, the scope of which is defined in the claims and their equivalents.

Claims (2)

1. A method for recording data on an information recording medium, the information recording medium including a data area and a defect management area, the data area including a user data area for storing user data and a spare area for storing a replacement block that replaces a defect block occurring in the user data area, the defect management area for storing a defect list including defect entries, the method comprising:

converting a defect entry having first state information including location information on the replacement block and first state information indicating that the replacement block cannot be used to replace another defect block into a new defect entry having second state information indicating that the replacement block corresponding to the new defect entry may be a defect block during the re-initialization if the replacement block corresponding to the defect entry is included in the user data area after changing the range of the spare area by the re-initialization;

a new defect entry having the second state information is recorded on the information recording medium.

2. A method for reproducing data from an information recording medium, the information recording medium including a data area including a user data area for storing user data and a spare area for storing a replacement block that replaces a defective block occurring in the user data area, and a defect management area for storing a defect list including defect entries, the method comprising:

if a replacement block corresponding to a defect entry is included in the user data area after changing the range of the spare area by re-initialization, a new defect entry having second state information is reproduced from the information recording medium, wherein the new defect entry having the second state information is an entry converted from a defect entry having first state information during re-initialization, the defect entry having the first state information including position information on the replacement block and first state information indicating that the replacement block cannot be used to replace another defect block, the second state information indicating that the replacement block corresponding to the new defect entry may be a defect block.