KR20120053101A - Compatible raid optical disc and managing method - Google Patents

Compatible raid optical disc and managing method Download PDF

Info

Publication number
KR20120053101A
KR20120053101A KR1020100114178A KR20100114178A KR20120053101A KR 20120053101 A KR20120053101 A KR 20120053101A KR 1020100114178 A KR1020100114178 A KR 1020100114178A KR 20100114178 A KR20100114178 A KR 20100114178A KR 20120053101 A KR20120053101 A KR 20120053101A
Authority
KR
South Korea
Prior art keywords
raid
file
information
disk
recorded
Prior art date
Application number
KR1020100114178A
Other languages
Korean (ko)
Inventor
양인창
Original Assignee
엘지전자 주식회사
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 엘지전자 주식회사 filed Critical 엘지전자 주식회사
Priority to KR1020100114178A priority Critical patent/KR20120053101A/en
Publication of KR20120053101A publication Critical patent/KR20120053101A/en

Links

Images

Classifications

    • G—PHYSICS
    • G11—INFORMATION STORAGE
    • G11B—INFORMATION STORAGE BASED ON RELATIVE MOVEMENT BETWEEN RECORD CARRIER AND TRANSDUCER
    • G11B19/00—Driving, starting, stopping record carriers not specifically of filamentary or web form, or of supports therefor; Control thereof; Control of operating function ; Driving both disc and head
    • G11B19/20—Driving; Starting; Stopping; Control thereof
    • G11B19/209—Driving; Starting; Stopping; Control thereof in multiple disk arrays, e.g. spindle synchronisation in RAID systems
    • G—PHYSICS
    • G11—INFORMATION STORAGE
    • G11B—INFORMATION STORAGE BASED ON RELATIVE MOVEMENT BETWEEN RECORD CARRIER AND TRANSDUCER
    • G11B27/00—Editing; Indexing; Addressing; Timing or synchronising; Monitoring; Measuring tape travel
    • G11B27/10—Indexing; Addressing; Timing or synchronising; Measuring tape travel
    • G11B27/19—Indexing; Addressing; Timing or synchronising; Measuring tape travel by using information detectable on the record carrier
    • G—PHYSICS
    • G11—INFORMATION STORAGE
    • G11B—INFORMATION STORAGE BASED ON RELATIVE MOVEMENT BETWEEN RECORD CARRIER AND TRANSDUCER
    • G11B7/00—Recording or reproducing by optical means, e.g. recording using a thermal beam of optical radiation by modifying optical properties or the physical structure, reproducing using an optical beam at lower power by sensing optical properties; Record carriers therefor
    • G11B7/004—Recording, reproducing or erasing methods; Read, write or erase circuits therefor
    • G11B7/0045—Recording
    • G—PHYSICS
    • G11—INFORMATION STORAGE
    • G11B—INFORMATION STORAGE BASED ON RELATIVE MOVEMENT BETWEEN RECORD CARRIER AND TRANSDUCER
    • G11B20/00—Signal processing not specific to the method of recording or reproducing; Circuits therefor
    • G11B20/10—Digital recording or reproducing
    • G11B20/12—Formatting, e.g. arrangement of data block or words on the record carriers
    • G11B20/1217—Formatting, e.g. arrangement of data block or words on the record carriers on discs
    • G11B2020/1218—Formatting, e.g. arrangement of data block or words on the record carriers on discs wherein the formatting concerns a specific area of the disc
    • G11B2020/1229—Formatting, e.g. arrangement of data block or words on the record carriers on discs wherein the formatting concerns a specific area of the disc lead-in area
    • G—PHYSICS
    • G11—INFORMATION STORAGE
    • G11B—INFORMATION STORAGE BASED ON RELATIVE MOVEMENT BETWEEN RECORD CARRIER AND TRANSDUCER
    • G11B20/00—Signal processing not specific to the method of recording or reproducing; Circuits therefor
    • G11B20/10—Digital recording or reproducing
    • G11B20/12—Formatting, e.g. arrangement of data block or words on the record carriers
    • G11B2020/1264—Formatting, e.g. arrangement of data block or words on the record carriers wherein the formatting concerns a specific kind of data
    • G11B2020/1265—Control data, system data or management information, i.e. data used to access or process user data
    • G11B2020/1285—Status of the record carrier, e.g. space bit maps, flags indicating a formatting status or a write permission
    • G—PHYSICS
    • G11—INFORMATION STORAGE
    • G11B—INFORMATION STORAGE BASED ON RELATIVE MOVEMENT BETWEEN RECORD CARRIER AND TRANSDUCER
    • G11B2220/00—Record carriers by type
    • G11B2220/20—Disc-shaped record carriers
    • G11B2220/25—Disc-shaped record carriers characterised in that the disc is based on a specific recording technology
    • G11B2220/2537—Optical discs
    • G—PHYSICS
    • G11—INFORMATION STORAGE
    • G11B—INFORMATION STORAGE BASED ON RELATIVE MOVEMENT BETWEEN RECORD CARRIER AND TRANSDUCER
    • G11B2220/00—Record carriers by type
    • G11B2220/40—Combinations of multiple record carriers
    • G11B2220/41—Flat as opposed to hierarchical combination, e.g. library of tapes or discs, CD changer, or groups of record carriers that together store one title
    • G11B2220/415—Redundant array of inexpensive disks [RAID] systems

