1. Field of the Invention
This invention relates generally to visual status displays and control interfaces for computer hardware, and in more specific embodiments, to displaying and modifying the status of one or more drives in a RAID array.
2. Background Art
There are many applications, particularly in a business environment, where there are needs beyond those that can be fulfilled by a single hard disk, regardless of its size, performance or quality level. Many businesses can't afford to have their systems go down for even an hour in the event of a disk failure. They need large storage subsystems with capacities in the terabytes. And they want to be able to insulate themselves from hardware failures to any extent possible. Some people working with multimedia files need fast data transfer exceeding what current drives can deliver, without spending a fortune on specialty drives. These situations require that the traditional “one hard disk per system” model be set aside and a new system employed. This technique is called Redundant Arrays of Inexpensive Disks or RAID. (“Inexpensive” is sometimes replaced with “Independent”, but the former term is the one that was used when the term “RAID” was first coined by the researchers at the University of California at Berkeley, who first investigated the use of multiple-drive arrays in 1987. See D. Patterson, G. Gibson, and R. Katz. “A Case for Redundant Array of Inexpensive Disks (RAID)”, Proceedings of ACM SIGMOD '88, pages 109-116, June 1988.
The fundamental structure of a RAID is the array. An array is a collection of drives that is configured, formatted and managed in a particular way. The number of drives in the array, and the way that data is split between them, is what determines the RAID level, the capacity of the array, and its overall performance and data protection characteristics.
A number of RAID levels are known. JBOD stands for Just a Bunch of Drives. The controller treats one or more disks or unused space on a disk as a single array. JBOD provides the ability to concatenate storage from various drives regardless of the size of the space on those drives. JBOD is useful in scavenging space on drives unused by other arrays. JBOD does not provide any performance or data redundancy benefits.
RAID0, or striping, provides the highest performance but no data redundancy. Data in the array is striped (i.e. distributed) across several physical drives. RAID0 arrays are useful for holding information such as the operating system paging file where performance is extremely important but redundancy is not.
RAID1, or mirroring, mirrors the data stored in one physical drive to another. RAID1 is useful when there are only a small number of drives available and data integrity is more important than storage capacity.
RAID1n, or n-way mirroring, mirrors the data stored in one hard drive to several hard drives. This array type will provide superior data redundancy because there will be three or more copies of the data and this type is useful when creating backup copies of an array. This array type is however expensive, in both performance and the amount of disk space necessary to create the array type.
RAID10 is also known as RAID(0+1) or striped mirror sets. This array type combines mirrors and stripe sets. RAID10 allows multiple drive failures, up to 1 failure in each mirror that has been striped. This array type offers better performance than a simple mirror because of the extra drives. RAID10 requires twice the disk space of RAID0 in order to offer redundancy.
RAID10n stripes multiple n-way mirror sets. RAID10n allows multiple drive failures per mirror set, up to n−1 failures in each mirror set that has been striped, where n is the number of drives in each mirror set. This array type offers better random read performance than a RAID10 array, but uses more disk space.
RAID5, also known as a stripe with parity, stripes data as well as parity across all drives in the array. Parity information is interspersed across the drive array. In the event of a failure, the controller can rebuild the lost data of the failed drive from the other surviving drives. This array type offers exceptional read performance as well as redundancy. In general, write performance is not an issue due to the tendency of operating systems to perform many more reads than writes. This array type requires only one extra disk to offer redundancy. For most systems with four or more disks, this is the correct choice as array type.
RAID50 is also known as striped RAID5 sets. Parity information is interspersed across each RAID5 set in the array. This array type offers good read performance as well as redundancy. A 6-drive array will provide the user with 2 striped 3-drive RAID5 sets. Generally, RAID50 is useful in very large arrays with 10 or more drives.
If a disk drive or multiple disk drives are connected to and controlled by a RAID controller, then they are collectively referred to as a “RAID array”. A disk drive previously configured by the operating system of a computing device and then connected to a RAID controller is referred to as a “legacy drive”. After the legacy drive is configured by the RAID controller its is referred to as a “legacy array”. If a new drive which was not configured by the RAID controller or the OS is attached to the RAID controller, then the drive is referred to as an “un-initialized drive”. The drive is converted into an initialized RAID drive after the RAID controller writes its unique configuration data to that disk.
Thus RAID or Redundant Array of Independent Disks are simply several disks that are grouped together in various organizations to either improve the performance or the reliability of a computer's storage system. These disks are grouped and organized by a RAID controller. The user interacts with RAID controller software to configure disks and their RAID levels in the RAID array. The arrays can be configured to any of the RAID levels RAID 0, RAID 5, RAID 1 etc. as mentioned above.
Besides RAID arrays, computer systems have multiple hardware elements such as motherboard, audio and video cards, memory chips etc. If one of these elements fails and needs to be replaced or needs maintenance, firstly, the user may not be aware of the faulty status of that hardware element and secondly, the user may have difficulty identifying the responsible hardware element amongst other hardware elements present in the system.
There is a need for improvement in communicating status and fault information for hardware elements in a computer system to persons who use and maintain the computer system.
Additional features and advantages of the invention will be set forth in the description that follows, and in part will be apparent from the description, or may be learned by practice of the invention.
In preferred embodiments, the invention comprises a method and related computer program product for operating a computer system which comprises acquiring a digital image of a hardware element, storing the digital image, and displaying the image in a software program. The display preferably provides hardware status information in connection with the digital image, dynamically updates and displays the hardware status information, and allows the user to dynamically control the hardware element's operation by interacting with the displayed image.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory and are intended to provide further explanation of the invention as claimed. The description herein is not intended to limit the scope of the claimed invention in any way.
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description serve to explain the principles of the invention. In the drawings:
The present invention will now be described with reference to the accompanying drawings. In the drawings, like reference numbers may indicate identical or functionally similar elements. Additionally, the left-most digit(s) of a reference number may identify the drawing in which the reference number first appears.
While the present invention is described herein with reference to illustrative embodiments for particular applications, it should be understood that the invention is not limited thereto. Those skilled in the art with access to the teachings provided herein will recognize additional modifications, applications, and embodiments within the scope thereof and additional fields in which the invention would be of significant utility.
The present invention will be described in terms of an embodiment applicable to the display of status information relating to one or more computer disk drives, and in particular, a RAID array, and to the interactive control of those hardware elements through a visual display. It will be understood that the essential display and control concepts disclosed herein are applicable to a wide range of electronic systems, architectures and hardware elements. Thus, although the invention will be disclosed and described in terms of providing RAID status and control functions, the invention is not limited to this field.
A conventional RAID controller can manage many disk drives and large databases have multiple RAID controllers resulting in a large number of disk drives. The inventor has identified a number of problems with traditional control software for these RAID controllers. In conventional designs there may or may not be a visual display of the hardware configuration, and there is no visual mapping between the physical RAID configuration and the logical RAID configuration shown by the RAID software. For example, assume that the RAID software is used to configure four disks as a RAID level 10 array, and three disks as a RAID level 5 array. In the event that the third disk belonging to RAID level 10 undergoes failure or needs maintenance, it is difficult to visually identify the location of the responsible physical hard drive in the system. This is because in the physical RAID configuration the drives may not be arranged in the same order as their logical configuration in the RAID software. Thus, users may need to know how their disks are organized, both in the RAID software and in their corresponding physical location. In cases where there is more than one logical array, the user also needs to know which physical disks are associated with which RAID arrays in software and be able to identify the physical disks by visually inspecting the RAID configuration in software. The user may also not be aware of a faulty drive in the array and needs a software indicator to identify the responsible drive. Some storage systems provide a fixed set of supported physical configurations and a fixed mapping between software RAID configurations and the physical RAID configurations. However, this method does not provide the user with any flexibility to modify the physical or software RAID configuration.
A general-purpose RAID controller can be used in an unlimited number of environments. A typical RAID controller has no fixed physical or software RAID array configurations. In a first embodiment of the present invention, the user may store an actual digital image of hardware elements (e.g. disks in a RAID array), configure control and/or status display software to use that image of hardware elements, and then configure status information for the hardware elements to be displayed proximate to the uploaded image. In one preferred embodiment, status information for each hardware element, for example a disk, is overlaid on the digital image of those disks and the information is updated dynamically as system status changes. In this manner, the user is provided with a visual display of current status information for each drive in the array. The user can also interact with the displayed information to control the array. In particular, the user can click on regions in the display, such as a status information region proximate to a hardware element, and select functions from a menu displayed in response to the click, to provide control inputs for the hardware elements and the array.
If the RAID configuration needs to be modified by removing a physical disk, changing the physical position of a disk or replacing a disk, it is desirable for the user to know the physical location of the disk and its associated RAID level configuration in software. In addition, if one of the disks in the array undergoes failure or needs maintenance, it is desirable for RAID controller software 108 to provide an indication of the failure or maintenance requirement. After identifying a drive with reference to software 108, the user should be able to identify a corresponding disk in the physical layout of the RAID array. Although the examples presented herein have four drives in the array for simplicity, many computer systems contain a larger number of drives. With the logistics of managing a large number of drives, it becomes difficult for the user to identify which disks in the physical RAID array configuration belong to which RAID level configuration in software. The user should be able to identify which disks in the physical array correspond to disk drives in software.
In a preferred embodiment, a status display configuration mode is provided by RAID controller software 108, and in this mode the user can load one or more hardware images, re-position status information boxes, and change the image to correspond to any changes in the physical or software RAID configuration. Thus, the user can configure each status information box 300, 302, 304 and 306 and then drag and drop the box to a suitable position associated with the corresponding disk drive. In the present embodiment, the status information for each disk in the array displays the RAID level that the drive belongs to e.g. RAID 0, RAID 1 etc., along with the drive number for that RAID level configuration. In the example above, D1 is the first drive in a RAID level 5 array and D4 is the second drive in a RAID level 1 array. The status information for D1, since it belongs to the RAID level 5 array and is the first disk in that array, will be displayed as 5:0 in status information box 300. Similarly for D4 which belongs to a RAID level 1 and is the second disk in the RAID level 1 array, the status information is displayed as 1:1 in status information box 306. These status information displays are described as examples and are not intended to be exhaustive; a variety of status displays other than displaying the RAID level and the drive number for that RAID level configuration are possible within the scope of the invention. In particular, in other embodiments, the status information can be configured to display any information available to the RAID controller software about a disk in the RAID array.
Besides viewing the disk status information for all the disks in the array, the status information boxes can also be used to control operation and/or modify the status of each disk in the array. In a preferred embodiment, by right clicking on the status information box 300, the user causes display of a menu that allows the user to select from among various status control functions relating to disk D1. For example, disk D1 can be assigned as a dedicated spare or as a global spare, made accessible to the operating system, or hidden from the operating system. The status information boxes can also be used to activate light emitting diodes (LEDs) on disk enclosures and/or on RAID controllers associated with the array, as will be discussed in detail later in the application. The functions that can be accessed by clicking on the status information box are not limited to the examples given herein, but can include control of any hardware, software or configuration attribute that can be set through the RAID controller software.
As explained in the embodiments above, in this example the foreground text indicates the RAID level the drive belongs to along with the drive number for that particular configuration. Black foreground text is used to indicate a normally functioning drive and red foreground text is used to indicate a malfunctioning or failed drive. In this example, if the first drive in the RAID level 5 array (i.e. D1) undergoes failure, the status information (i.e. 5:0) will be displayed in red. The key 422 helps the user associate the background and foreground text colors with the currently displayed drive status colors. It is noted that the choice of color and information displayed is arbitrary and can be modified by a person skilled in the relevant art(s) within the scope of the invention. The embodiments use a box to display the overlaid status information, however, the geometric shape, if any, used to display the status information is arbitrary and can also be modified.
If a drive in the array undergoes failure or needs maintenance, the status information box in RAID controller software 108 preferably indicates the condition of the drive by changing the relevant background or foreground color.
The embodiments presented above are related to RAID controllers and RAID arrays, but it will be apparent to a person skilled in the relevant art(s) that the invention encompasses displaying an image of any hardware element and using that displayed image to indicate and/or control the status of the corresponding hardware element. Since the user can tailor the software view either by moving the overlaid status information or by moving individual images, an unlimited number of configurations can be achieved for any physical layout of hardware elements based on user preference.
The following description of a general-purpose computer system is provided for completeness. The present invention can be implemented in hardware or as a combination of software and hardware. Consequently, the invention may be implemented in the environment of a computer system or other processing system. An example of such a computer system 1000 is shown in
Computer system 1000 also includes a main memory 1005, preferably random access memory (RAM), and may also include a secondary memory 1010. The secondary memory 1010 may include, for example, a hard disk drive 1012, and/or a RAID array 1016, and/or a removable storage drive 1014, representing a floppy disk drive, a magnetic tape drive, an optical disk drive, etc. The removable storage drive 1014 reads from and/or writes to a removable storage unit 1018 in a well known manner. Removable storage unit 1018, represents a floppy disk, magnetic tape, optical disk, etc. As will be appreciated, the removable storage unit 1018 includes a computer usable storage medium having stored therein computer software and/or data.
In alternative implementations, secondary memory 1010 may include other similar means for allowing computer programs or other instructions to be loaded into computer system 1000. Such means may include, for example, a removable storage unit 1022 and an interface 1020. Examples of such means may include a program cartridge and cartridge interface (such as that found in video game devices), a removable memory chip (such as an EPROM, or PROM) and associated socket, and other removable storage units 1022 and interfaces 1020 which allow software and data to be transferred from the removable storage unit 1022 to computer system 1000.
Computer system 1000 may also include a communications interface 1024. Communications interface 1024 allows software and data to be transferred between computer system 1000 and external devices. Examples of communications interface 1024 may include a modem, a network interface (such as an Ethernet card), a communications port, a PCMCIA slot and card, etc. Software and data transferred via communications interface 1024 are in the form of signals 1028 which may be electronic, electromagnetic, optical or other signals capable of being received by communications interface 1024. These signals 1028 are provided to communications interface 1024 via a communications path 1026. Communications path 1026 carries signals 1028 and may be implemented using wire or cable, fiber optics, a phone line, a cellular phone link, an RF link and other communications channels.
The terms “computer program medium” and “computer usable medium” are used herein to generally refer to media such as removable storage drive 1014, a hard disk installed in a disk drive enclosure 1012, and remotely located media accessed through a communications interface. These computer program products are means for providing software to computer system 1000.
Computer programs (also called computer control logic) are stored in main memory 1008 and/or secondary memory 1010. Computer programs may also be received via communications interface 1024. Such computer programs, when executed, enable the computer system 1000 to implement the present invention as discussed herein. In particular, the computer programs, when executed, enable the processor 1004 to implement the processes of the present invention. Where the invention is implemented using software, the software may be stored in a computer program product and loaded into computer system 1000 using raid array 1016, removable storage drive 1014, hard drive 1012 or communications interface 1024.
In another embodiment, features of the invention are implemented primarily in hardware using, for example, hardware components such as Application Specific Integrated Circuits (ASICs) and gate arrays. Implementation of a hardware state machine so as to perform the functions described herein will also be apparent to persons skilled in the relevant art(s).
While various embodiments of the present invention have been described above, it should be understood that they have been presented by way of example, and not limitation. It will be apparent to persons skilled in the relevant art that various changes in form and detail can be made therein without departing from the spirit and scope of the invention.
The present invention has been described above with the aid of functional building blocks and method steps illustrating the performance of specified functions and relationships thereof. The boundaries of these functional building blocks and method steps have been arbitrarily defined herein for the convenience of the description. Alternate boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed. Any such alternate boundaries are thus within the scope and spirit of the claimed invention. One skilled in the art will recognize that these functional building blocks can be implemented by discrete components, application specific integrated circuits, processors executing appropriate software and the like or any combination thereof. Thus, the breadth and scope of the present invention should not be limited by any of the above-described exemplary embodiments, but should be defined only in accordance with the following claims and their equivalents.