JP4798003B2 - Recording apparatus, recording method, program, and optical disk recording apparatus - Google Patents

Description

  The present invention relates to a recording apparatus, a recording method, a program, and an optical disk recording apparatus. Specifically, the present invention performs the read processing of the recording unit block necessary for the read modify write process from the recording medium when the size of the data requested to be sent from the host computer is smaller than the recording unit size of the recording medium. Related to a recording apparatus or the like that can perform data writing satisfactorily even when the recording unit block cannot be read by notifying the host computer of success or synchronization error after It is.

  The optical disk drive assigns an address to every accessible recording area of the optical disk as a loaded recording medium for each unit size defined by the standard of the optical disk, and sends it to a connected host PC (Personal Computer) Provide access services to that area. Here, the area of the unit to which this address is assigned is referred to as “access unit block”, and its size is referred to as “access unit size”.

  By the way, this access unit size is not necessarily equal to the unit size recorded on the optical disc. Here, the unit area recorded on the optical disc is referred to as “recording unit block”, and the size thereof is referred to as “recording unit size”. The recording unit size takes into account error correction due to scratches on the optical disk and the recording capacity, and has a size of 64 Kbytes, for example. On the other hand, the access unit size is smaller than the recording unit size, such as 2 Kbytes, in order to cope with accesses smaller than the cache page size (for example, 4 Kbytes) requested mainly from the host PC side.

  For this reason, a write request smaller than the recording unit size may be issued from the host PC to the optical disk drive. In that case, the optical disk drive once reads the recording unit block into the memory so as not to change the data that should not be changed in the writing process by the writing request, and partially writes the data requested to be written to the recording unit block. It is necessary to perform a read modify write process in which the overwritten recording unit block is written back to the optical disc in the recording unit size again. For example, Patent Document 1 describes an example of a read modify write process.

  Here, let us consider a case where a scratch that cannot be recovered by the optical disc drive has occurred on the optical disc. When writing is performed in the recording unit size in the defective area where the scratch has occurred, the optical disk drive performs replacement processing in the replacement area at another position on the optical disk with the recording unit size. However, a problem arises with respect to a write request that is smaller than the recording unit size that requires the above-described read-modify-write processing.

  This is because, in the course of the writing process of the optical disk drive, the underlying data that should not be changed due to scratches cannot be read out on the memory, so that the replacement process with the recording unit size cannot be performed. Here, there is no problem as long as the optical disc standard enables partial replacement processing with a recording unit size smaller than that. However, the present invention is an invention for a standard that only supports replacement in the recording unit size.

  On the other hand, the optical disk drive is a storage device connected to, for example, an ATA, SCSI, or USB bus. In this optical disc drive, a method called write-back caching is frequently used in order to increase the writing speed of the storage device as seen from the host PC.

Write-back caching is a process in which data requested to be written by the host PC is taken into the memory (cache memory) by the optical disk drive, although the optical disk is not actually written. This is a method of notifying the host PC that the command has been completed successfully and completing the apparent writing at high speed. By using this write-back caching, the host PC can be expected to increase the processing speed, such as the writing process being released quickly. For example, Patent Document 2 describes an example of write-back caching processing.
Japanese Patent Laid-Open No. 9-22375 JP 2002-15499 A

  The optical disk drive side can perform write back caching as long as the cache memory permits. However, since the writing process to the optical disk is delayed with respect to the notification of the command completion completion, as described above, a write request smaller than the recording unit size is issued to the recording unit block in which a scratch that cannot be recovered occurs. When this occurs, since the replacement process cannot be performed, a delay error is usually reported to the host PC for the next (another) instruction. On the other hand, a write request of the recording unit size or an integral multiple of the recording unit size can be made “successful” by performing an alternate process on the optical disc drive side, and therefore is unlikely to cause a delay error.

  Thus, when a write request smaller than the recording unit size is generated for a recording unit block in which a scratch that cannot be recovered occurs, the writing request fails. Here, the problem is that the host PC is notified of the successful completion of the command once even for a write request smaller than the recording unit size to the recording unit block in which an unrecoverable scratch has occurred. There is a possibility that the original data of the write request has already been released from the cache memory.

  When the original data of the write request is released from the cache memory, the host PC side cannot write to another area again, and eventually the data writing itself fails.

  An object of the present invention is to enable good data writing even when a recording unit block cannot be read.