Landscapes

  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

PURPOSE: A compatible RAID optical disc and a managing method thereof are provided to read each disc on which data are recorded in parallel by an RAID, thereby maintaining compatibility. CONSTITUTION: A lead-in area manages data recorded on a data area. The data area comprises the following units. A compatible area stores a restoration program, RAID file information, and RAID disc information. The restoration program restores RAID files into one file wherein the RAID files are distributed and recorded on RAID optical discs. The RAID file information manages information about the RAID files. The RAID disc information manages information about the discs on which the RAID files are distributed and recorded.

Description

Compatible RAID optical disc and managing method

The present invention relates to a method for distributing and writing data to two or more optical disks in a parallel manner while maintaining compatibility with a general optical disk device.

Redundant Array of Independent Disks (RAID), a technology that divides and stores some redundant data among several storage devices to increase the reliability of the storage device or improve the overall performance, is mainly used as a hard disk drive (HDD). ) Is applied. There are various ways of dividing data, which are called levels.

FIG. 1 illustrates an example in which a RAID is implemented in an HDD. RAID 0 is a method of simply writing a disk in parallel, and when there are several disks, the disk is divided into a certain amount of data size and divided into each disk and recorded sequentially. RAID 1 replicates two equal-sized disks with each other, and RAID 5 decomposes data into a constant size, such as RAID 0, and divides each disk into sequential records, but writes parity on one disk. In a way that recovers even if one drive fails, distributing parity to each disk rather than writing it to a fixed disk is different from RAID 3 and RAID 4.

There are attempts to apply RAID technology to optical disks that improve performance by storing or replaying data on multiple disks in parallel. FIG. 2 shows an example of applying RAID 0 to an optical disk, in which data decomposed into a certain size of data is written to several disks in parallel. When writing in a RAID method (except RAID 1), an individual disk has already been used. The continuity is broken and the data position and data information cannot be read.

As such, when data is written to two or more optical discs with RAID technology, there is a compatibility problem, unlike the standard format or file system of the optical disc (ISO9660 or UDF), so that the optical disc recorded with RAID is read by a general optical disc drive. It becomes impossible and becomes a barrier to applying RAID technology to optical disks.

Accordingly, the present invention has been made to solve the above problems, and an object of the present invention is to provide a method for maintaining compatibility so that each disk written in parallel with RAID can be read by a general optical disk drive.

A compatible RAID optical disk according to an embodiment of the present invention for achieving the above object, the data area; And a lead-in area for managing data recorded in the data area, wherein the data area includes a recovery program for recovering the recorded RAID files distributed and recorded in a plurality of RAID optical discs into a single file; A compatibility area for storing raid file information for managing information on a raid file in which a part of data is stored and raid disk information for managing information on the plurality of disks in which raid files are distributed and recorded; And a RAID area for storing a portion of the data.

In one embodiment, the recovery program is recorded as one file together with the raid file information and raid disk information or as a file separate from the raid file information and raid disk information, and the raid area is recorded as an independent file. The management information for each file may be recorded in the lead-in area, and the file including the recovery program may be recorded in the form of an executable file.

