JP2018116472A - Disk management system, disk management method, and disk management program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To perform efficient media error checking.SOLUTION: A disk management system including: an OS that secures a logical block to which an unclosed physical block of a disk device is allocated and uses it as a data writing area; driving means for converting an input address of a physical block into an address of a logical block to which the physical block is allocated, and acquiring use state information indicating whether the logical block of the converted address is in use from the OS and outputting the use state information; and medium inspection means for executing sequential test lead for physical blocks of the disk device and, if a failure is detected, acquiring the use state information from the driving means, and determining whether the logical block to which the failed physical block is allocated is in use, and a) if it is not in use, closing the physical block and proceeding to the test lead of the next physical block, and b) if it is in use, outputting a failure report.SELECTED DRAWING: Figure 1

Description

  The present invention relates to a disk management system, a disk management method, and a disk management program, and more particularly to a disk management system that performs a media error check.

  The disk array device makes disks redundant by a RAID (Redundant Arrays of Inexpensive Disks) configuration for the purpose of data integrity. However, if a media error occurs at the same address of the redundant disk, the data is lost.

  Even in such a case, it is possible to determine whether the location where the data was lost was an area where data important to the user was stored or an entirely unused area. Is also possible. (See Patent Document 1 described later).

  However, when data loss is detected by a media error check performed by the firmware of the disk array controller or the like, it is difficult to confirm the usage status. This is because the input / output during the check does not go through the OS Operating System).

  Patent Document 1 discloses a disk array controller corresponding to this problem. The disk array controller completes the recovery by allocating the alternative sector and writing the fixed data to the alternative sector without performing the data recovery by the data of the redundant disk device if the stripe in which the data reading has failed is unused. In order to do this, this disk array controller obtains information about the usage status of the logical block by the file system at that time from the host computer before performing the medium inspection.

JP 2003-303057 A

  Prior to the media error check, the disk array controller of Patent Document 1 acquires information about the stripe usage status in the file system at that time from the host computer. Therefore, the execution efficiency of the check is bad. This is because a large amount of information transmission / reception overhead occurs each time the media error check is performed, and during the media error check, it is not possible to change the usage status of the file generation, disappearance, and expansion stripes.

  This problem is not limited to the disk device constituting the RAID. A similar problem exists in the media error check of a single disk device.

  An object of the present invention is to solve the above problems and provide an efficient media error check.

The disk management system according to one embodiment of the present invention inputs an OS that secures and uses a logical block to which a non-blocked physical block of a disk device is allocated as a data writing area, and the address of the physical block Then, the address is converted into the address of the logical block to which the physical block is allocated, and usage status information indicating whether or not the logical block at the converted address is in use is acquired from the OS. When a test read is sequentially executed on the drive means for outputting and the physical block of the disk device and a medium failure is detected, the usage status information is obtained from the drive means, and the physical that has the medium failure It is determined whether the logical block to which the block is allocated is in use. A) If it is unused, the physical block The disk management method according to an embodiment of the present invention includes: a medium inspection unit that outputs a failure report if in use, and proceeds to the test read of the next physical block. Detected when a logical block to which an unoccluded physical block is allocated performs a test read on the physical block of the disk device used as a data write area sequentially and detects a media failure. The address of the physical block is converted into the address of the logical block to which the physical block is allocated, and usage status information indicating whether or not the logical block at the converted address is in use is acquired. Determine whether the logical block is in use; a) block the physical block if it is not used before the next physical block Proceed to test lead, b) if it is in use, and outputs a fault report.

  The disk management program according to an embodiment of the present invention secures a logical block to which a physical block that is not blocked of a disk device is allocated and uses it as a data write area, and an address of the physical block. The input is converted into the address of the logical block to which the physical block is allocated, and usage status information indicating whether or not the logical block at the converted address is in use is acquired from the OS. When the medium processing is detected by sequentially performing a test read on the physical block of the disk device and detecting a medium failure, the usage status information is obtained from the driving means, and the medium failure is detected. It is determined whether the logical block to which the physical block is allocated is in use. A) If not used, the physical block To close the lock advances to the test leads of the next of said physical block, b) if in use, to perform a medium testing process of outputting failure report, to the computer.

  The disk management system according to the present invention can perform an efficient media error check.