The concept of this invention is
When the size of the data requested to be written is an integer multiple of the recording unit size of the recording medium, the recording medium is recorded as a recording unit block for each recording unit size. When the size of the data requested to be written is smaller than the recording unit size of the recording medium, the recording device writes the recording medium by a read modify write process ,
Data fetching means for fetching into the memory the data requested for writing sent from the host computer;
Data writing means for writing the data captured in the memory to the recording medium;
Data size determining means for determining the size of data captured in the memory;
Notification means for notifying the host computer of successful writing before the data writing means writes the data fetched into the memory to the recording medium;
The notification means is
When it is determined that the size of the data fetched into the memory by the data size determination means is an integral multiple of the recording unit size of the recording medium, the host computer is notified of the writing success,
When the size of the data taken into the memory by the data size judging means is determined to be recorded unit size smaller than the recording media, recording required from the data writing means the recording medium in the read modify write process upon successful reading of the unit block, it notifies the successful write to said host computer
In the records system.

  In the present invention, data for which a write request is sent from the host computer is taken into the memory. Then, the data captured in the memory is written on a recording medium such as an optical disk. In this case, when the size of the data requested to be written is smaller than the recording unit size, the data is written to the recording medium by the read modify write process.

  The size of the data fetched into the memory is determined, and the success or synchronization error is notified to the host computer according to the determination result. That is, when it is determined that the size of the data captured in the memory is smaller than the recording unit size of the recording medium, the recording unit block necessary for the read modify write process is read from the recording medium, and then the host computer A success or synchronization error is notified.

  In this case, when the recording unit block can be read, the read-modify-write process is possible, and the success is notified to the host computer. On the other hand, when the recording unit block cannot be read due to a scratch on the recording medium or the like, the read-modify-write process is impossible, and a synchronization error is notified to the host computer. As described above, if the recording unit block required for the read modify write process cannot be read, a synchronization error is notified to the host computer, so the host computer can write to another area again. It becomes.

  In this case, since processing different from the write-back caching processing is performed, the host computer cannot obtain the advantage that the writing process is released quickly. However, since the operation system (OS) tries to write in the recording unit size as much as possible, the frequency of the data requested for writing sent from the host computer is less often than the recording unit size.

  Further, in the present invention, for example, when it is determined that the size of the data taken into the memory is an integral multiple of the recording unit size of the recording medium, a success notification is immediately sent to the host computer. . In this case, since write back caching is performed, there is an advantage that the writing process is released quickly on the host computer side.

  According to the present invention, when the size of the data requested to be sent from the host computer is smaller than the recording unit size of the recording medium, the recording unit block reading process necessary for the read modify write process is performed from the recording medium. After that, the host computer is notified of success or synchronization error, and even if the recording unit block cannot be read, data can be written satisfactorily.

  Embodiments of the present invention will be described below with reference to the drawings. FIG. 1 shows a configuration example of an optical disc recording apparatus 100 as an embodiment.

  An optical disc recording apparatus 100 includes a CPU (Central Processing Unit) 101, an I / O (Input / Output) bridge 102, a main memory 103, a bus interface (BUS I / F) 104, and an internal bus (for example, an ATA bus). Etc.) 105, an optical disk drive 106, and a hard disk drive (HDD) 107.

  The CPU 101 constitutes a host computer. The CPU 101 and the main memory 103 are connected to the I / O bridge 102. The I / O bridge 102 is connected to the internal bus 105 via the bus interface 104. The optical disk drive 106 and the hard disk drive 107 are each connected to the internal bus 105. With such a configuration, the CPU 101 can control the optical disk drive 106 and the hard disk drive 107 connected to the internal bus 105 using the I / O bridge 102 and the bus interface 104.

  The optical disk drive 106 can be loaded with an optical disk 170 as a recording medium. The optical disk drive 106 includes a controller 161, a bus interface (BUS I / F) 162, an internal bus 163, a media input / output control unit 164, and a cache memory 165.

  The controller 161 controls the operation of the entire drive. Although not shown, the controller 161 includes a CPU, a ROM (Read Only Memory), a RAM (Random Access Memory), and the like. The CPU reads the control program stored in the ROM as necessary, transfers the read control program to the RAM, develops it, and reads and executes the developed control program, thereby controlling the operation of each unit. To do. The controller 161, media input / output control unit 164, and cache memory 165 are connected to the internal bus 163, and the internal bus 163 is connected to the internal bus 105 via the bus interface 162.

  An internal operation of the optical disc drive 106 when a write command and data (data requested to be written) is sent from the CPU 101 will be described. That is, a write command and data sent from the CPU 101 via the internal bus 105 are received by the bus interface 162 and are once taken into the cache memory 165. Thereafter, data (hereinafter referred to as “write data”) taken into the cache memory 165 is written to the optical disc 170 using the media input / output control unit 164.

  In the optical disc drive 106, the size of the write data fetched into the cache memory 165 (hereinafter referred to as “write data size”) is determined. When the write data size is smaller than the recording unit size (for example, 64 Kbytes) (less than the recording unit size), the write data is written to the optical disc 170 by the read modify write process. That is, the recording unit block (background data) is once read from the optical disk 170 onto the cache memory 165, the write data is partially overwritten on the recording unit block, and the overwritten recording unit block is again recorded in the recording unit size. Write back to optical disc 170. On the other hand, when the write data size is not less than the recording unit size (when it is an integral multiple of the recording unit size), the write data is written to the optical disc 170 as a recording unit block for each recording unit size.

  Note that the optical disc drive 106 does not support partial replacement processing with a recording unit size smaller than that, and only supports replacement with a recording unit size. Therefore, the optical disk drive 106 notifies the CPU 101 of success or a synchronization error in accordance with the determination result of the write data size.

  When the write data size is less than the recording unit size, processing different from write-back caching is performed. That is, after the recording unit block (background data) necessary for the read modify write process is read from the optical disc 170, the CPU 101 is notified of success or a synchronization error. In this case, when the recording unit block can be read, the read-modify-write process is possible, so the CPU 101 is notified of success. On the other hand, when the recording unit block cannot be read due to a scratch on the optical disk 170, the read-modify-write process is impossible, and therefore a synchronization error is notified to the CPU 101.

  On the other hand, when the write data size is not less than the recording unit size (when it is an integral multiple of the recording unit size), a write back caching process is performed. That is, when the write data is fetched into the cache memory 165, the CPU 101 is immediately notified of success.

  FIG. 2 shows a processing model of a write request when the write data size is less than the recording unit size. In this model, it is assumed that the recording unit size of the optical disc 170 is 64 Kbytes.

  (1) First, write data is written from a main memory (user memory) 103 to a cache memory (PC system cache) (not shown) in the CPU 101. The size of this write data is 4K bytes.

  (2) Next, a write command and write data are sent from the CPU 101 to the optical disc drive 106. The optical disk drive 106 takes the write command and write data into the cache memory 165.

  (3) Next, the optical disk drive 106 performs a reading process of recording unit blocks (background data) necessary for the read modify write process from the optical disk 170. The recording unit block obtained by this reading process is taken into the cache memory 165.

  (4) Next, when the recording unit block can be read from the optical disc 170 and the recording unit block is taken into the cache memory 165, the optical disc drive 106 notifies the CPU 101 of success. Upon receiving the success notification, the CPU 101 can release the writing process. On the other hand, when the recording unit block cannot be read from the optical disc 170 due to scratches or the like, the optical disc drive 106 notifies the CPU 101 of a synchronization error. Upon receiving the notification of the synchronization error, the CPU 101 can secure another recording area of the optical disc 170 and send the write command and write data to the optical disc drive 106 again.

  (5) Next, when the optical disk drive 106 notifies the CPU 101 of success, the optical disk drive 106 partially overwrites the write data in the recording unit block (background data) fetched into the cache memory 165.

  (6) Next, the optical disc drive 106 writes back the recording unit block obtained by overwriting to the optical disc 170.

  FIG. 3 shows a conventional processing model of a write request when the write data size is smaller than the recording unit size as a comparative example. In this model as well, the recording unit size of the optical disc 170 is assumed to be 64 Kbytes.

  (1) First, write data is written from a main memory (user memory) 103 to a cache memory (PC system cache) (not shown) in the CPU 101. The size of this write data is 4K bytes.

  (2) Next, a write command and write data are sent from the CPU 101 to the optical disc drive 106. The optical disk drive 106 takes the write command and write data into the cache memory 165.

  (3) Next, the optical disk drive 106 notifies the CPU 101 of success. Upon receiving the success notification, the CPU 101 can release the writing process.

  (4) Next, the recording unit block (background data) necessary for the read modify write process is read from the optical disc 170.

  (5) Next, when the recording unit block can be read from the optical disc 170, the write data is partially overwritten on the recording unit block (background data) fetched into the cache memory 165.

  (6) Then, the optical disc drive 106 writes back the recording unit block obtained by overwriting to the optical disc 170.

  When the recording unit block cannot be read from the optical disc 170, the optical disc drive 106 cannot perform the processes (5) and (6) described above, and the next (other) command from the CPU 101 is not received. On the other hand, it reports to the CPU 101 as a delay error. In this case, there is a possibility that the CPU 101 has already released the original data of the write request from the cache memory because the success notification is returned in the process (3) described above. When the original data of the write request is released from the cache memory, the CPU 101 cannot write to another area again, and eventually the data writing itself fails.

  The flowchart of FIG. 4 shows a command processing task for a write command (WRITE command) in the controller 161 of the optical disc drive 106.

  First, the controller 161 starts processing in step ST1, and then moves to step ST2. Then, when the controller 161 receives the write command ((WRITE command) and fetches it into the cache memory 165 in step ST2, the controller 161 proceeds to step ST3. In this step ST3, the controller 161 determines whether the delay error queue is empty. Determine whether or not.

  When the delay error queue is not empty, the controller 161 proceeds to step ST4. In step ST4, the controller 161 acquires an error packet (ERROR packet) from the delay error queue. In step ST5, the controller 161 transmits an error packet to the CPU 101 to notify the error, and then returns to the processing in step ST2.

  The notification of the delay error from the optical disc drive 106 to the CPU 101 is performed only when any command (command) is sent from the CPU 101 to the optical disc drive 106. Therefore, even when a write command is sent from the CPU 101 to the optical disc drive 106 as in the operations of steps ST3 to ST5 described above, if the delay error queue is not empty, an error packet is acquired from the delay error queue. The error packet is transmitted to the CPU 101.

  When the delay error queue is empty at step ST3, the controller 161 proceeds to step ST6. In step ST6, when the controller 161 receives the write data (WRITE data) and loads it into the cache memory 165, the controller 161 proceeds to step ST7. In step ST7, the controller 161 determines whether the data size of the write data is less than the recording unit size or an integer multiple of the recording unit size.

  When the data size is an integral multiple of the recording unit size, the controller 161 notifies the CPU 101 of success in step ST8, and then proceeds to step ST9. As described above, when the data size of the write data is an integral multiple of the recording unit size, the CPU 101 is notified of success when the write data is taken into the cache memory 165, and a write back caching process is performed.

  When the data size is smaller than the recording unit size in step ST7, the controller 161 immediately moves to step ST9. As described above, when the data size of the write data is less than the recording unit size, the CPU 101 is not notified of success when the write data is taken into the cache memory 165, which is a process different from the write back caching process.

  In step ST9, the controller 161 places the write packet (WRITE packet) in the IO request queue, and then returns to the processing in step ST2. Each time the controller 161 receives a write command (WRITE command) from the CPU 101, the controller 161 executes the same processing as described above. The write packet is composed of a write command and write data.

  The flowchart in FIG. 5 shows a write processing task in the controller 161 of the optical disc drive 106.

  First, the controller 161 starts processing in step ST11, and then proceeds to step ST12. In step ST12, the controller 161 acquires a write packet from the IO request queue. In step ST13, the controller 161 determines whether the data size of the write data is less than the recording unit size or an integer multiple of the recording unit size. When the data size is an integral multiple of the recording unit size, the controller 161 moves to step ST14. On the other hand, when the data size is less than the recording unit size, the controller 161 moves to step ST15.

  In step ST15, the controller 161 uses the media input / output control unit 164 to read out the recording unit block (background data) necessary for the read modify write process from the optical disc 170. In step ST16, the controller 161 determines whether or not the reading is successful. When the reading is not successful, the controller 161 notifies the CPU 101 of a synchronization error in step ST17, and then returns to step ST12. Upon receiving the notification of the synchronization error, the CPU 101 can secure another recording area of the optical disc 170 and send the write command and write data to the optical disc drive 106 again.

  When reading is successful in step ST16, the controller 161 can perform read-modify-write processing. Therefore, in step ST18, the controller 161 notifies the CPU 101 of success, and then proceeds to step ST19. Upon receiving the success notification, the CPU 101 can release the writing process.

  In step ST19, the controller 161 creates write data (WRITE data), and then proceeds to step ST14. Here, as described above, the write data is created by partially overwriting the write data sent from the CPU 101 on the recording unit block (background data) fetched into the cache memory 165.

  In step ST14, the controller 161 uses the media input / output control unit 164 to write data to the optical disc 170. In this case, the write data is written to the optical disc 170 as a recording unit block for each recording unit size. Then, in step ST20, the controller 161 determines whether or not the writing is successful. When the writing is successful, the controller 161 returns to the process of step ST12.

  When the writing is not successful due to a scratch on the optical disc 170 or the like, the controller 161 moves to step ST21. In step ST21, the controller 161 determines whether or not the recording area can be changed. When the replacement is possible, the controller 161 performs the replacement process in step ST22, and then returns to the process of step ST14 to perform the same process as described above. On the other hand, when the replacement is impossible, the controller 161 moves to step ST23. In step ST23, the controller 161 places the error packet in the delay error queue. And the controller 161 returns to the process of step ST12 after the process of step ST23.

  As shown in FIG. 4 and FIG. 5, in the above description, the command processing and write processing of the write command have a multitask configuration, but a single task configuration may be used.

  FIG. 6 shows a state of re-recording when a synchronization error is notified from the optical disk drive 106 to the CPU 101 (see step ST17 in FIG. 5), that is, when a synchronization error occurs.

  (1) Write data (shown with diagonal lines) smaller than the recording unit size (64 Kbytes) is sent from the CPU 101 to the optical disc drive 106 together with a write command.

  (2) Since the data size of the write data is less than the recording unit size, the optical disk drive 106 starts the recording unit block (background data) from the recording area of the optical disk 170 secured on the CPU 101 side in order to perform the read modify write process. However, reading of the recording unit block fails (indicated by “x”).

  (3) Since the optical disk drive 106 has failed to read the recording unit block (background data) necessary for the read modify write process, it notifies the CPU 101 of a synchronization error.

  (4) The CPU 101 secures a new recording area on the optical disc 170 in response to the notification of the synchronization error. Then, a write command to which write data (shown by hatching) is added is sent again from the CPU 101 to the optical disc drive 106. In the optical disk drive 106, write data is written into the recording area newly secured on the CPU 101 side by the read modify write process.

  If the optical disk drive 106 fails to read the recording unit block (background data) necessary for the read-modify-write process from the recording area of the optical disk 170 newly set on the CPU 101 side, the optical disk drive 106 again sends a synchronization error to the CPU 101. Will be notified.

  The flowchart in FIG. 7 shows processing of a file system driver (not shown) of the CPU 101.

  First, in step ST31, the file system driver starts processing, and proceeds to step ST32. In step ST32, when the file system driver acquires a file write request from an OS (Operating System) (not shown), the file system driver moves to step ST33. In step ST33, the file system driver determines whether a recording area has been secured on the optical disc 170 or not. When the recording area has been secured, the file system driver moves to step ST34.

  When the recording area is not secured, the file system driver moves to step ST35. In step ST35, the file system driver determines whether or not a recording area can be secured on the optical disc 170. When the recording area cannot be secured, the file system driver notifies the OS of an error in step ST36. In step ST37, the file system driver returns the processing to step ST32 after the OS releases the write data from the cache memory.

  When the recording area can be secured in step ST35, the file system driver secures the recording area on the optical disc 170 in step ST38, and then proceeds to step ST34.

  In this step ST34, the file system driver issues a write command (WRITE command) to which the write data stored in the cache memory is added and sends it to the optical disc drive 106. Then, in step ST39, the file system driver determines whether or not the writing is successful. In this case, the file system driver determines that writing has succeeded when there is a notification of success from the optical disc drive 106, and determines that writing has not succeeded when there is a notification of a synchronization error from the optical disc driver 106.

  When the writing is successful, the file system driver notifies the OS of the success in step ST40, and then returns to the processing of step ST32 via step ST37. On the other hand, when the writing is not successful, the file system driver moves to step ST41.

  In step ST41, the file system driver determines whether or not a new recording area can be secured on the optical disc 170. When the recording area can be secured, the file system driver reallocates the recording area in step ST42, and then returns to step ST34. In step ST34, the file system driver sends the optical disk drive 106 a write command to which the write data stored in the cache memory is added again.

  When the recording area cannot be secured in step ST41, the file system driver notifies the OS of an error in step ST43, and then returns to the processing of step ST32 via step ST37.

  In the optical disc recording apparatus 100 shown in FIG. 1, when the data size of the write data sent from the CPU 101 to the optical disc drive 106 is less than the recording unit size of the optical disc 170, the optical disc drive 106 stores the write data in the cache memory 165. At that time, the CPU 101 is not notified of the success, and the CPU 101 is notified of the success when the recording unit block (background data) necessary for the read modify write process is successfully read from the optical disc 170.

  When the optical disk drive 106 fails to read the recording unit block (background data) necessary for the read modify write process from the optical disk 170, it notifies the CPU 101 of a synchronization error. Therefore, the CPU 101 can receive the synchronization error and secure a new recording area on the optical disc 170 to write data.

  Therefore, when the data size of the write data sent from the CPU 101 to the optical disc drive 106 is smaller than the recording unit size of the optical disc 170, the optical disc drive 106 performs processing different from the write back caching processing. Writing can be performed satisfactorily.

  In this case, since processing different from the write-back caching processing is performed, the CPU 101 cannot obtain the advantage that the writing process is released quickly. However, since the operation system (OS) tries to write in the recording unit size as much as possible, the frequency of the size of the write data sent from the CPU 101 to the optical disk drive 106 is not so much smaller than the recording unit size.

  In the optical disc recording apparatus 100 shown in FIG. 1, when the data size of the write data sent from the CPU 101 to the optical disc drive 106 is an integral multiple of the recording unit size of the optical disc 170, the optical disc drive 106 Is stored in the cache memory 165, the success is notified to the CPU 101, and the write back caching process is performed. Therefore, the CPU 101 has an advantage that the writing process is released quickly.

  In the above embodiment, the optical disk recording apparatus 100 whose recording medium is the optical disk 170 has been described as an example. However, the present invention is similarly applied to a recording apparatus using other recording media such as a magnetic disk and a semiconductor memory. Of course you can. In addition, the numerical example of the recording unit size in the above embodiment is an example, and the present invention is not limited to this.

  The present invention can be applied to, for example, an optical disk recording apparatus in which data is written by read-modify-write processing when the size of write data is smaller than the recording unit size of the optical disk.

It is a block diagram which shows the structural example of the optical disk recording device as embodiment. It is a figure which shows the processing model of a write request in case a write data size is less than a recording unit size. It is a figure which shows the conventional processing model of the write request in case a write data size is less than a recording unit size as a comparative example. It is a flowchart which shows the command processing task with respect to the write command (WRITE command) in the controller of an optical disk drive. 5 is a flowchart showing a write processing task in the controller of the optical disc drive. It is a figure which shows the mode of re-recording when a synchronous error is notified to CPU from the optical disk drive (at the time of a synchronous error occurrence). It is a flowchart which shows the process of the file system driver of CPU.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 100 ... Optical disk recording device, 101 ... CPU, 102 ... I / O bridge, 103 ... Main memory, 104 ... Bus interface, 105 ... Internal bus, 106 ... Optical disk driver 107, hard disk drive, 161, controller, 162, bus interface, 163, internal bus, 164, media input / output control unit, 165, cache memory, 170, optical disk

Claims (4)

When the size of the data requested to be written is an integer multiple of the recording unit size of the recording medium, the recording medium is recorded as a recording unit block for each recording unit size. When the size of the data requested to be written is smaller than the recording unit size of the recording medium, the recording device writes the recording medium by a read modify write process ,
Data fetching means for fetching into the memory the data requested for writing sent from the host computer;
Data writing means for writing the data captured in the memory to the recording medium;
Data size determining means for determining the size of data captured in the memory;
Notification means for notifying the host computer of successful writing before the data writing means writes the data fetched into the memory to the recording medium;
The notification means is
When it is determined that the size of the data fetched into the memory by the data size determination means is an integral multiple of the recording unit size of the recording medium, the host computer is notified of the writing success,
When the size of the data taken into the memory by the data size judging means is determined to be recorded unit size smaller than the recording media, recording required from the data writing means the recording medium in the read modify write process upon successful reading of the unit block, it notifies the successful write to said host computer
Record apparatus. When the size of the data requested to be written is an integer multiple of the recording unit size of the recording medium, the recording medium is recorded as a recording unit block for each recording unit size. And when the size of the data requested to be written is smaller than the recording unit size of the recording medium, the recording method of writing to the recording medium by a read modify write process ,
A data fetching step of fetching into the memory the data requested for writing sent from the host computer;
A data writing step of writing the data captured in the memory to the recording medium;
A data size determining step for determining the size of the data captured in the memory;
A notification step of notifying the host computer of successful writing before writing the data captured in the memory in the data writing step to the recording medium;
In the notification step above,
When it is determined that the size of the data captured in the memory in the data size determination step is an integral multiple of the recording unit size of the recording medium, the host computer is notified of the writing success,
When the size of the data taken into the memory by the data size determining step is determined to record unit size smaller than the recording medium, the recording needed from the recording medium by the data writing step to the read modify write process upon successful reading of the unit block, it notifies the successful write to said host computer
Record method. When the size of the data requested to be written is an integer multiple of the recording unit size of the recording medium, the recording medium is recorded as a recording unit block for each recording unit size. And when the size of the data requested to be written is smaller than the recording unit size of the recording medium, the recording method of writing to the recording medium by a read modify write process ,
A data fetching step of fetching into the memory the data requested for writing sent from the host computer;
A data writing step of writing the data captured in the memory to the recording medium;
A data size determining step for determining the size of the data captured in the memory;
A notification step of notifying the host computer of successful writing before writing the data captured in the memory in the data writing step to the recording medium;
In the notification step above,
When it is determined that the size of the data captured in the memory in the data size determination step is an integral multiple of the recording unit size of the recording medium, the host computer is notified of the writing success,
When the size of the data taken into the memory by the data size determining step is determined to record unit size smaller than the recording medium, the recording needed from the recording medium by the data writing step to the read modify write process upon successful reading of the unit block, the record how to notify the successful write to said host computer,
A program that causes a computer to execute. An optical disk recording apparatus in which a host computer and an optical disk drive are connected via a bus,
The optical disc drive is
The data requested to be sent from the host computer is recorded as a recording unit block for each recording unit size when the size of the data requested to be written is an integral multiple of the recording unit size of the recording medium. When writing to the medium and the size of the data requested to be written is smaller than the recording unit size of the recording medium, writing to the recording medium by a read modify write process,
Data fetching means for fetching into the memory the data requested for writing sent from the host computer;
Data writing means for writing the data captured in the memory to the recording medium;
Data size determining means for determining the size of data captured in the memory;
Notification means for notifying the host computer of successful writing before the data writing means writes the data fetched into the memory to the recording medium;
The notification means is
When it is determined that the size of the data fetched into the memory by the data size determination means is an integral multiple of the recording unit size of the recording medium, the host computer is notified of the writing success,
When the size of the data taken into the memory by the data size judging means is determined to be recorded unit size smaller than the recording media, recording required from the data writing means the recording medium in the read modify write process upon successful reading of the unit block, it notifies the successful write to said host computer
An optical disk recording device.

Images