Patent Document

BACKGROUND OF THE INVENTION  
         [0001]    1. Field of the Invention  
           [0002]    The present invention relates to an information processing system in which computers are connected to respective disk devices.  
           [0003]    2. Description of Related Art  
           [0004]    In a conventional computer system, multiple computers were interconnected via a LAN or other network and disk devices were directly connected to the computers. The data stored in the disk devices were managed by the computers that were directly connected to them. In other words, the data were distributed for management purposes.  
           [0005]    Recently, however, there is an increase in the number of configurations in which multiple computers share a disk device, including a configuration for sharing input/output channels for virtual computing and computer logical sharing, a storage area network (hereinafter abbreviated to “SAN”), and a network attached storage (hereinafter abbreviated to “NAS”). These configurations offer the advantage of reducing the cost of disk devices as well as the cost of management, because they make it possible to integrate the data distributed to multiple disk devices for centralized management purposes.  
           [0006]    The operating system function called “Union File Mount”, which is stated on pages 235 through 237 of Addison Wesley&#39;s “The Design and Implementation of the 4.4BSD Operating System (1996)”, provides a means of partial sharing by saving the updates for a file system established on a disk device onto another disk device.  
           [0007]    All the above-mentioned conventional technologies provide a means of sharing user disks and a part of system disk, but do not permit the entire system disk to be shared. The reason is that individual computers have their own unique items such as a configuration file.  
           [0008]    When, for instance, a NAS or other network file system is used, flexible operations cannot be performed because there is no alternative but to define common and private parts in the unit of a directory and only partial sharing is achievable.  
           [0009]    The “Union File Mount” function, on the other hand, permits partial sharing. However, the function does not become available until the operating system is completely started up because it relates to the file system, which is an upper layer of the operating system. Therefore, it cannot be applied to the boot disk.  
           [0010]    In a system used at a data center or the like, where a large number of similarly configured computers operate, the contents of system disks are mostly the same but not perfectly the same. Therefore, the computers are provided with system disks that devote most of their spaces to the storage of the same information. That is why the device cost and management cost cannot easily be reduced.  
         SUMMARY OF THE INVENTION  
         [0011]    The object of the present invention is to let multiple computers share the common portions of system disk devices and other disk devices the contents of which are not perfectly the same, and offer a sharing function at a lower level of the operating system to permit boot disk sharing.  
           [0012]    In carrying out our invention in one preferred mode, we utilize an information processing system having: computers connected to their respective private disk devices, a common disk device commonly connected to the computers, a means for storing writes into said common disk device into said private disk devices to permit said computers to share the data in said common disk device, and a means for translating reads of said common disk device into reads of said private disk devices or said common disk device.  
           [0013]    Other and further objects, features and advantages of the invention will appear more fully from the following description.  
       
    
    
     BRIEF DESCRIPTION OF THE DRAWINGS  
       [0014]    [0014]FIG. 1 is a schematic diagram of a preferred embodiment of the present invention;  
         [0015]    [0015]FIG. 2 shows a virtual disk configuration image of a preferred embodiment of the present invention;  
         [0016]    [0016]FIG. 3 shows the private table structure of a preferred embodiment of the present invention;  
         [0017]    [0017]FIG. 4 shows a typical relationship between a private table and a virtual disk of a preferred embodiment of the present invention;  
         [0018]    [0018]FIG. 5 shows a read routine flowchart of a preferred embodiment of the present invention; and  
         [0019]    [0019]FIG. 6 shows a write routine flowchart of a preferred embodiment of the present invention. 
     
    
     DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS  
       [0020]    The embodiments of disk sharing in a virtual machine environment of the present invention are detailed below with reference to drawings.  
         [0021]    [0021]FIG. 1 is a schematic diagram of an information processing system of the present invention. A host computer  101  contains a virtual machine  110 , a common disk device  120 , and a private disk device  130 . The common disk device  120  is only one device within the host computer  101  and shared by multiple virtual machines. One unit of private disk device  130  is required for each virtual machine and used exclusively by a virtual machine. If a large number of virtual machines exist, multiple common disk devices can be furnished to prevent the performance from being degraded by common disk device access. A user program  111  and an operating system  112  operate within the virtual machine  110 . The operating system  112  controls the common disk device  120  and private disk device  130 , and provides the user program  111  with a file access function. There are a file system module  113 , a disk sharing module  114 , and a disk access module  117  within the operating system  112 . The file system module  113  translates file access requests from the user program  111  into block-specific inputs/outputs relative to disk devices and passes them to the disk sharing module  114 . The disk sharing module  114 , the software that is a feature of the present invention, offers a disk sharing function as it receives block-specific input/output requests from the file system module  113 , translates them into appropriate block-specific input/output requests for the common disk device  120  and private disk device  130 , and passes them to the disk access module  117 . (A typical preferred embodiment is such that the common disk device  120  is a system disk for storing the information common to individual computers whereas the private disk device  130  is a system disk for storing the information unique to a specific computer. Common data and private data can also be stored in the same manner for user disk management.) The disk access module  117  receives block-specific input/output requests from the disk sharing module  114 , controls the common disk device  120  and private disk device  130 , and processes block-specific physical inputs/outputs relative to the disk devices. The disk sharing module  114  consists of a read routine  115  and a write routine  116 . The read routine  115  translates the input portions of block-specific input/output requests to be translated by the disk sharing module  114 . The write routine  116  translates the output portions of block-specific input/output requests to be translated by the disk sharing module  114 . The common disk device  120  contains common blocks  121 . The common blocks  121  form an area for storing data that is common to multiple virtual machines. A private disk device  130  contains private blocks  131  and a private table  132 . The private blocks  131  form an area for storing data that is unique to a specific virtual machine. The private table  132  is an area for storing information that indicates what data in the common disk device  120  is replaced and where in a private disk device  130  the replaced data is stored.  
         [0022]    [0022]FIG. 2 shows how disks are shared when there are three units of virtual machines. The virtual machines share the common disk device  201  for read operations only. Virtual machine A  211 , virtual machine B  221 , and virtual machine C  231  exclusively use private disk device A  212 , private disk device B  222 , and private disk device C  232 , respectively, for read/write operations. Virtual disk A  213 , virtual disk B  223 , and virtual disk C  233  are virtual disk devices that are exclusively used by virtual machine A, virtual machine B, and virtual machine C, respectively. The virtual disks are visible to the virtual machines as if they really exist. The contents of the virtual disks are initially the same as those of the common disk device. The contents of the virtual disks can be updated by the virtual machines and the private disks store the updated portions.  
         [0023]    When the above configuration is used, only the contents of the common disk device  201 , and private disk devices A  212 , B  222 , and C  232  are to be backed up. There is no need to back up the entire contents of virtual disks A  213 , B  223 , and C  233 .  
         [0024]    [0024]FIG. 3 shows the structure of the private table and its typical use. The private table stores the information about the status of all private blocks. Column  310  indicates private block numbers. Column  320  shows validity flags, which indicate whether private blocks are used. Column  330  indicates common block numbers, which represent private block replacement destinations. For example, private block No. 0 is used for replacing common block No. 9 and private block No. 5 is not used.  
         [0025]    [0025]FIG. 4 shows a typical virtual disk configuration for private table use indicated in FIG. 3. This configuration example shows a common disk device  410 , a virtual disk  420 , and a private disk device  430 . The contents of the virtual disk  420  are nearly the same as those of the common disk device  410 . However, the contents of blocks No. 9 through 11 are replaced by the contents of private blocks No. 0 through 2 of the private disk device  430 , and the contents of blocks No. 45 and 46 are replaced by the contents of private blocks No. 3 and 4 of the private disk device  430 .  
         [0026]    [0026]FIG. 5 shows a read routine flowchart. In step  501 , block number A is acquired as the input target. Block number A is designated by a caller. In step  502 , the disk access module  117  is called. As a result of this call, a private table  132  is read from a private disk device  130 . In step  503 , the private table  132  is searched. This search is conducted to determine whether input target block A is replaced. More specifically, all entries in the private table  132  are checked. If an entry is found to have a validity flag value of  1  and a common block number of A, it means that block A is replaced. In step  504 , a branch occurs in accordance with the judgment result. The program branches to step  511  when block A is replaced. If not, the program branches to step  521 . In step  511 , private block B is acquired. The block number of private block B is the private block number of an entry that was retrieved by a search in step  503 . In step  512 , the disk access module  117  is called. As a result of this call, data is read from block B of the private disk device  130 . In step  521 , the disk access module  117  is called. As a result of this call, data is read from block A of the common disk device  120 .  
         [0027]    [0027]FIG. 6 shows a write routine flowchart. In step  601 , block number A is acquired as the output target. Block number A is designated by a caller. In step  602 , the disk access module  117  is called. As a result of this call, a private table  132  is read from a private disk device  130 . In step  603 , the private table  132  is searched. This search is conducted to determine whether output target block A is replaced. More specifically, all entries in the private table  132  are checked. If an entry is found to have a validity flag value of 1 and a common block number of A, it means that block A is replaced. In step  604 , a branch occurs in accordance with the judgment result. The program branches to step  611  when block A is replaced. If not, the program branches to step  621 . In step  611 , private block B is acquired. The block number of private block B is the private block number of an entry that was retrieved by a search in step  603 . In step  612 , the disk access module  117  is called. As a result of this call, data is written into block B of the private disk device  130 . In step  621 , the private table  132  is searched. As a result of this search, unused private block C is acquired. More specifically, all entries in the private table  132  are checked to acquire private block number C of the first entry that is found to have a validity flag value of 1. In step  622 , the private table  132  is updated. New private block C is registered by this update. More specifically, the entries having a private block number of C in the private table  132  are set to a validity flag value of 1 and a common block number of A, and then the disk access module  117  is called to reflect the results in the private table within the private disk device. In step  623 , the disk access module  117  is called. As a result of this call, data is written into block C of the private disk device  130 .  
         [0028]    In the preferred embodiment, data is shared when the disk devices are shared by multiple virtual machines on a host computer. However, the present invention is also applicable to situations where the disk devices are shared by multiple host computers.  
         [0029]    In the preferred embodiment, the private disk devices are separate from the common disk device. However, the present invention is also applicable to situations where these disk devices virtually exist on volumes that are obtained by logically dividing a physical disk device.  
         [0030]    In the preferred embodiment, virtual machines and disk devices are used to implement the present invention within the software on the virtual machines. However, the present invention is also applicable to the control software in a NAS or network file server when the NAS or network file server is used instead of a disk device.  
         [0031]    In the preferred embodiment, normal disk devices are used to implement the present invention within the software on virtual machines. However, the present invention is also applicable to situations where disk devices that run control software on a processor and memory they have.  
         [0032]    In another preferred embodiment, a single computer that is connected to one or more of the above private disk devices, furnished with one or more network connections, and provided with a read routine, a write routine, and disk access module can be used instead of multiple computers mentioned above. In another preferred embodiment, a single computer that is connected to one or more of the above private disk devices, furnished with one or more channels for connecting itself to the other computers as a disk device, and provided with a read routine, a write routine, and disk access module can be used instead of multiple computers mentioned above.  
         [0033]    As explained above, the preferred embodiments permit a part of a disk to be shared by multiple computers so as to reduce the cost of hardware. Further, the present invention does not duplicate common data when they store in files. As a result, the amount of data to be backed up decreases, thereby reducing the time required for backup and the cost of operations. When the present invention is applied to system disks, their common portions can be shared to reduce the required capacity and provide increased ease of management.  
         [0034]    According to the present invention, disks can be partly shared no matter whether they are system disks or user disks.  
         [0035]    The foregoing invention has been described in terms of preferred embodiments. However, those skilled, in the art will recognize that many variations of such embodiments exist. Such variations are intended to be within the scope of the present invention and the appended claims.

Technology Category: 3