FIG. 1 is a diagram showing a configuration of a disk management system 40 according to the first embodiment. FIG. 2 is a configuration diagram of the computer device 60. FIG. 3 is a flowchart of medium inspection processing executed by the disk management system 40. FIG. 4 is a diagram illustrating a configuration of the disk management system 40 according to the first embodiment.

<First Embodiment>
<Configuration>
FIG. 1 is a diagram showing a configuration of a disk management system 40 according to the first embodiment. The disk management system 40 includes a disk management device 20, a disk control device 10 connected to the disk management device 20, and a disk device 30 connected to the disk control device 10.

  The disk management device 20 is sometimes called a host server or the like, and includes an OS 21 and a drive unit 22. The OS 21 has a general operating system function. In particular, the OS 21 includes modules that secure unused logical blocks of the disk device 30 and use them as data storage areas, such as a file system and a database system. The drive unit 22 is started from a file system or the like and executes input / output with respect to the disk device 30.

  The disk control device 10 is sometimes called a disk controller or the like, and includes a medium inspection unit 11, a management table 12, and an input / output unit 13. The input / output unit 13 is activated from the drive unit 22 and executes input / output for a file system or the like. The medium inspection unit 11 and the management table 12 will be described later.

  The disk device 30 is, for example, a magnetic disk device. When a plurality of disk devices 30 are present, a RAID may be configured. The storage area of the disk device 30 is divided into a plurality of physical blocks of, for example, 521 bytes. A plurality of physical blocks having consecutive addresses are allocated to the logical block which is a management unit of the OS 21. The logical block is, for example, 8 kilobytes. The OS 21 determines the size of the logical block.

  The OS 21 performs processing in units of logical blocks, and the medium inspection unit 11 and the input / output unit 13 perform processing in units of physical blocks. The drive unit 22 converts the addresses of the logical block and the physical block.

The medium inspection unit 11 of the disk control device 10 inspects the medium of the disk device 30 and is also called a medium error. The medium inspection unit 11 inspects a media error by sequentially test-reading the physical blocks of the disk device 30 in, for example, the order of addresses. When the medium inspection unit 11 detects a media error of a certain physical block, the medium inspection unit 11 performs the following processing.
If a failed physical block is in use, recovery is attempted with the data of another disk device 30 having a redundant configuration, and if the recovery fails, a report is made to the OS 21, for example.
If the faulty physical block is unused, the block of the physical block is recorded in the management table 12. The blocked physical block is not assigned to a logical block used for the OS 21.

  Here, the medium inspection unit 11 and the input / output unit 13 of the disk control device 10 are configured by logic circuits.

  The disk control device 10 may be realized by the computer device 60. FIG. 2 is a configuration diagram of the computer device 60. The computer device 60 includes a processor 61, a main storage unit 63, and an external storage device 62 that are connected to each other via a bus 64. The processor 61 reads and writes data from and to the main storage unit 63 and the external storage device 62 via the bus 64. Further, the processor 61 executes a program 65 stored in the main storage unit 63. Note that the program 65 is initially stored in the external storage device 62, and the processor 61 may load the main storage unit 63 from the external storage device 62 when the computer device 60 is initially set.

  Here, the main storage unit 63 is a semiconductor memory device. The external storage device 62 is an HDD (Hard Disk Drive) or a storage device such as a semiconductor storage device.

  The processor 61 of the disk control device 10 functions as the medium inspection unit 11 and the input / output unit 13 by executing the program 65. That is, the processor 61 executes the process performed by the medium inspection unit 11 and the input / output unit 13 by executing the program 65.

  The external storage device 62 may be used as a storage area for logical block usage status information acquired from the OS 21.

  Note that the program 65 in FIG. 6 may be firmware stored in a ROM (Read Only Memory) (not shown). That is, the medium inspection unit 11 and the input / output unit 13 may be realized by firmware.

  The disk management device 20 is realized by a computer device 60. The processor 61 of the disk management device 20 functions as the OS 21 and the drive unit 22 by executing the program 65.