In one embodiment, the raid file information includes information indicating the number of raid files recorded on the disk, and for each raid file, information indicating a file identifier, meta information of the file, and data of the file are determined. The unit size information indicating the size of a predetermined unit, the information indicating the number of predetermined units included in the file, the information indicating the number of predetermined units included in the disk, and the corresponding disk when recording sequentially on each disk divided into units. At least one of the first unit address information indicating the location of the first recorded unit, and a flag indicating whether the first unit recorded on the disk is the first unit of the file.

In one embodiment, the first unit address information may be represented relative to the address at which the RAID region begins, and the unit size information may be represented by the number of other known units.

The RAID disk information may include: address information indicating an address where a RAID region starts on the disk, level information indicating a RAID level applied to parallel recording of data, number information indicating how many disks are written in parallel, And identifier information indicating an identifier of each disc recorded in parallel.

In one embodiment, the identifier information may be listed in recording order when data is sequentially recorded on each disk, and the RAID disk information may be separately provided for the level files and the number information for each RAID file included in the disk. And identifier information.

In an embodiment, the file including the raid file information and the raid disk information may be recorded in text form including both syntax and a value according to the syntax.

In one embodiment, the recovery program is executed on the operating system of the host connected to the optical disk drive in which the RAID optical disk is inserted, it is determined whether to automatically run with reference to the flag provided in a predetermined register, the executed recovery program is After restoring the RAID file to one file, the flag can be released and terminated.

Possible RAID optical disk management method according to another embodiment of the present invention, RAID file information for managing data on the RAID file distributed and recorded on the plurality of RAID optical disk, and the RAID file in which a part of the data is stored on the disk And a recovery program recorded on the RAID optical disk for storing the RAID disk information for managing the information on the plurality of disks in which the RAID file is distributed and recorded, on the operating system of the host connected to the optical disk drive into which the RAID optical disk is inserted. Checking the RAID file information and the RAID disk information with respect to the disk inserted into the optical disk drive, and reading and temporarily storing data recorded on the disk based on the identified information; Repeating the checking and storing step for each disc inserted into the optical disc drive; And restoring the temporarily stored data to one file after completing the repeating step for all of the plurality of disks.

In one embodiment, the recovery program is automatically executed when the host accesses the disk including the recovery program through the optical disk drive, and after execution, the flag is referenced with a flag provided in a predetermined register. If it is set, the execution may be terminated and if not set, the checking and storing may be performed, and after completing the restoring step, the flag may be released and terminated.

In the case of splitting and recording data to multiple optical discs using the multiple disc parallel recording method, since the individual optical discs are not compatible with the existing optical disc file system, there is a limit in recovering from the parallel recording method support system. It is effective in overcoming the limitations of recovery.

In addition, when configuring an archive library system using an optical disc, it is possible to apply a multi-disk parallel recording method that supports fast writing and reading.

Figure 1 shows an example in which RAID is implemented in the HDD,
2 illustrates an example in which RAID 0 is applied to an optical disk.
Figure 3 shows a disk area to which the present invention is applied in a continuous bar form,
4 shows an example of writing RAID data to a plurality of optical disks in a disk in a continuous bar form,
FIG. 5 illustrates a relationship between RAID file information recorded in a compatible area and RAID data recorded in a RAID area when a plurality of RAID files are written in parallel to a plurality of RAID disks.
FIG. 6 illustrates an example of information constituting a compatible region and syntax of the information according to the present invention.

Hereinafter, an embodiment of a compatible RAID optical disk and management method according to the present invention will be described in detail with reference to the accompanying drawings.

In order to recover a RAID disk having data divided into several disks by RAID method and reading from a general optical disk drive, not only RAID data written in the corresponding RAID disk and RAID data written in parallel to other RAID disks are read, Or combine into more files. To do this, a recovery application that can be read and executed from a general optical disk drive must be written to the RAID disk according to the optical disk file system (ISO9660 or UDF). RAID file information related to RAID files distributed and written in parallel across several disks, and RAID disk information such as the structure of the RAID disk, the names (or identifiers), and the order of distributed recorded disks must also be recorded in the RAID disk.

