CN113439306B

CN113439306B - Magnetic memory device

Info

Publication number: CN113439306B
Application number: CN202180001800.3A
Authority: CN
Inventors: 寺户智浩
Original assignee: Toshiba Corp; Toshiba Infrastructure Systems and Solutions Corp
Current assignee: Toshiba Corp; Toshiba Infrastructure Systems and Solutions Corp
Priority date: 2020-01-17
Filing date: 2021-01-15
Publication date: 2023-06-06
Anticipated expiration: 2041-01-15
Also published as: CN113439306A; WO2021145406A1; JP2021114349A; TW202129507A; KR20220024746A; JP6946485B2; SG11202112189XA; TWI755064B

Abstract

The magnetic memory device of the embodiment comprises: a magnetic disk storing data; a magnetic head for reading and writing data from and to the magnetic disk, the magnetic head being moved over the magnetic disk by an actuator; a confirmation processing unit that executes a confirmation process of confirming the normality of data of a predetermined size among data stored in the disk at a predetermined timing; and a setting unit that sets a 1 st addition value to be set in advance for the higher address among the higher address and the lower address constituting the head address for starting the next confirmation processing when the confirmation processing is completed.

Description

Magnetic memory device

Technical Field

Embodiments of the present invention relate to magnetic storage devices.

Background

Conventionally, as means for storing data, magnetic storage devices (HDD (Hard Disk Drive)) and the like have been used in large numbers. The magnetic storage device includes a magnetic disk for storing data, and a magnetic head for reading and writing data from and to the magnetic disk and moving over the magnetic disk by an actuator.

With respect to magnetic storage devices, it is reported that failures occur due to long-time fixed-point levitation. The fixed-point suspension is the following phenomenon: when only specific data of the disk is accessed, the magnetic head hardly moves on the disk (including the case of not moving at all, the same applies hereinafter). If the fixed-point levitation continues for a long time, sometimes the lubricant on the disk becomes uneven or the magnetic head is adsorbed to the disk, thereby causing a failure.

Prior art literature:

patent literature:

[ patent document 1] Japanese patent laid-open No. 7-281966

Disclosure of Invention

Problems to be solved by the invention

However, in the prior art, long-term fixed-point levitation cannot be easily avoided in the magnetic storage device.

Accordingly, an object of an embodiment of the present invention is to provide a magnetic storage device capable of easily avoiding long-term fixed-point levitation.

Means for solving the problems

Drawings

Fig. 1 is a schematic diagram showing the overall configuration of a computer according to the embodiment.

Fig. 2 is a table showing information for calculating a head address of a patrol (patrol) process in the embodiment.

Fig. 3 is a flowchart showing inspection processing and the like in the computer according to the embodiment.

Fig. 4 is a flowchart showing a head address determination process of the next patrol process in the computer according to the embodiment.

Fig. 5 is a diagram showing a relationship between an address of the HDD and a target area of the patrol process in the embodiment.

Detailed Description

Hereinafter, embodiments of a magnetic storage device according to the present invention will be described with reference to the drawings. The present invention is not limited to the following embodiments.

Fig. 1 is a schematic diagram showing the overall configuration of a computer 1 according to the embodiment. The computer 1 (magnetic storage device) includes a main board 10, a RAID card 3, and a plurality of HDDs (Hard Disk drives) 2. The computer 1 further includes a display device such as a display, not shown, and an input device such as a keyboard and a mouse.