<Operation>
FIG. 3 is a flowchart of medium inspection processing executed by the disk management system 40.

  First, in the disk control device 10, the medium inspection unit 11 is activated, for example, periodically or by a command. The medium inspection unit 11 selects the disk device 30 to be inspected, for example, the disk device 30 (1) in FIG.

  The activated medium inspection unit 11 selects the first physical block of the selected disk device 30 (1) and issues a test read (S1). If it is normal (Y in S2), the medium inspection unit 11 sequentially issues a test read to the next physical block (N in S8), and the test of all physical blocks in the disk device 30 (1) is completed. This is repeated until (S8: Y). Thereafter, the medium inspection unit 11 selects the next disk device 30 to be inspected, for example, the disk device 30 (2) in FIG. 1, and performs the same inspection.

  When a media error is detected in a test read (S1) of a certain physical block of the disk device 30 to be inspected (N in S2), the medium inspection unit 11 tests a physical block of the same address in another disk device 30. A lead is issued (S3). Here, the other disk device 30 refers to a disk device 30 that stores redundant data of the disk device 30 to be inspected, for example, the disk device 30 (1), for example, the disk device 30 (2).

  If the test read (S3) to the disk device 30 storing the redundant data ends normally (Y in S4), the medium inspection unit 11 repairs the data of the physical block in which the media error is detected with the redundant data (S9). ) Continue the inspection.

  If the test read (S3) to the redundant disk device 30 also ends abnormally (N in S4), the medium inspection unit 11 is assigned the physical block in which the media error is detected from the OS 21 via the drive unit 22. Usage status information indicating whether or not a logical block is used is acquired (S5). There are several alternative ways of processing in this step.

  The first method is as follows. First, the medium inspection unit 11 notifies the drive unit 22 that a media error has been detected and the address of the physical block in which the media error has been detected.

  Upon receiving the notification, the drive unit 22 acquires, from the OS 21, table information indicating the usage status of all logical blocks, and information necessary for address conversion such as the logical block size. Next, the drive unit 22 converts the address of the physical block in which the media error is detected into the address of the logical block to which the physical block is assigned. This conversion is performed based on the size ratio between the logical block and the physical block. Finally, the drive unit 22 notifies the medium inspection unit 11 of the logical block address and the table information obtained from the OS 21.

  Note that the OS 21 does not perform the process of changing the usage status of the logical block until the release notification described later after outputting the table information indicating the usage status of the logical address. This process is, for example, file generation, expansion, or deletion.

  Instead of notifying the medium checking unit 11 of the logical block address and the table information obtained from the OS 21, the driving unit 22 searches the table information obtained from the OS 21 using the logical block address and uses the logical block. It is also possible to notify the medium inspection unit 11 only of whether or not it is present.

  The second way is as follows. First, the medium inspection unit 11 notifies the drive unit 22 that a media error has been detected and the address of the physical block in which the media error has been detected.

  Upon receiving the notification, the drive unit 22 acquires information necessary for address conversion, such as a logical block size, from the OS 21. This information may be acquired in advance by the drive unit 22 from the OS 21 and stored in advance, for example, when the disk controller 10 is initially set. Next, the drive unit 22 converts the address of the physical block in which the media error is detected into the address of the logical block to which the physical block is assigned. Thereafter, the drive unit 22 adds an address of the logical block and outputs an information request indicating the usage status of the logical block to the OS 21. The OS 21 that has received the request outputs table information to the drive unit 22 as much as the usage status of the logical block at the specified address can be known. Finally, the drive unit 22 notifies the medium inspection unit 11 of the table information obtained from the OS 21.

  The third way is as follows. The third way is similar to the second way. However, the OS 21 having received the information request indicating the use status of the logical block to which the logical block address is added does not output to the drive unit 22 the table information as much as the use status of the specified logical block. . Instead, the OS 21 determines whether or not the logical block at the designated address is in use, and outputs flag information indicating the determination result. Finally, the drive unit 22 notifies the medium inspection unit 11 of flag information obtained from the OS 21.

  In the determination based on the usage status information obtained from the OS 21 (S6), if the logical block to which the physical block in which the media error is detected is unused (Y in S6), the medium inspection unit 11 The physical block is blocked (S7), and the process proceeds to the next physical block inspection (S8). At this time, the medium inspection unit 11 records the block of the physical block in the management table 12 and sends the above-described release notification to the OS 21 via the drive unit 22.

  The OS 21 does not use a logical block to which a physical block whose blockage is recorded in the management table 12 is assigned. Here, description of the interface between the OS 21 and the medium inspection unit 11 for this purpose is omitted.

  If the logical block to which the physical block in which the media error has been detected is in use (N in S6) in the determination based on the usage status information obtained from the OS 21 (N in S6), the medium inspection unit 11 Data loss due to an error is reported to, for example, the OS 21 (S10). At this time, the medium inspection unit 11 sends the above-described release notification to the OS 21 via the drive unit 22.

  The OS 21 that has received the report of data loss executes, for example, full backup file restoration, reinstallation, and file reconstruction.