Accordingly, the optical disk according to the present invention manages RAID data corresponding to data recorded on a physical disk and RAID data distributed and recorded on the disk and other disks so as to maintain compatibility with the file system of the existing optical disk. RAID management information such as a recovery program, RAID file information, RAID disk information, and the like, can be recorded in the data area of the optical disk.

As shown in Fig. 3, at the beginning of the data area, a compatible region for recording RAID management information for managing RAID data recorded on the optical disk is formed, and the RAID data in the data area after the compatible area. A RAID region for recording the data may be formed.

4 illustrates an embodiment in which data is sequentially distributed and recorded in the RAID areas of four disks DISK 1 to DISK 4. For example, the compatibility area can be formed from LBA (Logical Block Address) 0 to 0xFFF of the data area, and the RAID area can be formed from LBA 0x1000. A RAID system that writes and plays back data in parallel is the starting address LBA of the RAID area. 0x1000 can be managed by converting to virtual address 0. LBA 0 and LBA 0x1000 are for example, and this invention is not limited to the value.

FIG. 5 shows a relationship between RAID file information recorded in the compatible area in each RAID disk and RAID data recorded in the RAID area.

In FIG. 5, FILE_A including RAID data of data 1 to 13 is recorded by distributing FILE_B including RAID data of data 14 to 41 to four RAID disks (DISK 1 to DISK 4), and the data of FILE_A is DISK. Start at 1 and the data in FILE_B starts at DISK 2. The RAID file information for the distributed files FILE_A and FILE_B is recorded in the compatibility area of each disk.

When a general optical disk drive reads a RAID disk according to the present invention, first, by reading the RAID management information recorded in the compatible area, the RAID data recorded in the RAID area of the disk is read, and each disk is sequentially changed. After reading the RAID data recorded in the RAID area of the file, you can collect it and obtain the desired file.

A recovery program that reads not only the RAID data recorded in the RAID area formed in the data area of the RAID disk according to the present invention but also the RAID data recorded in parallel in the RAID area of another disk, and then combines them into one or more files. It is recorded in the compatible area, and can be executed automatically or at the user's choice when the optical disk drive accesses the RAID disk.

In addition, the recovery program executed by the operating system (OS) of the host read by the optical disk drive and connected to the optical disk drive, reads the RAID file information and the RAID disk information recorded in the compatibility area and based on the RAID disk information, In addition to the RAID data written to the zone, check the other parallel RAID disks in which the RAID files written on the disks are written in parallel, and when the parallel RAID disk is inserted, the RAID file information and RAID disk information written to the compatible zones in the same way. After reading the RAID data recorded in the RAID area based on the read data and reading the RAID data for all the parallel RAID disks, the read RAID data may be merged into one or more files.

The recovery program recorded in the compatibility area is recorded as one file for compatibility with the conventional optical disk file system or as one file together with the RAID file information and the RAID disk information, and recorded as an executable file (.exe). When the host connected to the optical disk drive accesses the RAID disk through the optical disk drive, it can be executed automatically or by user's choice.

In the optical disk lead-in area, information about data recorded in the data area is recorded. In the RAID disk according to the present invention, a compatible area in which a recovery program, RAID file information, and RAID disk information is recorded is managed as one file and the file is stored. The information is recorded in the lead-in area, and the entire RAID area is also managed as one file so that the file information can be recorded in the lead-in area. Alternatively, the recovery program, the RAID file information, the RAID disk information, and the RAID area may be managed as separate files, respectively, in the lead-in area.

FIG. 6 shows an example of syntax of RAID file information and RAID disk information recorded in the compatible area.

In order to recover a RAID file recorded in parallel on a plurality of RAID disks, RAID file information and RAID disk information are required.

The RAID file information includes length indicating the size of the RAID file information, number_files indicating the number of RAID files recorded on the disk, and file_ID indicating a file identifier for each RAID file, name, attribute, and time information of the corresponding file. File_meta including information such as size, size, etc., when RAID data of the file is divided into predetermined units and sequentially written to each RAID disk, the size of a predetermined unit (for example, may be expressed as the number of sectors whose size is a known unit). Size_data_unit pointing to), number_units_total pointing to the number of the given unit contained in the file, number_unit_thisdisk pointing to the number of the given unit included in the RAID disk, start_address pointing to the location of the first unit written to the disk, and writing to the disk Start_flag to indicate whether the first unit It can hamhal.