The main board 10 is a control board on which a CPU (central processing unit (Central Processing Unit)) 11, a ROM (Read Only Memory), a RAM (random access Memory (Random Access Memory), and the like, which are not shown, are mounted.

The HDD2 is used in a large amount because it can store large-capacity data even though its operation speed is low among the auxiliary storage devices for computers in recent years. The HDD2 is composed of a large number of components, and includes, for example, a magnetic disk for storing data, and a magnetic head for reading and writing data from and to the magnetic disk and moving the magnetic disk by an actuator.

Further, for example, the HDD2 in recent years has a hardware interface such as Serial attached SCSI (Serial Attached SCSI (SAS)) or Serial ATA (SATA), and the logical interface for connection is SCSI or ATA. In these logical interfaces, the storage location of data is managed in units of sectors, addresses, and the like.

The HDD2 is a device capable of storing large-capacity data at low cost, and is also a device for storing data by using a magnetic or actuator (motor or the like), and therefore, the storage of data cannot be sufficiently ensured due to physical factors. As a countermeasure technique, there is RAID (redundant array of inexpensive disks (Redundant Arrays of Inexpensive Disks)).

In RAID, a plurality of HDDs 2 are used to store redundant data. In this way, even when a failure of the HDD2 occurs, after the replacement of the failed HDD2, the data stored in the failed HDD2 can be restored based on the redundant data. RAID card 3 (hardware RAID board) implements the RAID functionality in hardware.

The RAID card 3 is an expansion card mounted on the computer 1. The RAID card 3 realizes not only the RAID function but also a function of patrol processing that periodically accesses the HDD2 and confirms the normality of data of the HDD 2.

In addition, as described above, the HDD2 has a problem that a failure occurs due to long-time fixed-point suspension. Thus, the following description is made regarding the following technique: by using the function of the patrol process of the RAID card 3, the range of the patrol process is set so as to periodically forcibly move the magnetic head, and by executing the patrol process, the long-time fixed-point suspension can be easily avoided.

The RAID card 3 includes a RAID controller 31. The RAID controller 31 is configured by hardware including a control device such as a processor and a storage device such as a flash memory, for example. The functions of the RAID controller 31 may be realized by hardware, software programs, or firmware.

The RAID controller 31 includes a processing unit 32, a setting unit 33, and a transmitting/receiving unit 34.

The processing unit 32 performs various processes related to RAID. The processing unit 32 also has a function as a patrol processing unit (check processing unit) that executes a patrol process (check processing) for checking the normality of data of a predetermined size among the data stored in the HDD2 at a predetermined timing.

The processing unit 32 determines the timing of the patrol process for each predetermined size of data so that the patrol process can be executed for a predetermined period (for example, several weeks) for all the data of the plurality of HDDs 2.

When the 1 st seek process is completed, the setting unit 33 sets the head address of the next seek process by adding the 1 st added value, which is preset to be equal to or greater than a predetermined amount of movement of the magnetic head on the magnetic disk in the radial direction for each seek process, to the head address (an example of the target address) of the seek process.

For example, when the range of the seek processing is set by the logical address of the HDD2, the 1 st addition value described above may be set to a value at which the head is moved by a predetermined amount or more in the radial direction on the disk per seek processing in consideration of the correspondence between the logical address and the physical address of the HDD2, the physical configuration of the HDD2, and the like, so that long-time fixed-point suspension can be reliably avoided.

When the patrol process is completed, the setting unit 33 adds the 1 st added value to the head address of the patrol process, and when the added address exceeds the address range of the disk, the head address of the next patrol process is set by adding the 2 nd added value to the low address of the 1 st prescribed number of bits, with the high address of the 1 st prescribed number of bits being set to 0. In this case, for example, the 2 nd added value is a predetermined size.

For example, when the head address of the next patrol process is set, the setting unit 33 sets the range of the next patrol process from the head address to the final address when the size from the head address to the final address of the address range is smaller than a predetermined size. Details of the processing by the setting unit 33 will be described later.

The transceiver 34 performs data transmission and reception with the main board 10 and the HDD 2.

Fig. 2 is a table showing information for calculating a head address of a patrol process in the embodiment. The setting unit 33 stores and manages information of the following items (1) to (6) in a nonvolatile storage unit in order to execute the patrol process.

(1) HDD Capacity (capability)

The unit is, for example, a sector, which is the total storage capacity information of the HDD2 as the auxiliary storage device. In addition, the final address of the address range is referred to as "final LBA (Last LBA)". For example, in the case where capability is "0x80000000" and the address range is "0x00000000" to "0x7FFFFFFF", the final LBA is "0x7FFFFFFF".

(2) Beginning Address (LBA) of next inspection process

The unit is, for example, a sector, which is the start address information of the next patrol process determined after the completion of the patrol process. The LBA is obtained by adding the following (3) LBA-L and (4) LBA-H. In the following description, the LBA is mainly set to 32 bits in the 2-ary system and 8 bits in the 16-ary system (hereinafter also referred to as "0 x"). Further, LBA-L is set to the lower 12 bits (2 nd predetermined number of bits) among the lower 32 bits of 2 th system of LBA, and the lower 3 bits (2 nd predetermined number of bits) among the lower 8 bits of 16 system. Further, LBA-H is set to 20 bits (1 st predetermined bit number) of the upper bits among the 32 lower bits in the 2 th system of LBA, and 5 bits (1 st predetermined bit number) of the upper bits among the 8 lower bits in the 16 system.

(3) Low order address (LBA-L)

The unit is, for example, a sector (details will be described later) which is the low-order address information of the 2 nd prescribed number of bits for calculating (2) LBA.

(4) High-order address (LBA-H)

The unit of the high-order address information of the 1 st prescribed number of bits for calculating (2) the LBA is, for example, a sector (details will be described later).

(5) High/low management split Shift (Shift)

Is bit shift value information (12 in the above example) in 2, which indicates a boundary for dividing an LBA into two parts, LBA-H and LBA-L. Hereinafter, the value obtained by shifting "1" to the higher order by Shift in the 2 nd order is "1 st added value". That is, if Shift is "12", the 1 st added value is "1000000000000" in the 2-ary, and "1000 (0×1000)" in the 16-ary.

(6) Inspection range (Size)

The size information is size information of data read out in the patrol processing, and the unit is, for example, a sector.

For example, when Shift is "12", the lower 12 bits of the LBA in the 2-system are LBA-L, and the remaining upper 20 bits are LBA-H. Specifically, for example, if the LBA is "0x12345678", LBA-L becomes "0x678", LBA-H becomes "0x12345000".

In addition, when Shift is "16", the lower 16 bits of the LBA in the 2-system are LBA-L, and the remaining upper 16 bits are LBA-H. Specifically, for example, if the LBA is "0x12345678", the LBA-L becomes "0x5678", and the LBA-H becomes "0x12340000".

In addition, for example, when the function of the RAID controller 31 is realized by firmware, the processing unit 32 executes the patrol processing at a predetermined timing from the transition of the firmware to the normal state.

When performing the patrol process, the processing unit 32 performs the patrol process on data of the size (6) (for example, "0×100") from the (2) LBA in the address range of the HDD 2.

The setting unit 33 sets the head address of the patrol process to be changed from the left side to the right side of the "LBA" in fig. 2. The processing in this case will be described with reference to fig. 3 and 4.

Fig. 3 is a flowchart showing the inspection processing and the like in the computer 1 according to the embodiment.

First, in step S1, the processing unit 32 determines whether or not the start timing of the patrol process is reached, and if yes, the process proceeds to step S2, and if no, the process returns to step S1.

In step S2, the processing unit 32 executes patrol processing for data of a predetermined Size (Size) from the LBA of the head address among the data stored in the HDD 2.

Next, in step S3, the processing unit 32 determines whether or not the result of the patrol processing in step S2 is normal, and if so, proceeds to step S4, and if not, proceeds to step S5.

In step S5, the processing unit 32 stores the result of the inspection processing in step S2 as data indicating an abnormality (error). Further, the user of the computer 1 may be notified of the error by voice or display.

In step S4, the setting unit 33 executes the head address determination process of the next patrol process. Step S4 will be described with reference to fig. 4. Fig. 4 is a flowchart showing a head address determination process (process of step S4 in fig. 3) of the next patrol process in the computer according to the embodiment.

In step S41, the setting unit 33 adds the 1 st addition value (for example, "0×1000") to the LBA-H, and calculates a new LBA-H.

Next, in step S42, the setting section 33 adds LBA-H and LBA-L, thereby calculating a new LBA.

Next, in step S43, the setting unit 33 determines whether or not the LBA exceeds the final LBA, and if yes, proceeds to step S44, and if no, proceeds to step S47.

In step S44, the setting unit 33 sets LBA-H to 0 ("0 x 00000000").

Next, in step S45, the setting unit 33 adds the 2 nd addition value (for example, "0×100") to the LBA-L, thereby calculating a new LBA-L.

Next, in step S46, the setting unit 33 adds LBA-H to LBA-L, calculates a new LBA, and proceeds to step S47.

In step S47, the setting unit 33 determines whether or not the address (lba+size-1) of the Size (Size) from the LBA to the front exceeds the final LBA, and if yes, proceeds to step S49, and if no, proceeds to step S48.

In step S48, the setting unit 33 sets the patrol processing range from LBA to (lba+size-1).

In step S49, the setting unit 33 sets the patrol processing range from the LBA to the final LBA.

A specific example of the calculation will be described with reference to fig. 2. In addition, refer to fig. 5. Fig. 5 is a diagram showing a relationship between an address of the HDD2 and a target area of patrol processing in the embodiment. The following is given as that the inspection processing results are all normal.

Each value of the column C1 of fig. 2 is an initial value. When the Size (for example, "0x 100") of the patrol process is performed with the LBA "0x00000000" of the column C1 as the start address, and then the start address of the next patrol process is determined, first, the 1 st added value "0x1000" is added to the LBA-H "0x00000000" of the column C1, and a new LBA-H "0x00001000" is calculated (step S41 in fig. 4).

Next, this LBA-H "0x00001000" is added to the LBA-L "0x000" of the column C1, thereby calculating a new LBA "0x00001000" (step S42).

At this time, the LBA "0x00001000" does not exceed the final LBA "0x7FFFFFFF" (step S43: NO).

In addition, the address (LBA+Size-1, i.e., "0x000010 FF") of the amount of "0x100" from LBA "0x00001000" to the Size "0x100" does not exceed the final LBA "0x7FFFFFFF" (step S47: NO).

Therefore, the patrol process range is set from LBA "0x00001000" to (lba+size-1, that is, "0x0000 FFF") (step S48). In this way, each value of the column C2 is set. Further, with respect to LBA-L and Size, the value of column C1 is copied to column C2.

As described above, the start address of the patrol process is updated at the end of each patrol process, and each value in fig. 2 is set to be in the state of column C3. When the Size (Size) "0x100" is determined after the patrol process is performed using the LBA "0x7FFFE000" of the column C3 as the start address, the 1 st added value "0x1000" is added to the LBA-H "0x7FFFE000" of the column C3 to calculate a new LBA-H "0x7FFFF000" (step S41).

Next, this LBA-H "0x7FFFF000" is added to the LBA-L "0x000" of the column C3, thereby calculating a new LBA "0x7FFFF000" (step S42).

At this time, the LBA "0x7FFFF000" does not exceed the final LBA "0x7FFFFFFF" (step S43: NO).

In addition, the address (LBA+Size-1, i.e., "0x7FFFF0 FF") from this LBA "0x7FFFF000" to the Size "0x100" does not exceed the final LBA "0x7FFFFFFF" (step S47: NO).

Therefore, the patrol process range is set from LBA "0x7FFFF000" to (lba+size-1, i.e., "0x7FFFF0 FF") (step S48). In this way, each value of the column C4 is set. Further, with respect to LBA-L and Size, the value of column C3 is copied to column C4.

Next, when the head address of the next patrol process is determined after the patrol process of the Size "0x100" is performed with the LBA "0x7FFFF000" of the column C4 as the head address, first, the 1 st added value "0x1000" is added to the LBA-H "0x7FFFF000" of the column C4, and a new LBA-H "0x80000000" is calculated (step S41).

Next, this LBA-H "0x80000000" is added to the LBA-L "0x000" of the column C4, thereby calculating a new LBA "0x80000000" (step S42).

At this time, the LBA "0x80000000" exceeds the final LBA "0x7FFFFFFF" (step S43: yes).

Therefore, LBA-H is set to 0 ("0 x 00000000") (step S44).

Then, the 2 nd addition value "0x100" is added to the LBA-L "0x000" of the column C4, thereby calculating a new LBA-L "0x100" (step S45).

Next, LBA-H "0x00000000" is added to LBA-L "0x100", thereby calculating a new LBA "0x00000100" (step S46).

In addition, the address (LBA+Size-1, i.e., "0x000001 FF") from this LBA "0x00000100" to the Size "0x100" does not exceed the final LBA "0x7FFFFFFF" (step S47: NO).

Therefore, the patrol process range is set from LBA "0x00000100" to (lba+size-1, that is, "0x000001 FF") (step S48). In this way, each value of the column C5 is set. Further, with regard to Size, the value of column C4 is copied to column C5.

In this way, the range of the patrol processing in the HDD2 moves in the longitudinal direction indicated by the arrow in fig. 5. Therefore, the magnetic head is forcedly operated at each inspection process, and long-time fixed-point suspension can be avoided.

Further, in the related art, the range of the patrol process moves in the lateral direction of fig. 5. Therefore, even if the patrol process is performed, the magnetic head hardly moves, and long-time fixed-point levitation cannot be avoided by the patrol process.

As described above, according to the computer 1 of the embodiment, when the patrol process is completed, the 1 st added value, which is preset to be a predetermined amount or more of the head to be moved in the radial direction on the disk every patrol process, is added to the head address of the patrol process, and the head address of the next patrol process is set, so that long-time fixed-point suspension can be easily avoided. That is, by utilizing the function of the patrol process inherent in the RAID card 3 and setting the head address of the patrol process as described above, the magnetic head can be easily forcedly moved at short intervals.

In addition, as a more specific setting procedure of the head address of the patrol process, when the address obtained by adding the 1 st added value to the head address of the patrol process exceeds the address range of the disk, the high-order address of the 1 st prescribed number of bits is set to 0, and the 2 nd added value is added to the low-order address of the 2 nd prescribed number of bits. The 2 nd added value is set to a predetermined size. As a result, as can be seen from fig. 5, the patrol processing can be executed without omission for the entire data of the address range of the HDD 2.

When the head address of the next patrol process is set, if the size from the head address to the final address of the address range is smaller than a predetermined size, the range of the next patrol process is set from the head address to the final address. Thus, even in the vicinity of the final address, the range of the patrol process can be appropriately set.

The program executed by the computer 1 according to the present embodiment is provided by being loaded in advance in a ROM or the like. The program may be provided by recording a file in a form that can be installed or executed on a computer-readable recording medium such as a CD-ROM, a Flexible Disk (FD), or a CD-R, DVD (digital versatile disk (Digital Versatile Disk)).

Further, the program may be stored in a computer connected to a network such as the internet, and may be downloaded via the network. The program may be provided or distributed via a network such as the internet.

The program is a module including the respective parts (the processing unit 32, the setting unit 33, and the transmitting/receiving unit 34), and is generated by a CPU (processor) reading out the program from the ROM as actual hardware and executing the program, and the respective parts are loaded on a main storage device.

While the present invention has been described with reference to several embodiments, these embodiments are presented by way of example and are not intended to limit the scope of the invention. These novel embodiments can be implemented in various other modes, and various omissions, substitutions, and changes can be made without departing from the spirit of the invention. These embodiments and modifications thereof are included in the scope and gist of the invention, and are included in the invention described in the claims and their equivalents.

For example, in the above embodiment, the case where Shift is "12" is mainly described. However, the Shift is not limited to this, and, for example, in view of the tendency of the HDD to have a large capacity in recent years, the Shift may be set to "16", "20", or the like, and another value may be used as the Shift within a range satisfying the condition that the fixed-point suspension for a long time can be avoided.

Description of the reference numerals

1 … … computer, 2 … … HDD,3 … … RAID card, 10 … … motherboard, 11 … … CPU,31 … … RAID controller, 32 … … processing unit, 33 … … setting unit, 34 … … transmitting/receiving unit.

Claims

1. A magnetic storage device is provided with:

a magnetic disk storing data;

a magnetic head for reading and writing data from and to the magnetic disk, the magnetic head being moved over the magnetic disk by an actuator;

a confirmation processing unit that executes a confirmation process of confirming the normality of data of a predetermined size among data stored in the disk at a predetermined timing; and

and a setting unit that sets a 1 st addition value to be set in advance for the higher address among the higher address and the lower address constituting the head address for starting the next confirmation processing when the confirmation processing is completed.

2. A magnetic memory device as in claim 1 wherein,

the setting unit sets the high-order address to 0 and adds a 2 nd added value to the low-order address when the head address exceeds the address range of the disk, thereby setting the head address of the next confirmation processing.

3. A magnetic memory device as in claim 2 wherein,

the 2 nd addition value is the prescribed size.

4. A magnetic memory device according to claim 3 wherein,

when the head address of the next confirmation processing is set, the setting unit sets the range of the next confirmation processing from the head address to the final address when the size from the head address to the final address of the address range of the disk is smaller than the predetermined size.