<Effect>
The disk management system 40 according to the present embodiment can perform an efficient media error check. The reason is that the medium checking unit 11 does not need information for determining whether or not a logical block is in use when a physical block failure is not detected. That is, it is not necessary to transfer the usage status information.

  Furthermore, since the address of the physical block in which the failure is detected can be specified, the amount of usage status information to be transferred can be narrowed down.

  In other words, the disk management system 40 according to the present embodiment reduces both the transfer timing of the logical block usage status information and the transfer amount, so that the information transmission / reception overhead and the OS 21 generate, erase, and expand the file. The period during which the usage status cannot be changed is reduced.

<Modification>
The drive unit 22 may be included in the disk control device 10 instead of the disk management device 20.

  Further, the disk management device 20 and the disk control device 10 may be implemented as one device. That is, one device may include all of the components of the other device.

  The disk device 30 does not necessarily have to be RAID. In that case, the steps of S3, S4, and S9 are not necessary in the flowchart of FIG.

  The medium inspection unit 11 may test whether the media error state can be resolved by overwriting a specific data pattern, instead of managing the physical block whose data has been lost by the management table 12. When managing with the management table 12, there is a possibility that a shortage of alternative sectors of the disk device 30 may occur when a problem occurs in a large number of physical blocks. If the media error is eliminated by overwriting, there is an effect that the physical block in which the medium failure is detected can remain usable.

<Second Embodiment>
FIG. 4 is a diagram illustrating a configuration of a disk management system 40 according to the second embodiment.

  The disk management system 40 includes an OS 21, a drive unit 22, and a medium inspection unit 11. The disk management system 40 is connected to one or more disk devices 30 via a communication network, for example. The disk device 30 may or may not constitute a RAID.

  The OS 21 secures a logical block to which an unblocked physical block of the disk device 30 is allocated and uses it as a data writing area. The OS 21 is, for example, a file system.

  The drive unit 22 receives the address of the physical block, converts it to the address of the logical block to which the physical block is assigned, and indicates whether or not the logical block of the converted address is in use Information is acquired from the OS 21 and output to the medium inspection unit 11.

  When the medium inspection unit 11 sequentially performs a test read on the physical blocks of the disk device 30 and detects a failure, the medium inspection unit 11 acquires usage status information from the drive unit 22 and is assigned a failed physical block. Determine if the logical block is in use. The medium checking unit 11 closes the physical block if it is not used and proceeds to the test read of the next physical block, and outputs a failure report to, for example, the OS 21 if it is in use.

  The OS 21 that has received the failure report restores a full backup file or reinstalls a program file, for example.

  The disk management system 40 according to the present embodiment can perform an efficient media error check. The reason is that the medium checking unit 11 does not need information for determining whether or not a logical block is in use when a physical block failure is not detected. That is, it is not necessary to transfer the usage status information.

  Furthermore, since the address of the physical block in which the failure is detected can be specified, the amount of usage status information to be transferred can be narrowed down.

  While the present invention has been described with reference to the embodiments, the present invention is not limited to the above embodiments. Various changes that can be understood by those skilled in the art can be made to the configuration and details of the present invention within the scope of the present invention.