In addition, the RAID disk information includes a length indicating the size of the RAID disk information, a start_address_RAID_region indicating an address where the RAID area starts on the disk, and a RAID level applied to parallel writing of the file for each RAID file written to the disk. RAID_level, number_disks indicating how many disks the file was written to in parallel, and disk_ID indicating the ID of each disk on which the file was written in parallel, where disk_ID is divided into the corresponding files and written to each disk sequentially. Can be listed. Here, the disk_ID may be a manufacturer identifier (ID) of the corresponding disk, or may be a disk name automatically input by a user or automatically generated by an application operating an optical disk driver.

Since RAID_level, number_disks, and disk_ID can be the same for each RAID file, you can write them only once instead of repeatedly recording each file. In addition, when RAID_level is 3 or 4, information indicating a disk on which parity is recorded, for example, parity_disk_ID, may be added to the RAID disk information. Also, RAID_level information may be recorded in each file of the RAID file information. When RAID_level is 5, parity_unit_flag information indicating parity may be recorded in each data unit of number_units_thisdisk number.

In FIG. 5, RAID management information recorded in the compatible area of DISK 1 will be described. In RAID file information, number_files is 2, size_data_unit is the size of RAID data data 1 (or FILE_A and FILE_B are the same as data 2, 3, 14, etc.), number_units_total is 13, and number_units_thisdisk is FILE_A. 4 (1, 5, 9, 13), and start_address is the location where data 1 is written. In FIG. 5, it may be the first address of a RAID region (expressed as a relative address starting from start_address_RAID_region), and start_flag Becomes 1 (because data 1, the first RAID data of FILE_A, is written to the disk). Also, in FILE_B, number_units_total is 28, number_units_thisdisk is 7 (17, 21,, 41), start_address is the location where data 17 is written, and start_flag is 0 (data 14 is the first RAID data of FILE_B). Because it is not written to disk).

Also, in the RAID disk information of DISK 1, start_address_RAID_region becomes 0x1000 when referring to the example of FIG. 4, RAID_level becomes 3 or 5, number_disks becomes 4, and disk_ID is DISK 1's ID-> ID of DISK 2-> It can be recorded in the same order as ID of DISK 3-> ID of DISK 4 (or ID of DISK 2-> ID of DISK 3-> ID of DISK 4-> DISK 1, etc.).

When a RAID disk is inserted into a conventional optical disk drive, and the recovery program in the form of an executable file is executed automatically or on user's OS of the connected host, the recovery program checks the RAID file information and the RAID disk information stored in the compatibility area. On the screen, a list of RAID files recorded on the disk and a list of all RAID disks in which the RAID files are distributed is displayed on the screen so that the user can select a RAID file to recover or automatically perform a recovery operation on all files.

The recovery program reads the RAID data of the RAID file distributed and recorded on the disk based on the identified RAID file information and the RAID disk information, and temporarily restores the RAID data to a mass storage medium such as a hard disk or flash memory provided in the memory or the connected host. After you save the data, you can display a guide message requesting that another RAID disk be inserted after all data on the disk has been read.

If another RAID disk is inserted afterwards, the recovery program recorded on that RAID disk may be automatically executed again. Therefore, by setting a flag (running_flag) in a predetermined register, the flag is set when the recovery program is automatically executed. If it is not set, it starts the operation only when it is not set, and sets the flag. If it is set, the recovery program of the corresponding disk is not executed. The recovery program, which continues to run while the disk is changing, can read all the RAID data distributed over multiple RAID disks, consolidate the RAID files, and then reset the flag as it exits. That is, a recovery program that is first accessed and executed by a RAID disk can continue to run even if the RAID disk is changed until all data is recovered.

When the RAID file information and the RAID disk information are recorded as one file separately from the recovery program, the file including the RAID file information and the RAID disk information includes text including both the syntax shown in FIG. 6 and the values according to the syntax. It can be written in a form so that users can access this file directly and identify the RAID disk and information related to the RAID file recorded on that disk.

