JP2008158768A - Information storage device control method, information storage device, program, and computer-readable information recording medium - Google Patents

Abstract

An object of the present invention is to provide a configuration capable of effectively dealing with a failure in maintaining a redundant state in an information storage device for making stored information redundant.
When a failure occurs in maintaining a redundant state of information, the redundancy failure recording unit records the fact in the state recording unit, and the redundancy monitoring unit reports the redundancy failure from the state recording unit. And when the record of the redundancy failure is read by the redundancy monitoring means, the notification means notifies the fact.
[Selection] Figure 4

Description

  The present invention relates to an information storage device control method, an information storage device, a program, and a computer-readable information recording medium, and more particularly to an information storage device control method having a function of making information stored in an information storage device redundant, The present invention relates to an information storage device, a program for causing a computer to execute the control method, and a computer-readable information recording medium storing the program.

  In an information storage device in which hard disk devices are redundantly mounted for the purpose of high reliability, a minor failure of the redundant hard disk device, so-called “redundancy failure” may occur.

  For example, as shown in FIG. 1, a user operation function, a maintenance function, a test function, a communication function with an external monitoring device, etc. are provided as a computer called an SVP (service processor) 100 ′ for managing and controlling a large computer. Assume that two hard disk drives HDD # 0 151 and HDD # 1 152 for storing the SVP control program 20 ′ and control data necessary for realizing these functions are mounted.

  The SVP is also provided with an HDD duplication control unit 31 ′ for managing and controlling the two hard disk devices as resources of the redundant duplication configuration.

  The HDD duplication control unit divides two hard disk devices with the same configuration, and performs duplication control in units of divided partitions.

  When the HDD duplication control unit detects a failure that cannot be recovered in one of the hard disk devices (hard disk device # 0 in the example of FIG. 1), the failed partition (partition # 1 in the example of FIG. 1). Is switched to single control using only normal hard disk devices, and the operation of the upper SVP control program is continued.

  In addition, the HDD duplication control section notifies the maintenance personnel that the hard disk device has been made redundant, that is, the duplication state has partially broken.

  Here, in the specification and claims of the present application, “redundancy is lost” or “redundancy is lost” means that information is made redundant, that is, a plurality of pieces of information having the same contents are copied by copying the information to be made redundant. In a state where a plurality of pieces of information having the same contents are stored in each of a plurality of recording media, that is, in a redundant state, one of the plurality of pieces of information having the same contents is not the total number. Or, it means that the redundancy state is lost due to some failure in a plurality of pieces of information.

  In this “redundancy breakdown”, at least one piece of information having the same contents is free from any failure, so that no substantial loss of information has occurred. The effect of improving the safety of the information is only reduced accordingly.

  That is, in the example of FIG. 1, the frequency of occurrence of an unrecoverable failure in the normal hard disk drive side is low with respect to the partition whose duplex state has been lost due to the failure of redundancy. Therefore, it can be said that the degree of urgency with respect to the replacement work of the failed hard disk drive, which is the cause of the loss of redundancy, is not so high.

  However, it is not desirable to leave this state of failure of redundancy for a long time. Furthermore, there is a small possibility that a failure will occur on the normal hard disk device side of the partition. If such a situation occurs, the operation of the SPV itself will be stopped. Therefore, in order to prevent such a situation, the maintenance staff arranges a new hard disk device for early recovery from the breakdown of redundancy. It is desirable to replace the failed hard disk drive.

  On the other hand, a large computer that is subject to monitoring and control by the SVP has a large number of devices and parts, and there are many notification events necessary for maintenance other than the failure of a hard disk device connected to the SVP. Is also expensive.

Here, when a minor failure of the hard disk device (that is, the “redundancy of partition”) is detected, the SVP notifies the maintenance staff of that fact. Assuming that many other high-priority notification events happen to occur at the same time, they are reported to the maintenance staff almost at the same time, and there is a possibility that a report of a minor failure of the hard disk device may be overlooked.
JP 2004-271983 A

  The present invention has been made in view of such a situation, and when a failure occurs in the information storage device to maintain the redundancy of the stored information, measures are taken to eliminate the failure. An object is to provide such a configuration.

  In the present invention, the redundancy means performs redundancy of the information stored in the information storage device, and when a failure occurs in maintaining the redundant state of the information, the redundancy failure recording means indicates the redundancy failure. Is recorded in the status recording means, the redundancy monitoring means reads the record indicating the redundancy failure from the status recording means, and when the redundancy monitoring means reads the record indicating the redundancy failure, the notification means The report was made.

  In the present invention, when the redundancy monitoring means reads the record indicating the redundancy failure from the state recording means, and when the redundancy monitoring means reads the record indicating the redundancy failure, the notification means notifies the fact. I do.

  For this reason, even if the maintenance staff does not respond to the first notification in the event of the occurrence of the redundancy failure, it records the redundancy failure from the status recording means by the redundancy monitoring means. When the data is read and the record of the redundancy failure is read by the redundancy monitoring means, the notification means notifies that fact.

  Therefore, it is possible to reliably avoid a situation where the redundant failure state is left for a long period of time.

  As described above, according to the present invention, when a failure in maintaining redundancy occurs in an information storage device having a function of making stored information redundant, there is a situation in which the state of the redundancy failure is left for a long period of time. It can be avoided reliably. For this reason, the redundant state of the stored information is reliably maintained in the information storage device, so that the safety of the stored information can be effectively ensured.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

  Example 1 of the present invention will be described.

  According to the first embodiment of the present invention, in a device that manages and controls a hard disk device having a redundant redundant configuration and can continue operation with a non-redundant configuration even when a failure occurs in one of the hard disk devices, After the failure is reported, if the failure is left unattended, the failure is automatically re-detected every certain time or every time the power is turned on, and the notification is made repeatedly.

  FIG. 2 is a block diagram for explaining the outline of a computer system including an SVP (service processor) as a computer for executing the control method of the information recording apparatus according to the first embodiment of the present invention.

  In FIG. 2, the main unit 200 of the computer system has various functional units SSM 212, SSX 0 124, SSX 1 215, SSU 216, IOP 217, I / O 219, and CLK 213 centering on a system board 211.

  The main device console 201 is a console for the user to operate various functions provided by the computer system to the user (functions provided by the OS operating on the system board 211).

  The SVP console 101 is a console for operating a user operation function, a maintenance function, and a test function. Only the user operation function can be operated in the user mode. In the maintenance mode, functions necessary for maintenance can be operated. The maintenance mode is used when maintenance is performed after user operation is stopped.

  The maintenance terminal 202 is a console for operating functions necessary for maintenance when maintenance (active maintenance) is performed without stopping user operations. Connect only during hot maintenance.

  The SVP 100 includes an MPU (microprocessor unit) 111, a cache 112, a ROM 121, a RAM 122, hard disk devices 151 and 152, an MO drive 161, a flexible disk drive 162, and the like configured as described above.

  The SSU 216 and I / O 219 are connected to the outside of the main body device 200, an SSU (System Storage Unit) 216 is a system storage device, and an I / O (Input / Output) 219 is an input / output device such as DASD.

  The following units are connected to the main unit 200 and are subject to control and maintenance by the SVP 100.

  System board 211: A plurality of CPUs and memories are mounted.

  CLK (Clock Board) 213: The clock is distributed to the system board 211.

  SSM (SS Mover) 212: connected to the SSU 216, and performs data transfer between the main memory and the system memory.

  IOP (Input / Output Processor) 217: Transfers data to / from the input / output device.

  SCI (System Console Interface) 103: Provides an interface for the SVP 100 to control and communicate with each unit in the main device 200.

  SPC (System Power Controller) 102: Controls the power supply of the main apparatus 200 as a whole.

  FAN105: a cooling fan.

  FEP (Front End Power Supply) 106: supplies power to each unit in the main device 200.

  The following units are the SVP 100 itself connected to the main unit 200 and an adapter inside the SVP 100.

  SVP (Service Processor) 100: provides a user operation function, a maintenance function, a test function of the main device 200, and a communication function with the external monitoring device 300.

  SCIA (SCI Adapter) 144: an adapter that communicates with and controls the main apparatus 200 via the SCI 103.

  SPCA (System Power controller adapter) 145: An adapter that controls an interface with the SPC 103.

  DPA (Display Adapter) 143: an adapter for connecting a display device.

  SIA (Serial Interface Adapter) 146: an adapter for connecting lines.

  FDA (Floppy Disk Adapter) 141: an adapter for controlling a flexible disk. ("Floppy" is a registered trademark)

  MDA (Micro Disk Adapter) 130: an adapter that controls the hard disk drive and the MO drive.

  SCA (SVP Communication Adapter) 135: an adapter connected to the LAN, and performs communication between the external monitoring apparatus 300 and another SVP 400.

  FIG. 3 is a block diagram for explaining the software configuration of the SVP 100.

  The software of the SVP 100 includes a program for providing an SVP internal diagnosis function provided in the ROM 121 and an SVP control program 20 stored in the hard disk devices 151 and 152. The SVP control program 20 includes a kernel 10, a frame task 21, an interrupt task 22, an initialization task 23, an error log task 24, and a patrol task 25.

  The initialization task 23 provides a function of detecting a failure of the hard disk devices 151 and 152, and the patrol task 25 provides a function of detecting a failure of the hard disk devices 151 and 152.

  Further, the SVP control program 20 includes a hard disk device driver 30, a flexible disk driver 41, a LAN port driver 42, a display device control driver 43, an SCI driver, an SPC driver 45, and an RS232C port driver 46.

  The hard disk device driver 30 includes an HDD duplication control unit 31 and a SCSI control unit 32.

  The program provided in the ROM 121 performs diagnosis inside the SVP 100. That is, the HDD duplication control information written in the header part (partition # 0) of the hard disk devices 151 and 152 is read and the contents are expanded on the memory (RAM 122) (HDD duplication control information 31a). The program loads the SVP control program 20 from the hard disk devices 151 and 152.

  The kernel 10 also performs state control of each task, exclusive control between tasks, and communication control included in the SVP control program 20. It also manages and controls memory resources, timer resources, and files.

  The HDD duplication control unit 31 of the hard disk device driver 30 controls the duplication of the hard disk devices 151 and 152, that is, redundancy, using the duplication control information 31a.

  The HDD duplication control unit 31 calls the SCSI control unit 32 to execute operations such as starting, stopping, reading of information, and writing of the hard disk devices 151 and 152.

  Also, the HDD duplication control unit 31 activates the error log task 24 via a system call when a failure of the hard disk devices 151, 152 is detected, and reports a failure.

  The SCSI control unit 32 starts and stops the hard disk devices 151 and 152, sets an operation mode, writes information to the hard disk devices 151 and 152, reads information from the same device, acquires failure information, and the like.

  Here, the control targets of the SCSI control unit 32 are the two hard disk devices 151 and 152 and the MO drive 161.

  The flexible disk driver 41 controls the floppy disk drive 162 (see FIG. 2) (“floppy” is a registered trademark).

  The LAN port driver 42 performs communication control with the monitoring device 300.

  The display device control driver 43 performs communication control with the console 201 of the main device 100 and the console 101 of the SVP 100.

  The RS232C port driver 46 performs communication control between the maintenance terminal 202 and the RS232C.

  The SPC driver 45 performs communication control with the SPC 102. Control at the time of turning on / off the computer system is performed by communication with the SPC 102.

  The SCI driver 44 controls the main device 200 via the SCI 103.

  The initialization task 23 initializes and activates each task included in the SVP control program 20 when the SVP 100 is activated, and checks whether the hard disk devices 151 and 152 have failed. When the failure of the initialization task hard disk devices 151 and 152 is detected, the error log task 24 is activated via a system call to report the failure.

  Further, the patrol task 25 is periodically started to monitor the state of the main body device 200 and monitor the failure of the hard disk devices 151 and 152. Here, it is activated in units of 500 ms, 60 minutes, 1 day, 1 week depending on the monitoring target.

  The monitoring of the failure of the hard disk devices 151 and 152 by the patrol task 25 is performed on a weekly basis. When the failure of the hard disk devices 151 and 152 is detected, the error log task 24 is activated via a system call to detect the failure. Make a report.

  The error log task 24 is activated via a system call from a detection source task or driver when a failure of the main body device 200, a failure of the SVP 100, or a failure of the hard disk devices 151, 152 occurs. Display, notification to the monitoring device 300, and the like.

  The frame task 21 provides a predetermined user operation function 21 a and maintenance function 21 b via the SVP console 101 or the maintenance terminal 202.

  The user operation function 21a corresponds to a control function by the main body apparatus 200, and is a function that provides various functions (for example, a communication control function of a large-scale communication network) that the computer system should originally provide to the user.

  The maintenance function 21b provides a maintenance / replacement function for components of the main body device 200 and the SVP 100 itself.

  The interrupt task 50 performs processing for an interrupt from the main device 200 notified via the SCI 103.

  FIG. 4 is a block diagram showing an extracted function part according to the present invention, among the functions of the SVP 100.

  That is, in the first embodiment of the present invention, the HDD duplication control unit 31 reads out information from the hard disk devices 151 and 152 and detects a failure of the hard disk devices 151 and 152 when writing information to the device (step S1). .

  That is, when a minor failure of the hard disk devices 151 and 152, that is, a duplexing failure (redundancy failure) of a specific partition (partition # 1 in the example in FIG. 4) is detected, the monitoring device is transmitted via the communication networks LAN # 0 and LAN # 1. This is notified to the maintenance staff by 300 or by the SVP console 101.

  Further, periodic monitoring is performed by the function of the patrol task 25, and the failure of the hard disk devices 151, 152 is detected and notified (step S2).

  That is, if the hard disk drive 151, 152 has a minor failure, that is, the failure of the partition (partition # 1) has been duplicated, the failure has been left after a certain period of time, and this is detected and the communication network LAN # 0, The maintenance device 300 is notified via the LAN # 1 or the SVP console 101 to the maintenance staff that a “minor failure” has occurred. Similarly, the status is further monitored at regular time intervals, and a notification of “minor failure” is repeatedly given to maintenance personnel until the duplex status is restored.

  Also, the function of the initialization task 23 detects and reports the failure of the hard disk devices 151 and 152 when the operation of the computer system is started (step S3).

  That is, after detecting a minor failure of the hard disk devices 151, 152, that is, the failure of duplication of the partition # 1, when the system operation is once stopped by maintenance personnel and then the operation is resumed, the minor failure of the hard disk devices 151, 152 is still That is, when the duplication of partition # 1 is left undetected and this is detected, the monitoring device 300 or the SVP console 101 notifies the maintenance staff of a minor failure via the communication networks LAN # 0 and LAN # 1 again. .

  As a result, it is possible to effectively avoid a situation in which a minor failure of the hard disk devices 151 and 152 is left for a long period of time, thereby avoiding an SVP operation stoppage due to an overlapping failure of the hard disk devices 151 and 152 and providing a highly reliable function. It becomes possible to provide.

  Hereinafter, the configuration related to the information redundancy function among the functions of the SVP 100 will be described in more detail.

(1) Configuration of the dual hard disk drives 151 and 152:
The two hard disk devices 151 and 152 are divided by the same configuration, and the same data is stored in areas at the same positions of the hard disk devices 151 and 152.

  Here, an area allocated to the same position of these two hard disk devices 151 and 152 is referred to as a partition, and is a unit of the duplication control target.

  The same information for each partition is redundantly held by the master hard disk device and the slave hard disk device. That is, the information of each partition is stored in a duplex or redundant state.

(2) HDD duplication control information 31a:
In the two hard disk devices 151 and 152, identification numbers corresponding to mounting positions with respect to the main body device 200 of the computer system are assigned in order from # 0. Hereinafter, for convenience of explanation, the hard disk devices 151 and 152 may be referred to as hard disk devices HDD # 0 and HDD # 1, respectively.

  The plurality of partitions are assigned identification numbers from # 0 in the order of addresses in the hard disk devices 151 and 152.

  The HDD duplication control information 31a is composed of a data table corresponding to the partition number.

  Each table shows the number of the master hard disk device that holds the partition and the number of the failed hard disk device that holds the partition in duplicate.

  The HDD duplication control information 31a is stored in partition # 0 (corresponding to the header portion of the recording area of each of the hard disk devices 151 and 152).

  The HDD duplication control information 31a is read from the hard disk devices 151 and 152 when the computer system is turned on and expanded on the memory 122, and the duplication configuration and state of the hard disk devices 151 and 152 at the previous operation are inherited as they are.

  If the status of the hard disk devices 151 and 152 changes during the operation of the computer system, the HDD duplication control information written in the partition # 0 is updated simultaneously with the update of the information on the memory 122.

  In addition, the HDD duplication control information 31a records the duplication valid state that is referred to when the failed hard disk device 151 or 152 is replaced when the failed hard disk device is disconnected. The duplex valid state is information indicating whether the hard disk devices 151 and 152 are duplex or single.

  The HDD duplication control information will be described later with reference to FIG.

(3) HDD duplication control unit 31:
When the information is written to the hard disk devices 151 and 152, the HDD duplication control unit 31 writes the same information to the corresponding areas of the two hard disk devices 151 and 152 that hold the corresponding partition in an overlapping manner.

  When information is read from the hard disk devices 151 and 152, information is read from the area of the master hard disk device for the corresponding partition.

  When an error occurs in the writing process, the master hard disk device or slave hard disk device for the partition in which the error has occurred is recognized as a failure state.

  If an error occurs in the read process, the master hard disk device for the partition in which the error has occurred is recognized as being in a failure state.

  When the master hard disk device for the partition concerned in the reading or writing process fails, the hard disk device on the side where the failure has not occurred, that is, the slave hard disk device is re-recognized as the master hard disk device for the partition.

(4) Failure notification processing of the hard disk devices 151 and 152 by the HDD duplex control unit 31 (steps S4 in FIGS. 6 to 9):
When either of the master hard disk device or the slave hard disk device for a certain partition fails, the HDD duplication control unit 31 recognizes that the hard disk devices 151 and 152 have a minor failure, that is, the duplication of the partition has occurred.

  When the HDD duplication control unit 31 detects a minor failure of the hard disk devices 151 and 152 in this way, that is, the duplexing collapse of the partition, the minor maintenance failure is notified to the maintenance staff via the monitoring device 300 or the SVP console 101 as described above. Report to that effect.

(5) Hard disk device 151, 152 failure periodic monitoring process (step S5 in FIGS. 6-9):
The patrol task 25 of the SVP control program 20 performs regular monitoring processing for failures of the hard disk devices 151 and 152. The patrol task 25 is activated at weekly intervals to monitor whether there is a minor failure of the hard disk devices 151, 152, that is, whether the partition has been duplicated or not.

  When a failure is detected, a minor failure is reported to maintenance personnel via the monitoring device 300 or the SVP console 101 again.

  Further, the patrol task 25 monitors the presence or absence of a minor failure of the hard disk devices 151 and 152 every week, and a minor failure to maintenance personnel until the dual state (redundancy state) of the hard disk devices 151 and 152 is restored. Repeat the report.

(6) Failure detection processing of the hard disk devices 151 and 152 in the initialization processing (steps S6 in FIGS. 6 to 9):
The initialization task 23 of the SVP control program 20 is a minor failure of the hard disk devices 151 and 152 when the operation of the computer system is stopped by the maintenance staff and the operation of the system is restarted. Detect the presence or absence of double-collapse.

  When a minor failure of the hard disk devices 151, 152 is detected, the maintenance staff is notified of the minor failure via the monitoring device 300 or the SVP console 101 again.

  FIG. 5 is a diagram showing an example of the HDD duplex control information 31a.

In the figure, “duplexing valid state” indicates the duplexing state or the unifying state of the hard disk devices 151 and 152 as follows.

0: Duplex effective state 1: Single operation state in HDD # 0 2: Single operation state in HDD # 1

When the failed hard disk device is disconnected at the time of hot replacement of the hard disk device, the state is “HDD # 0 single operation” or “HDD # 1 single operation”. In other words, the operation is performed independently by any one of the hard disk devices, and therefore, the duplex (redundant) state of the stored information is invalidated, that is, a single state.

  That is, when a failure occurs in any of the hard disk devices 151 and 152, only the normal operation is performed, which is referred to as “single operation”. In such a case, the failed hard disk device is disconnected and replaced with a newly prepared hard disk device in the active state.

In FIG. 5, the “restoring flag” indicates a state in which the hard disk devices 151 and 152 are being duplexed and restored.

0: Copy not yet executed for restoration State 1: Data copying from HDD # 0 to HDD # 1 State 2: Data copy from HDD # 1 to HDD # 0

That is, when the duplexing is lost, one of the hard disk devices 151 and 152 is out of order, so that only the normal state is operated. When restoring the duplication, the information is copied from the normal one in operation to the one newly arranged, replaced and installed.

  In FIG. 5, “number of partitions” indicates the number of partitions that the hard disk devices 151 and 152 have.

The “duplex state of partition #n” (n: 0, 1, 2,...) Indicates the presence / absence of a duplex state for the partition as follows.

0: Partition is in normal duplex state 1: Partition HDD # 0 side is in failure state 2: Partition HDD # 1 side is in failure state

“Master HDD of partition #n” (n: 0, 1, 2,...) In FIG. 5 indicates the master hard disk device and slave hard disk devices 151 and 152 for the partition as follows.

0: HDD # 0 side is the master:
That is, if the duplex state of the partition (that is, the “duplex state of partition #n” (n: 0, 1, 2,...)) Is “HDD # 1 failure”, the HDD # The 0 side is the operational hard disk device and is the master.
1: HDD # 1 side is master:
Similarly to the above, when the duplication state of the partition is “HDD # 0 side failure”, the HDD # 1 side is the operation hard disk device and is set as the master.

In FIG. 5, “physical position of partition #n” indicates the start position (address) of each partition.

  6 to 9 are flowcharts for explaining the operation flow of the SVP control program 20 of the SVP 100.

  Here, the flow from the failure occurrence of the hard disk devices 151 and 152 to the replacement of the failed hard disk device will be described.

  FIGS. 6 to 7 show a flow from the failure occurrence of the hard disk devices 151 and 152 until the power supply of the computer system is turned off after the failure is left for two weeks.

  FIGS. 8 to 9 show the flow from the time when the computer system is turned off to the time when the power is turned on again and the hard disk drive is replaced after one week.

  In this case, it is assumed that the hard disk device HDD # 0 is the master in the duplex state of the hard disk devices 151 and 152.

  The duplication control information on partition # 0 is also subject to duplication control of the hard disk devices 151 and 152 as in the other partitions. Is omitted.

  In FIG. 6, when the maintenance engineer turns on the power of the computer system (step S11), the header portions of the hard disk devices 151 and 152 are read by the SVP internal diagnosis function by the program in the ROM 121 (step S12). The HDD duplication control information 31a is expanded in the memory 122 (step S13). This process will be described later with reference to FIGS.

  Next, the SPV internal diagnostic function reads the SVP control program 20 from the header portion of the master hard disk device HDD # 0 in the hard disk devices 151 and 152, and loads it into the memory 122 (step S14). Is completed (step S15).

  Next, the kernel 10 starts the initialization task 23 of the SVP control program 20 (step S16). The initialization task 23 performs failure detection processing for the hard disk devices 151 and 152. This process, that is, the process of step S6 will be described later with reference to FIGS.

  When the initialization process by the initialization task 23 is successfully completed (step S17), a predetermined user operation function 21a is executed (step S18), and predetermined operation data is transferred from the master hard disk device HDD # 0 by the function of the HDD duplication control unit 31. A file is read (step S19).

  Here, it is assumed that an abnormality occurs while reading a predetermined operation data file from the hard disk devices 151 and 152 for the purpose of performing the user operation function 21a. That is, it is assumed that a failure has occurred in the master hard disk device HDD # 0, and an abnormality has been detected when reading from the partition # 2 (step S20).

  In this case, the HDD duplication control unit 31 tries to read the partition # 2 from the slave-side hard disk device HDD # 1 and succeeds (step S21).

  Upon receiving the result, the HDD duplexing control unit 31 updates the HDD duplexing control information 31a being expanded in the memory 122 because the partition # 2 of the hard disk device HDD # 0 has failed (step S22). The HDD duplication control unit 31 updates the contents of the header part (partition # 0) of the hard disk devices 151 and 152 with the same contents (step S22).

  Next, the HDD duplication control unit 31 notifies the kernel 10 of the failure of the hard disk device HDD # 0 as “mild failure” (step S24).

  In this way, it is assumed that the operation data file has been normally read except for the “read failure” in step S20 (step S25).

  Then, it is assumed that the execution of the user operation function 21a has ended normally (step S26).

  Next, in FIG. 7, the kernel 10 activates the error log task 24 and notifies the maintenance personnel of the occurrence of the “minor failure” via the monitoring device 300 or the SVP console 101 (step S 27).

  Then, after one week has elapsed, the kernel 10 activates the patrol task 25 to execute the duplex state check processing of the hard disk devices 151 and 152 (step S5). This process will be described later with reference to FIGS.

  As a result, it is detected that the failure state of the hard disk device HDD # 0 for the partition # 2 continues (step S30).

  Therefore, the patrol task 25 reports the failure of the hard disk device HDD # 0 to the kernel 10 (step S31).

  When this is completed (step S31), the kernel 10 activates the error log task 24 and notifies the maintenance personnel of the occurrence of a “minor failure” again via the monitoring device 300 or the SVP console 101 (step S32).

  After another week, the kernel 10 activates the patrol task 25 again (step S33). Thereafter, the processes of steps S34 to S37 are the same as the processes of steps S29 to S32, and the description thereof is omitted.

  Next, it is assumed that the maintenance staff operates the computer system to stop power (step S38).

  As a result, the hard disk drives 151 and 152 are stopped by the HDD duplication control unit 31 through the initialization task 23 under the control of the kernel 10 (steps S39 to S41). In response, the initialization task 23 turns off the computer system (step S42).

  Next, in FIG. 8, when the computer system is turned on by a maintenance person in step S51, the header portions of the hard disk devices 151 and 152 are executed by the SVP internal diagnosis function based on the program in the ROM 121, as in the operations after step S11. Is read (step S52). In step S23, the fact that the partition # 2 of the hard disk device HDD # 0 has failed is recorded in the header section.

  Further, the SVP internal diagnosis function by the program of the ROM 121 expands the HDD duplication control information read in this way in the memory 122 (step S53). Then, the SVP control program is loaded into the memory 122 (step S54), and the boot of the kernel 10 is completed (step S55).

  Next, the kernel 10 starts the initialization task 23 of the SVP control program 20 (step S56), and the initialization task 23 performs failure detection processing of the hard disk devices 151 and 152. As described above, this process, that is, the process of step S6 will be described later with reference to FIGS.

  In this case, the initialization task 23 recognizes the failure of the partition # 2 of the hard disk device HDD # 0 in this process, and the maintenance staff indicates that a “minor failure” has occurred via the monitoring device 300 or the SVP console 101 via the error log task 24. (Steps S57 and S59), and the initialization process ends (step S58).

  Furthermore, after one week, the kernel 10 activates the patrol task 25 again (step S60). Thereafter, the processing in steps S61 to S64 is the same as the processing in steps S29 to S32, and the description thereof is omitted.

  Here, in FIG. 9, it is assumed that the maintenance person performs hot replacement of the failed hard disk drive HDD # 0 in step S65.

  In that case, the maintenance function 21b of the frame task 21 in the SVP control program 20 refers to the HDD duplication control information 31a already developed in the memory 122 in the above step S53 (step S66), and as a result, is subject to the hot replacement. It is recognized that the failed hard disk device is the hard disk device HDD # 0.

  As a result, the maintenance function 21b issues an instruction to disconnect the failed hard disk device HDD # 01 from the SVP 100 (step S67), and the HDD duplication control unit 31 that receives the instruction stops the motor of the hard disk device (step S68). In other words, the hard disk device # 1 on the normal side is in a so-called “HDD unifying operation” state. Then, the HDD duplexing control information 31a developed in the memory 122 and the HDD duplexing control information in the header part of the hard disk device are respectively updated according to the HDD single operation state (steps S69 and S70). Then, the maintenance function 21b is notified that the process of shifting to the HDD single operation state has been completed (step S71).

  Thereafter, when the failed hard disk device HDD # 0 is replaced with a normal one by the maintenance personnel, the maintenance function 21b sends the original HDD that uses the replaced hard disk device HDD # 0 to the HDD duplication control device 31. An instruction to restore the HDD duplex state is issued (step S75).

  In response to this, the HDD duplexing control unit 31 updates the HDD duplexing control information 31a expanded in the memory 122 and the HDD duplexing control information in the header portion of the hard disk device to indicate that the HDD duplexing recovery is in progress (step). S76, S77).

  In step S78, the HDD duplication control unit 31 copies the stored information from the currently operating hard disk device HDD # 1 to the replaced new hard disk device HDD # 0, thereby changing the original HDD duplication state. Restore.

  When this copying process is normally completed for all partitions, the HDD duplexing control information 31a expanded in the memory 122 and the HDD duplexing control information in the header part of the hard disk device are updated accordingly (steps S79 and S80).

  Then, the HDD duplex control unit 31 notifies the maintenance function 21b that the HDD duplex state restoration has been completed (step S81).

  After one week, the kernel 10 activates the patrol task 25 again (step S83).

  In this case, since “normal state” is recorded in step S79 in the HDD duplication control information 31a developed in the memory, as a result of the reference, the patrol task 25 performs the HDD duplication state check processing normally. The completion is returned to the kernel 10 (step S85).

  As described above, according to the first embodiment of the present invention, when the state in which the duplex state of the hard disk devices 151 and 152 is lost is left by the functions of the initialization task 23 and the patrol task 25, the computer is restarted when the SVP 100 is restarted. During operation of the system, the status is regularly reported to maintenance personnel.

  Therefore, even if maintenance personnel are unable to take action according to the initial notification when the duplexing state is impaired, the maintenance personnel will restart the computer system or perform periodic notification during operation. Attention is drawn each time.

  Therefore, it is possible to effectively avoid a situation in which a state in which the duplex state of the hard disk devices 151 and 152 is lost is left for a long period of time.

  Next, the details of the process of reading the HDD duplication control information from the header part of the hard disk devices 151 and 152 by the SVP internal diagnosis function of the program stored in the ROM 121 and developing it in the memory 122 will be described with reference to FIGS.

  In FIG. 10, the header portion of the hard disk device HDD # 0 is read by the SVP internal diagnosis function (step S101), and if the header portion fails to be read, a flag indicating that fact is set (step S102). Yes, step S103).

  Similarly, the header part of the hard disk device HDD # 1 is read (step S104), and if the reading of the header part fails, a flag indicating that is set (Yes in step S105, step S106).

  Next, in FIG. 11, in step S107, it is determined whether or not the header portion has been successfully read in both the hard disk devices # 0 and # 1 by referring to the flag setting state.

When the header reading has failed in both the hard disk devices HDD # 0 and HDD # 1 (Yes in step S108), the operation of the SVP internal diagnosis function of the program in the ROM 121 ends abnormally. In that case, the process is stopped without loading the SVP control program. (When the SPC 102 detects that the SVP has stopped using the survival check function for the SVP, the SPC displays an error code indicating that the SVP has failed to start on the panel. Stop processing.)
On the other hand, if the reading of the header portion has failed with only the hard disk device HDD # 0 (Yes in step S109), the HDD duplication control information read from the header portion of the hard disk device HDD # 1 is expanded in the memory 122 (step S110). ).

  If only the hard disk device HDD # 1 fails to read the header portion (No in step S109), the HDD duplication control information read from the header portion of the hard disk device HDD # 0 is expanded in the memory 122 (step S111). ).

If the reading of the header part has succeeded in both the hard disk devices HDD # 0 and # 1 (Yes in step S107), both the hard disk devices HDD # 0 and # 1 in the information read from the header part. If a failure for partition # 0 (corresponding to the header portion) has been recorded (Yes in step S121 in FIG. 12, Yes in step S22), the operation of the SVP internal diagnosis function of the program in the ROM 121 ends abnormally. In that case, the process is stopped without loading the SVP control program. (When the SPC 102 detects that the SVP has stopped using the survival check function for the SVP, the SPC displays an error code indicating that the SVP has failed to start on the panel. Stop processing.)
On the other hand, if the failure of partition # 0 is recorded only for hard disk device HDD # 0 (Yes in step S123), the HDD duplication control information read from the header portion of hard disk device HDD # 1 is expanded in memory 122 (step S123). S124).

  If the failure of the partition # 0 is recorded only for the hard disk device HDD # 1 (No in step S123), the HDD duplication control information read from the header part of the hard disk device HDD # 0 is expanded in the memory 122 (step S123). S125).

  If there is no record of failure of partition # 0 in both hard disk devices HDD # 0 and # 1 in step S121, the process proceeds to step S126 in FIG.

  Here, if the hard disk device HDD # 0 is in a single HDD operation state (Yes in step S126, Yes in S127), the HDD duplication control information read from the header portion of the hard disk device HDD # 0 is expanded in the memory 122. (Step S128).

  On the other hand, if the hard disk device HDD # 1 is in a single HDD operation state (Yes in step S126, No in S127), the HDD duplication control information read from the header portion of the hard disk device HDD # 1 is expanded in the memory 122 ( Step S129).

  On the other hand, if such HDD unification operation is not performed, that is, if the HDD duplex operation is performed as usual (No in step S126), the HDD duplex control information read from the header portion of the hard disk device HDD # 0 is stored in the memory 122. (Step S130).

  Thus, in the first embodiment of the present invention, when the HDD duplication control information is read from the header part of the hard disk drives HDD # 0 and # 1 and expanded in the memory 122 in step S13 in FIG. 6 or step S53 in FIG. When reading from the header part of the device fails, when the failure of the partition # 0 storing the header part is recognized from the contents of the read header part, or when the HDD is in a single operation mode Then, the HDD duplication control information from the header part of the hard disk device on which reading is successful is expanded in the memory 122 (steps S108 to S111), and from the header part of the hard disk device on the side where partition # 0 has not failed. The HDD duplication control information is expanded in the memory 122 (step S122). S125), or to expand the HDD duplication control information from the header portion of the side of the hard disk drive in operation into the memory 122 (step S127~S129).

  As a result, it is possible to develop more reliable HDD duplication control information in the memory 122.

  14, 15, and 16, the initialization process (steps S <b> 16 and S <b> 6 in FIG. 6 or steps S <b> 56 and S <b> 6 in FIG. 8) or regular HDD duplexing status check process every week (FIG. 7). The details of middle steps S28, S5; S33, S5, steps S60, S5 in FIG. 8, steps S83, S5 in FIG. 9 will be described.

  First, the initialization task 23 is started by the kernel 10 at the time of initialization processing, and the HDD duplex state check processing is executed (step S141 in FIG. 14).

  Similarly, in the regular HDD duplication status check process for each week, the patrol task 24 is activated by the kernel 10, and the HDD duplication status check process is also executed (step S151 in FIG. 15).

  FIG. 16 shows a flow of the HDD duplex status check process executed in each of these steps S141 and S151.

  In FIG. 16, first, the HDD duplication control information 31a developed in the memory 122 is referred to (step S161). At this time, # 0 (that is, HDD # 0) is set as the number of the hard disk device to be referred to (step S162).

  If the hard disk device other than the set hard disk device HDD # 0, that is, the hard disk device HDD # 1, is in a single HDD operation state (Yes in step S163), the failure of the hard disk device HDD # 0 is indicated as a kernel. 10 (step S164).

  On the other hand, if it is not in the HDD single operation state, that is, if it is the HDD dual operation as usual (No in step S163), the partition number to be referred to is set to # 0 (step S165). If a failure is recorded for the partition in the HDD duplication control information 31a ("failure" in step S166), the fact is notified to the kernel 10 (step S167).

  Then, the partition number to be referred to is incremented by 1 (step S169), it is determined whether or not all the partitions have been checked (step S169), and the check is sequentially completed until all the partitions are checked (“complete” in step S169). The partition number to be updated is incremented (step S168), and the presence or absence of failure recording is checked for each partition (step S166). When there is a failure, the fact is notified to the kernel 10 each time (step S167).

  When all partitions are checked in this way (“complete” in step S169), the number of the hard disk device to be checked is incremented by 1 (step S170), and the same check is performed for the other hard disk device, that is, HDD # 1. Further, a failure notification is made to the kernel 10 as necessary (steps S163 to S169).

  Next, with reference to FIGS. 17 to 18, the details of the flow of the active replacement process of the failed hard disk drive after step S66 in FIG. 9 will be described.

  In step S181 in FIG. 17, the maintenance function 21b refers to the HDD duplication control information 31a developed in the memory 122, and displays the contents on the screen provided on the maintenance terminal 202 to the maintenance staff ( Step S182).

  On the other hand, when the maintenance staff performs an operation for instructing the disconnection of the failed hard disk device on the maintenance terminal 202 (step S183), the failed hard disk device is disconnected from the SVP 100 by the function of the HDD duplication control unit 31, and the completion of the HDD duplication is completed. The maintenance function 21b is notified through the control unit.

  In response to this, the maintenance function 21b updates the HDD duplication control information on the header part and the memory of the hard disk device that is in operation, in accordance with the fact that the HDD single operation state has been achieved by the above operation (step S184).

  The maintenance function 21b prompts maintenance personnel to replace the failed hard disk device on the screen of the maintenance terminal 202 (step S185).

  Next, in FIG. 18, when the maintenance staff performs replacement work for the failed hard disk device and instructs connection to the new hard disk device after replacement, the maintenance function 21 b receives the new hard disk related to the replacement via the HDD duplication control unit 31. An operation of connecting the device to the SVP 100 is performed (step S187), and the HDD duplexing control information on the header of the hard disk device in operation and the memory are updated to indicate that the HDD duplexing restoration is in progress (step S188).

  Then, it is maintained that the operation for restoring the original HDD duplex state is started by copying the stored information from the currently operating hard disk device to the new hard disk device to be replaced via the HDD duplex control unit 31. Is displayed on the screen of the service terminal 202 (step S189).

  Thereafter, an operation for restoring the original HDD duplex state is sequentially performed by copying the stored information from the currently operating hard disk device to the new hard disk device related to the replacement (step S190). At that time, the progress of the copy operation of the stored information is displayed on the screen of the maintenance terminal 202 (step S191).

  When the copy operation of the stored information is completed for all the partitions, the maintenance function 21b is in the HDD duplex state via the HDD duplex control unit 31, so that the HDD duplex control information on the header part of the hard disk device in operation and the memory is in effect. Is updated (step S192).

  Then, on the screen of the maintenance terminal 202, the fact that the active replacement work of the failed hard disk device has been completed is displayed (step S193).

  When maintenance is performed while the user operation is stopped, the SVP console 101 can be set in the maintenance mode, and the failed part can be replaced by a similar operation.

  The configuration of the second embodiment of the present invention will be described below.

  The second embodiment has the same configuration and function as the first embodiment described above, and the difference from the first embodiment is that a case where three or more hard disk devices are made redundant is assumed instead of two. .

  Only the contents relating to this difference will be described below, and other overlapping description will be omitted.

  In this case, (1) as a configuration of the redundant hard disk device, all the hard disk devices are divided into the same configuration as in the first embodiment, and the same data is stored in the area at the same position of each hard disk device.

  Similarly to the first embodiment, an area allocated at the same position in all hard disk devices is called a partition and is a unit for redundancy control.

  Each partition is redundantly held by one master hard disk device and one or more slave hard disk devices.

  (2) As HDD redundancy control information corresponding to the HDD duplication control information 31a, identification numbers corresponding to mounting positions are sequentially assigned to the plurality of hard disk devices from # 0.

  The plurality of partitions are assigned identification numbers from # 0 in the order of addresses in the hard disk device.

  The HDD redundancy control information is composed of a data table corresponding to the partition number.

  Each table shows the number of the master hard disk device that owns the partition and the number of the failed hard disk device that owns the partition. Here, the redundancy control information is stored in partition # 0.

  The HDD redundancy control information is expanded from the hard disk device to the SVP memory when the computer system is turned on, and the HDD redundancy state at the previous operation is taken over.

  When the status of the redundant hard disk device changes during operation, the HDD redundancy control information of partition # 0 in the hard disk device is updated simultaneously with the update of the HDD redundancy control information on the memory.

  (3) In the writing process to the hard disk device by the HDD redundancy control unit corresponding to the HDD duplication control unit 31 in the first embodiment, the same data is written in the areas of all the hard disk devices having each partition.

  In the read processing from the hard disk device, data is read from the area of the master hard disk device having the partition.

  When an error occurs in the writing process, the master hard disk device or slave hard disk device having the corresponding partition is recognized as a failure state.

  When an error occurs in the reading process, the master hard disk device having the corresponding partition is recognized as a failure state.

  When a master hard disk device having a corresponding partition fails in these read or write processes, an arbitrary hard disk device that has the partition and that has not failed is assigned as a master hard disk device for the partition.

  (4) In the hard disk device failure notification processing by the HDD redundancy control unit, if more than a prescribed number of master hard disk devices or slave hard disk devices having each partition fail, a minor failure (ie, partition It is determined that redundancy has occurred.

  When a minor failure (disruption of partition redundancy) of the hard disk device is detected, the maintenance staff is notified of the minor failure.

  (5) A patrol task (corresponding to the patrol task 25 of the first embodiment) having a function for periodically monitoring hard disk device failure is periodically started to monitor the presence or absence of a minor failure (partition redundancy failure) of the hard disk device. The

  If a minor failure is detected in this process, the maintenance staff is notified again of the minor failure. Further, every time a certain period of time elapses, the presence or absence of a minor failure of the hard disk device is checked, and until the redundancy state of the original hard disk device is restored, a notification to the maintenance staff that the minor failure has occurred is repeated.

  (6) In the hard disk device failure detection processing by the initialization processing, when the maintenance staff resumes the operation after stopping the operation of the SVP, a minor failure of the hard disk device (partition redundancy failure) is detected.

  If a minor failure of the hard disk device is detected in this process, the maintenance staff is notified again of the minor failure.

  As described above, according to the second embodiment of the present invention, when storing information is made redundant by a plurality of hard disk devices, that is, by storing information of the same contents in a plurality of hard disk devices, respectively, Even if the stored information of one or more hard disk devices (less than the total number of hard disk devices related to redundancy) is damaged, the same information is stored in the remaining hard disk devices, so the stored information is safe. If it is determined that the information stored in one or more predetermined number of hard disk devices, which is less than the total number of hard disk devices related to the redundancy, is damaged, the maintenance personnel are automatically notified of this. In addition, the notification is made every time the SVP is activated, and further every fixed period during operation.

  As a result, even if the maintenance staff did not respond by replacing the failed hard disk device at the time of the first minor failure notification, every time the SVP is started up, and even during operation, a certain period of time Since the same notification is automatically sent to the maintenance staff every time, the situation where the redundancy state is impaired, that is, the state where the so-called redundancy failure state is left for a long period of time can be effectively avoided. .

The present invention can take the configurations described in the following supplementary notes.
(Appendix 1)
An information storage device control method comprising:
The information stored in the information storage device is made redundant,
When a failure occurs in maintaining the redundant state of the information, the redundant failure recording unit records the redundancy failure in the state recording unit,
The redundancy monitoring means reads a record of redundancy failure from the state recording means,
A method for controlling an information storage device, comprising: each step in which a reporting unit reports a message to the effect when the redundancy monitoring unit reads a record to the effect of the redundancy failure.
(Appendix 2)
When a failure occurs in maintaining the redundant state of the information, a storage element to which a copy of the information is written is obtained in order to realize the redundancy of the information due to a failure of the storage element included in the information storage device. The control method of the information storage device according to appendix 1, which is formed when the information is lost.
(Appendix 3)
The method of controlling an information storage device according to appendix 1, wherein the step of reading out the redundancy failure from the state recording unit by the redundancy monitoring unit is periodically executed.
(Appendix 4)
The information storage device control method according to appendix 1, wherein the step of reading the redundancy failure from the status recording unit by the redundancy monitoring unit is executed when the information storage device is activated.
(Appendix 5)
An information storage device,
The information stored in the information storage device is made redundant,
Status recording means for recording information relating to the redundancy status;
When a failure occurs in maintaining the redundant state of the information, a redundant failure recording unit that records the redundancy failure in the state recording unit;
Redundancy monitoring means for reading a record of redundancy failure from the state recording means;
An information storage device comprising: reporting means for reporting that the redundancy failure is read by the redundancy monitoring means.
(Appendix 6)
When a failure occurs in maintaining the redundant state of the information, a storage element to which a copy of the information is written is obtained in order to realize the redundancy of the information due to a failure of the storage element included in the information storage device. The information storage device according to appendix 5, which is formed when no longer exists.
(Appendix 7)
The information storage device according to appendix 5, wherein the redundancy monitoring unit periodically reads out a redundancy failure from the state recording unit.
(Appendix 8)
The information storage device according to appendix 5, wherein the redundancy monitoring unit reads out the redundancy failure from the state recording unit when the information storage device is activated.
(Appendix 9)
A program for controlling an information storage device,
The information stored in the information storage device is made redundant,
A redundancy failure recording means for recording a state of the redundancy failure in the state recording means when a failure occurs in maintaining the state in which the information is made redundant, the computer for controlling the information storage device;
Redundancy monitoring means for reading a record of redundancy failure from the state recording means; and
A program including an instruction for functioning as a reporting unit that reports to the effect that a redundancy failure is read by the redundancy monitoring unit.
(Appendix 10)
When a failure occurs in maintaining the redundant state of the information, a storage element to which a copy of the information is written is obtained in order to realize the redundancy of the information due to a failure of the storage element included in the information storage device. The program according to appendix 9, which consists of a case where it disappears.
(Appendix 11)
The program according to appendix 9, wherein the redundancy monitoring unit periodically reads out a redundancy failure from the state recording unit.
(Appendix 12)
The program according to appendix 9, wherein the redundancy monitoring unit reads out a redundancy failure from the state recording unit when the information storage device is activated.
(Appendix 13)
A computer-readable information recording medium storing the program according to any one of appendices 9 to 12.

It is a block diagram for demonstrating the control method of an example of the conventional information storage device. It is a block diagram for demonstrating the hardware constitutions of the computer which has a function which implements the control method of the information storage device by one Example of this invention. It is a block diagram for demonstrating the structure of the program for making a computer perform the control method of the information storage device by one Example of this invention. It is a block diagram for demonstrating the control method of the information storage device by one Example of this invention. FIG. 5 is a diagram for explaining an example of HDD duplication control information in FIG. 4. It is a flowchart (the 1) for demonstrating the flow of operation | movement of the control method of the information storage device by one Example of this invention. It is a flowchart (the 2) for demonstrating the flow of operation | movement of the control method of the information storage device by one Example of this invention. It is a flowchart (the 3) for demonstrating the flow of operation | movement of the control method of the information storage device by one Example of this invention. It is a flowchart (the 4) for demonstrating the flow of operation | movement of the control method of the information storage device by one Example of this invention. It is a flowchart (the 1) for demonstrating the flow of operation | movement of the expansion | deployment process of HDD duplication control information in the control method of the information storage device by one Example of this invention. It is a flowchart (the 2) for demonstrating the flow of operation | movement of the expansion | deployment process of HDD duplication control information in the control method of the information storage device by one Example of this invention. It is a flowchart (the 3) for demonstrating the flow of operation | movement of the expansion | deployment process of HDD duplication control information in the control method of the information storage device by one Example of this invention. It is a flowchart (the 4) for demonstrating the flow of operation | movement of the expansion | deployment process of HDD duplication control information in the control method of the information storage device by one Example of this invention. It is a flowchart for demonstrating the flow of operation | movement of the hard disk apparatus failure detection process at the time of initialization in the control method of the information storage device by one Example of this invention. It is a flowchart for demonstrating the flow of operation | movement of the periodic monitoring process of the hard disk drive failure in the control method of the information storage device by one Example of this invention. It is a flowchart for demonstrating the operation | movement of the neglected detection process of the hard disk apparatus failure in the control method of the information storage device by one Example of this invention. It is a flowchart (the 1) for demonstrating operation | movement of the hard disk drive duplication recovery process in the control method of the information storage device by one Example of this invention. It is a flowchart (the 2) for demonstrating the operation | movement of the hard disk drive duplication recovery process in the control method of the information storage device by one Example of this invention.

Explanation of symbols

10 Kernel 20 SVP Control Program 21 Frame Task 23 Initialization Task 24 Error Log Task 25 Patrol Task 30 Hard Disk Driver 31 HDD Duplication Control Unit 31a HDD Duplication Control Information 100 SVP
121 ROM
151,152 Hard Disk Device 200 Main Device

Claims (10)

An information storage device control method comprising:
The information stored in the information storage device is made redundant,
When a failure occurs in maintaining the redundant state of the information, the redundant failure recording unit records the redundancy failure in the state recording unit,
The redundancy monitoring means reads a record of redundancy failure from the state recording means,
A method for controlling an information storage device, comprising: each step in which a reporting unit reports a message to the effect when the redundancy monitoring unit reads a record to the effect of the redundancy failure.   When a failure occurs in maintaining the redundant state of the information, a storage element to which a copy of the information is written is obtained in order to realize the redundancy of the information due to a failure of the storage element included in the information storage device. The method of controlling an information storage device according to claim 1, comprising: a case where there is no more.   2. The method of controlling an information storage device according to claim 1, wherein the step of reading out the redundancy failure from the state recording unit by the redundancy monitoring unit is periodically executed.   2. The method of controlling an information storage device according to claim 1, wherein the step of reading out the redundancy failure from the status recording unit by the redundancy monitoring unit is executed when the information storage device is activated. An information storage device,
The information stored in the information storage device is made redundant,
Status recording means for recording information relating to the redundancy status;
When a failure occurs in maintaining the redundant state of the information, a redundant failure recording unit that records the redundancy failure in the state recording unit;
Redundancy monitoring means for reading a record of redundancy failure from the state recording means;
An information storage device comprising: reporting means for reporting that the redundancy failure is read by the redundancy monitoring means.   When a failure occurs in maintaining the redundant state of the information, a storage element to which a copy of the information is written is obtained in order to realize the redundancy of the information due to a failure of the storage element included in the information storage device. The information storage device according to claim 5, wherein the information storage device is configured to disappear.   The information storage device according to claim 5, wherein the redundancy monitoring unit is configured to periodically read a redundancy failure from the state recording unit.   6. The information storage device according to claim 5, wherein the redundancy monitoring unit is configured to read out a redundancy failure from the state recording unit when the information storage device is activated. A program for controlling an information storage device,
The information stored in the information storage device is made redundant,
A redundancy failure recording means for recording a state of the redundancy failure in the state recording means when a failure occurs in maintaining the state in which the information is made redundant, the computer for controlling the information storage device;
Redundancy monitoring means for reading a record of redundancy failure from the state recording means; and
A program including an instruction for functioning as a reporting unit that reports to the effect that a redundancy failure is read by the redundancy monitoring unit.   A computer-readable information recording medium storing the program according to claim 9.

Images