DESCRIPTION OF SYMBOLS 10 Disk control apparatus 11 Medium inspection part 12 Management table 13 Input / output part 20 Disk management apparatus 21 OS
22 drive unit 30 disk device 40 disk management system 60 computer device 61 processor 62 external storage device 63 main storage unit 64 bus 65 program

Claims (10)

An OS that secures a logical block to which a physical block that is not blocked in the disk device is allocated and uses it as a data writing area;
When the address of the physical block is input, the address is converted into the address of the logical block to which the physical block is allocated, and usage status information indicating whether or not the logical block of the converted address is in use. Driving means for obtaining and outputting from the OS;
When a test read is sequentially performed on the physical blocks of the disk device and a medium failure is detected, the usage status information is acquired from the drive unit, and the physical block having the medium failure is allocated. Determine whether the logical block is in use, a) block the physical block if it is not used, and proceed to the test read of the next physical block, b) output a failure report if it is in use And a medium inspection means. The disk device has a redundant configuration with another disk device, and the medium checking means sequentially executes the test read on the physical block of the disk device, and detects the medium failure, the other When the test read is executed on the corresponding physical block in the disk device and the medium failure is detected again, the usage status information is obtained from the drive unit, and the physical block having the medium failure is The disk management system according to claim 1, wherein it is determined whether the allocated logical block is in use. The drive means calculates the address of the logical block to which the physical block is allocated from the input address of the physical block, and outputs the calculated address to the OS.
The disk management system according to claim 1, wherein the OS determines whether or not the logical block at the input address is in use, and outputs a determination result. A disk management device comprising the OS and the drive means;
A disk control device comprising the medium inspection means;
The disk management system according to any one of claims 1 to 3, comprising the disk device. A disk management device comprising the OS;
A disk control device comprising the medium inspection means and the drive means;
The disk management system according to any one of claims 1 to 3, comprising the disk device. A disk control device comprising the OS, the medium inspection unit, and the driving unit;
The disk management system according to any one of claims 1 to 3, comprising the disk device. A logical block to which a physical block that is not blocked is assigned performs a test read sequentially on the physical block of the disk device that is used as a data write area,
When a medium failure is detected, the address of the detected physical block is converted to the address of the logical block to which the physical block is allocated, and whether or not the logical block at the converted address is in use. Get usage information that indicates
Determine whether the logical block is in use, a) block the physical block if it is not used, and proceed to the test read of the next physical block, b) output a failure report if it is in use Disk management method. The disk device has a redundant configuration with other disk devices,
When the test read is sequentially performed on the physical block of the disk device and the medium failure is detected, the test read is performed on the corresponding physical block in the other disk device, and the medium is again performed. 8. The disk management according to claim 7, wherein when a failure is detected, the usage status information is acquired from the drive means to determine whether the logical block to which the physical block having the medium failure is allocated is in use. Method. OS processing for securing a logical block to which a physical block that is not blocked in the disk device is allocated and using it as a data writing area;
When the address of the physical block is input, the address is converted into the address of the logical block to which the physical block is allocated, and usage status information indicating whether or not the logical block of the converted address is in use. Driving processing to be obtained and output from the OS;
When a test read is sequentially performed on the physical blocks of the disk device and a medium failure is detected, the usage status information is acquired from the drive unit, and the physical block having the medium failure is allocated. Determine whether the logical block is in use, a) block the physical block if it is not used, and proceed to the test read of the next physical block, b) output a failure report if it is in use A disk management program for causing a computer to execute medium inspection processing. The disk device has a redundant configuration with another disk device. When the test read is sequentially performed on the physical block of the disk device and the medium failure is detected, a response in the other disk device is performed. When the test read is executed on the physical block and the medium failure is detected again, the usage status information is acquired from the driving unit, and the physical block having the medium failure is allocated to the logical block. 10. The disk management program according to claim 9, which causes a computer to execute the medium inspection process for determining whether a block is in use.

Images