A RAID system, in which a plurality of optical disk drives are prepared and distributes files in parallel to a plurality of optical disks and writes them in parallel, controls each optical disk drive to independently execute a compatible application of an executable file format in a compatible area of a predetermined size on each disk. Record the data divided into a predetermined size of a RAID file to be recorded in a RAID method in the RAID area after the compatible area, record information about the recorded RAID file as RAID file information in the compatible area, and Information about a plurality of disks inserted into an optical disk drive in which the RAID data is written, as RAID disk information in a compatible area, information about a recovery application managed as a separate file, and RAID file information managed as a separate file Information on managing the RAID and RAID disk information, and to manage the RAID area as a single file. To generate it can be recorded in the lead-in area of each disk. In a RAID system, the recovery program does not need to be run.

When the function of the above-described recovery program is implemented as firmware on the optical disk drive, and information identifying the RAID disk is recorded as a predetermined area or disk identifier of the lead-in area, the optical disk accessing the inserted RAID disk is performed. The disk drive may perform the operation of the recovery program sequentially on the RAID disk and other RAID disks.

The above-described preferred embodiments of the present invention are disclosed for purposes of illustration, and those skilled in the art can improve, change, and substitute various other embodiments within the technical spirit and scope of the present invention disclosed in the appended claims below. Or addition may be possible.

Claims (16)

Data area; And
A lead-in area for managing data recorded in the data area,
The data area,
A recovery program for recovering the raid files distributed and recorded on the plurality of raid optical disks into a single file, raid file information for managing information about the raid files in which a part of the data is stored on the disc, and the raid files distributed and recorded A compatibility area for storing RAID disk information for managing information on a plurality of disks; And
And a RAID area for storing a portion of the data. The method of claim 1,
The recovery program is recorded as one file together with the raid file information and raid disk information or as a separate file separately from the raid file information and raid disk information, and the raid area is recorded as an independent file, for each file. And management information is recorded in the lead-in area, and a file including the recovery program is recorded in the form of an executable file. The method of claim 1,
The RAID file information includes information indicating the number of RAID files recorded on the disk, and each disk is divided into information indicating a file identifier, meta information of the file, and data of the file in predetermined units. The unit size information indicating the size of the predetermined unit, the information indicating the number of predetermined units included in the file, the information indicating the number of the predetermined units included in the disk, and the first unit recorded on the disk. And at least one or more of address information indicating a location of a first unit address, and a flag indicating whether a first unit recorded on the disk is the first unit of the file. The method of claim 3, wherein
And the first unit address information is relatively represented based on an address at which the RAID region starts. The method of claim 3, wherein
And the unit size information is expressed by the number of other known units. The method of claim 1,
The RAID disk information includes address information indicating an address at which a RAID region starts on the disk, level information indicating a RAID level applied to parallel recording of data, number information indicating how many disks were written in parallel, and each disk recorded in parallel. And at least one of identifier information pointing to an identifier of the compatible optical disc. The method according to claim 6,
And the identifier information is listed in recording order when data is sequentially recorded on each disc. The method according to claim 6,
And the RAID disk information includes the level information, the number information, and the identifier information separately for each RAID file included in the disk. The method according to claim 3 or 6, wherein
And the file including the raid file information and the raid disk information is recorded in text form including both syntax and a value according to the syntax. The method of claim 2,
The recovery program is executed on the operating system of the host connected to the optical disk drive in which the RAID optical disk is inserted, and it is determined whether to automatically execute the program by referring to a flag provided in a predetermined register. And the flag is released and terminated after recovery to a file. Data of a RAID file distributed and recorded on a plurality of RAID optical disks, RAID file information for managing information about a RAID file in which a part of data is stored on the disk, and information about the plurality of disks on which a RAID file is distributed and recorded. The recovery program written to the RAID optical disk, which stores the managed disk information, runs on top of the host's operating system connected to the optical disk drive into which the RAID optical disk is inserted.
Confirming the RAID file information and the RAID disk information with respect to the disk inserted into the optical disk drive, and reading and temporarily storing data recorded on the disk based on the identified information; And
Repeating the checking and storing step for each disc inserted into the optical disc drive; And
And recovering the temporarily stored data into one file after completing the repeating step for all of the plurality of disks. 12. The method of claim 11,
The recovery program is recorded in the data area of the RAID optical disc as one file together with the RAID file information and RAID disk information or as a file separate from the RAID file information and RAID disk information, and includes the recovery program. Compatible file management method, characterized in that the file is recorded in the form of an executable file. 13. The method of claim 12,
The recovery program is automatically executed when the host accesses the disk including the recovery program through the optical disk drive. If the flag is set with reference to a flag provided in a predetermined register after execution, the recovery program is executed. Terminating and if not set, performing the checking and storing step, and after completing the restoring step, release the flag and terminate the compatible RAID optical disc management method. 12. The method of claim 11,
The RAID file information includes information indicating the number of RAID files recorded on the disk, and each disk is divided into information indicating a file identifier, meta information of the file, and data of the file in predetermined units. The unit size information indicating the size of the predetermined unit, the information indicating the number of predetermined units included in the file, the information indicating the number of the predetermined units included in the disk, and the first unit recorded on the disk. And at least one or more of address information indicating a location of the first unit address and a flag indicating whether the first unit recorded on the disk is the first unit of the file. 12. The method of claim 11,
The RAID disk information includes address information indicating an address at which an area where data of the RAID file is recorded on the disk starts, level information indicating a RAID level applied to parallel recording of data, and count information indicating how many disks are written in parallel. And at least one of identifier information indicating an identifier of each disc recorded in parallel. 16. The method according to claim 14 or 15,
And the file including the raid file information and the raid disk information is recorded in text form including both syntax and a value according to the syntax.
KR1020100114178A 2010-11-17 2010-11-17 Compatible raid optical disc and managing method KR20120053101A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
KR1020100114178A KR20120053101A (en) 2010-11-17 2010-11-17 Compatible raid optical disc and managing method

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
KR1020100114178A KR20120053101A (en) 2010-11-17 2010-11-17 Compatible raid optical disc and managing method

Publications (1)

Publication Number Publication Date
KR20120053101A true KR20120053101A (en) 2012-05-25

Family

ID=46269392

Family Applications (1)

Application Number Title Priority Date Filing Date
KR1020100114178A KR20120053101A (en) 2010-11-17 2010-11-17 Compatible raid optical disc and managing method

Country Status (1)

Country Link
KR (1) KR20120053101A (en)

Similar Documents

Publication Publication Date Title
US10168962B2 (en) Tape emulating disk based storage system and method with automatically resized emulated tape capacity
JP3607153B2 (en) File management method and apparatus
US8433867B2 (en) Using the change-recording feature for point-in-time-copy technology to perform more effective backups
US20060155944A1 (en) System and method for data migration and shredding
US8780480B2 (en) Presentation of shingled magnetic recording device to a host device resource manager
JP2013011919A (en) Storage apparatus and snapshot control method of the same
KR20080029677A (en) File storage system and file storage and file search method in file storage system
KR20070089603A (en) Apparatus, method, and computer program for processing information
JP5956971B2 (en) WORM cartridge support realized by LTFS (LinearTapeFileSystem)
CN101169705B (en) Method for implementing file class mirror-image under multiple hard disk based on nude file system
Hasenstein The logical volume manager (LVM)
US9235352B2 (en) Datastore for non-overwriting storage devices
KR20110106594A (en) Apparatus and method for setting a parity drive in optical disc drive archive system
JP2005284816A (en) Disk array system
CN111913664B (en) Data writing method and device
KR20120053101A (en) Compatible raid optical disc and managing method
KR101474285B1 (en) Fat file system and log data storage method of the same
KR20110103660A (en) Apparatus and method for recording raid of optical disc drive
US20140059305A1 (en) Management apparatus, storage device, and initialization method
CN102063273B (en) Hard disk management method and device
US7590780B2 (en) Method and computer program product to migrate legacy data to a RAID array while contemporaneously providing user access to legacy data
CN103617250A (en) File management method based on optical storage array and file format system
US20080140729A1 (en) Method for Changing Operation on a Storage Medium from a Current File System to a New or Updated File System
KR101077500B1 (en) Log Data Storage Method for Journaling FAT File System
JP4505520B2 (en) Disk array device and its control device, control method and control program

Legal Events

Date Code Title Description
WITN Withdrawal due to no request for examination