Storage management system having common volume manager

[0002] This application is related to the following applications, all of which are filed on the same day and assigned to the same assignee as the present application:

[0003] “Quorum Resource Arbitrator Within A Storage Network”—Ser. No. 09/449,579, filed Nov. 29, 1999,

[0004] “Storage Management System Having Abstracted Volume Providers”—Ser. No. 09/450,364, filed Nov. 29, 1999,

[0005] “Volume Stacking Model”—Ser. No. 09/451,219, filed Nov. 29, 1999,

[0006] “Volume Configuration Data Administration”—Ser. No. 09/450,300, filed Nov. 29, 1999, now U.S. Pat. No. 6,553,387, and

[0007] “Volume Migration Between Volume Groups”—Ser. No. 09/451,220, filed Nov. 29, 1999.

[0008] This invention relates generally to data storage, and more particularly to providing an administrator for logical volumes within a storage network.

[0009] A portion of the disclosure of this patent document contains material that is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever. The following notice applies to the software and data as described below and in the drawing hereto: Copyright© 1999, Microsoft Corporation, All Rights Reserved.

[0010] As computer systems have evolved so has the availability and configuration of data storage devices, such as magnetic or optical disks. For example, these storage devices can be connected to the computer system via a bus, or they can be connected to the computer system via a wired or wireless network. In addition, the storage devices can be separate or co-located in a single cabinet.

[0011] A storage volume is a software abstraction of the underlying storage devices and is the smallest self-contained unit of storage mounted by an operating system and administered by a file system. Storage volumes abstract the physical topology of the storage devices and may be a fraction of a disk, a whole disk or even multiple disks that are bound into a virtually contiguous range of logical blocks. This binding may increase the fault tolerance, performance, or capacity characteristics of the underlying storage devices.

[0012] One technique for improving fault tolerance, known as mirroring or plexing a disk, uses multiple disks. When data is written to one disk the data is also written to a second disk; thus the second disk is a “mirror image” of the first disk. If one disk should fail the second disk is still available for use and has an exact copy of the information on the first disk.

[0013] Volumes are constructed from one or more extents that are contiguous storage address spaces presented by the underlying storage devices. An extent is typically characterized by the size of the address space and a starting offset for the address space from a base of the media. Volume mapping is the process of mapping the contiguous address space presented by the volume onto the non-contiguous storage address spaces of the underlying extents. Volume mappings are either implemented on a specialized hardware controller, referred to as a hardware volume provider, or in software by a software volume provider.

[0014] Conventional volume providers are configured and managed with unique, vendor-specific tools. Each provider typically uses a proprietary protocol for communicating between the storage device and the driver. These unique applications make it difficult for an administrator to manage a system having multiple storage devices. For example, consider two RAID storage cabinets from different vendors that are combined to form a single, striped volume. A first vendor-specific volume management tool is often required to configure the disks within the first RAID cabinet while a completely different tool is required to configure the disks within the second cabinet. In addition, a third tool is required to combine the two storage cabinets to form a volume. Therefore, there is a need in the art for a mechanism for uniformly configuring and coordinating multiple volume providers.

[0015] The above-mentioned shortcomings, disadvantages and problems are addressed by the present invention. In one aspect, the invention is a storage management system in which a plurality of volume providers map logical storage volumes onto one or more storage devices of a storage network. A common volume manager executing on a computer within the storage network selectively communicates commands to one or more of the volume providers in order to control the storage devices. In this manner, the inventive storage management system seamlessly integrates management of multiple volume providers. The common volume manager provides a common application programming interface (API) by which applications are able to control and monitor hardware and software volume providers without requiring detailed knowledge of the volume providers or the underlying storage devices. The interface is extensible so as to support provider-specific storage management requests. In one aspect the interface conforms to a Component Object Model (COM) interface.

[0016] In another aspect, the invention is a method for managing the plurality of volume providers. According to the method, a storage management request is received from a software application. One or more commands are generated as a function of the received storage management request. The generated commands are then selectively communicated to one or more of the volume providers. In one aspect the method further includes aggregating response information from the volume providers and communicating the aggregated information to the software application that issued the storage management request.

[0017] FIG. 1 shows a diagram of the hardware and operating environment in conjunction with which embodiments of the invention can be practiced;

[0018] FIG. 2 is a block diagram illustrating a system-level overview of a storage network having two computing systems and a variety of storage devices;

[0019] FIG. 3 is a block diagram illustrating one embodiment of a storage management system for uniformly managing software and hardware volume providers according to the invention; and

[0020] FIG. 4 is a flowchart illustrating one mode of operation of the inventive storage management system.

[0021] In the following detailed description of exemplary embodiments of the invention, reference is made to the accompanying drawings that form a part hereof, and in which is shown by way of illustration specific exemplary embodiments in which the invention may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the invention, and it is to be understood that other embodiments may be utilized and that changes may be made without departing from the spirit or scope of the present invention. The following detailed description is, therefore, not to be taken in a limiting sense, and the scope of the present invention is defined only by the appended claims.

[0022] The detailed description is divided into six sections. In the first section, a glossary of terms is provided. In the second section, the hardware and the operating environment in conjunction with which embodiments of the invention may be practiced are described. In the third section, a system level overview of the invention is presented. In the fourth section, methods for an exemplary embodiment of the invention are provided. In the fifth section, an exemplary embodiment of the invention is provided. Finally, in the sixth section, a conclusion of the detailed description is provided.

[0023] Compromised—a status indicating that a fault tolerant volume is missing one or more disk or volume extents; for example, a mirror set with only one mirror currently available.

[0024] Configuration data—describes the mapping of physical resources to logical volumes.

[0025] Directed configuration—a provider is explicitly furnished rules for choosing logical block remapping.

[0026] Disk platter—a subset of a diskpack, used for exporting or importing volumes from a diskpack.

[0027] Diskpack—a collection of logical volumes and underlying disks. A diskpack is the unit of transitive closure for a volume.

[0028] Export—Move a disk platter and all volumes contained on that platter out of one diskpack.

[0029] Mounted—a volume is mounted by an operating system when the volume has an associated volume name (drive letter or volume mount point). The volume can be made available to a file system or other data store.

[0030] Free agent drive—a disk drive which is not a member of a disk pack. Free agent drives cannot contain logical volumes that are mounted.

[0031] Health—volume fault management status. A volume may be initializing, healthy, compromised, unhealthy, or rebuilding.

[0032] Healthy—containing or being able to contain valid data.

[0033] Hot-spotting—temporary plexing of a volume or collection of volume extents.

[0034] Import—Move a disk platter and all volumes contained on that platter into one diskpack.

[0035] Initializing—a status indicating that a volume is rediscovering volume configuration.

[0036] LBN—logical block number.

[0037] Logical block mapping—relationship between the logical blocks exposed to the logical volume provider to those exposed by the same provider.

[0038] Logical volume provider—software which exposes logical volumes. A provider includes runtime services, configuration data, and management services.

[0039] Management service—software to perform volume configuration, monitoring or fault handling.

[0040] Mapped volume—a simple linearly logical block mapping which concatenates volumes to expose a single larger volume.

[0041] Mirrored volume—logical volume which maintains two or more identical data copies. Also termed RAID 1.

[0042] Parity striped volume—logical volume which maintains parity check information as well as data. The exact mapping and protection scheme is vendor-specific. Includes RAID 3, 4, 5, 6.

[0043] Plexed volume—a temporary mirror volume. Plexing is used to create a copy of a volume rather than to provide fault tolerance. The mirror is added to the volume with the intent of removal after the contents have been synchronized.

[0044] RAID—redundant array of independent disks.

[0045] Rebuilding—a status indicating that a previously compromised fault tolerant volume is resynchronizing all volume extent data.

[0046] Runtime service—software that executes on a per-IO request basis.

[0047] SCSI—Small-Computer Systems Interface.

[0048] Stacked volume—volume has been constructed by more than one logical block mapping operation. An example is a stripe set of mirror volumes. Stacking includes stripping, mapping, and plexing.

[0049] Striped volume—a logical block mapping which distributes contiguous logical volume extents across multiple volumes. Also termed RAID 0.

[0050] Unhealthy—a status indicating that a non-fault tolerant volume missing one or more disk or volume extents; data contained on unhealthy volumes must not be accessed. Volume

[0051] Volume configuration stability—status to determine whether volume logical to physical mapping is undergoing change. A volume may be stable, extending, shrinking, plexing, or remapping.

[0052] Volume extent—a contiguous range of logical blocks contained on a volume. Volume extents are the smallest managed logical volume unit.

[0053] Volume status—current use of a volume by the system. A volume may be unused, mounted, in use, or unknown.

[0054] FIG. 1 is a diagram of the hardware and operating environment in conjunction with which embodiments of the invention may be practiced. The description of FIG. 1 is intended to provide a brief, general description of suitable computer hardware and a suitable computing environment in conjunction with which the invention may be implemented. Although not required, the invention is described in the general context of computer-executable instructions, such as program modules, being executed by a computer, such as a personal computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types.

[0055] Moreover, those skilled in the art will appreciate that the invention may be practiced with other computer system configurations, including hand-held devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, network PCs, minicomputers, mainframe computers, and the like. The invention may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.

[0056] The exemplary hardware and operating environment of FIG. 1 for implementing the invention includes a general purpose computing device in the form of a computer 20, including a processing unit 21, a system memory 22, and a system bus 23 that operatively couples various system components, including the system memory 22, to the processing unit 21. There may be only one or there may be more than one processing unit 21, such that the processor of computer 20 comprises a single central-processing unit (CPU), or a plurality of processing units, commonly referred to as a parallel processing environment. The computer 20 may be a conventional computer, a distributed computer, or any other type of computer; the invention is not so limited.

[0057] The system bus 23 may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, or a local bus using any of a variety of bus architectures. The system memory may also be referred to as simply the memory, and includes read only memory (ROM) 24 and random access memory (RAM) 25. A basic input/output system (BIOS) 26, containing the basic routines that help to transfer information between elements within the computer 20, such as during start-up, is stored in ROM 24. The computer 20 further includes a hard disk drive 27 for reading from and writing to a hard disk, not shown, a magnetic disk drive 28 for reading from or writing to a removable magnetic disk 29, and an optical disk drive 30 for reading from or writing to a removable optical disk 31 such as a CD ROM or other optical media.

[0058] The hard disk drive 27, magnetic disk drive 28, and optical disk drive 30 are connected to the system bus 23 by a hard disk drive interface 32, a magnetic disk drive interface 33, and an optical disk drive interface 34, respectively. The drives and their associated computer-readable media provide nonvolatile storage of computer-readable instructions, data structures, program modules and other data for the computer 20. It should be appreciated by those skilled in the art that any type of computer-readable media which can store data that is accessible by a computer, such as magnetic cassettes, flash memory cards, digital video disks, Bernoulli cartridges, random access memories (RAMs), read only memories (ROMs), and the like, may be used in the exemplary operating environment.

[0059] A number of program modules may be stored on the hard disk 27, magnetic disk 29, optical disk 31, ROM 24, or RAM 25, including an operating system 35, one or more application programs 36, other program modules 37, and program data 38. A user may enter commands and information into the personal computer 20 through input devices such as a keyboard 40 and pointing device 42. Other input devices (not shown) may include a microphone, joystick, game pad, satellite dish, scanner, or the like. These and other input devices are often connected to the processing unit 21 through a serial port interface 46 that is coupled to the system bus, but may be connected by other interfaces, such as a parallel port, game port, or a universal serial bus (USB). A monitor 47 or other type of display device is also connected to the system bus 23 via an interface, such as a video adapter 48. In addition to the monitor, computers typically include other peripheral output devices (not shown), such as speakers and printers.

[0060] The computer 20 may operate in a networked environment using logical connections to one or more remote computers, such as remote computer 49. These logical connections are achieved by a communication device coupled to or a part of the computer 20, the local computer; the invention is not limited to a particular type of communications device. The remote computer 49 may be another computer, a server, a router, a network PC, a client, a peer device or other common network node, and typically includes many or all of the elements described above relative to the computer 20, although only a memory storage device 50 has been illustrated in FIG. 1. The logical connections depicted in FIG. 1 include a local-area network (LAN) 51 and a wide-area network (WAN) 52. Such networking environments are commonplace in offices, enterprise-wide computer networks, intranets and the Internet.

[0061] When used in a LAN-networking environment, the computer 20 is connected to the local network 51 through a network interface or adapter 53, which is one type of communications device. When used in a WAN-networking environment, the computer 20 typically includes a modem 54, a type of communications device, or any other type of communications device for establishing communications over the wide area network 52, such as the Internet. The modem 54, which may be internal or external, is connected to the system bus 23 via the serial port interface 46. In a networked environment, program modules depicted relative to the personal computer 20, or portions thereof, may be stored in the remote memory storage device. It is appreciated that the network connections shown are exemplary and other means of, and communications devices for, establishing a communications link between the computers may be used.

[0062] The hardware and operating environment in conjunction with which embodiments of the invention may be practiced has been described. The computer in conjunction with which embodiments of the invention may be practiced may be a conventional computer, a distributed computer, or any other type of computer; the invention is not so limited. Such a computer typically includes one or more processing units as its processor, and a computer-readable medium such as a memory. The computer may also include a communications device such as a network adapter or a modem, so that it is able to communicatively couple to other computers.

[0063] FIG. 2 is a block diagram illustrating a system-level overview of storage network 100 that includes computer 105, computer 110 and storage devices 106 that are communicatively coupled via network 120. Computers 105 and 110 represent any suitable computing system such as local computer 20 or remote computer 49 in FIG. 1. Storage devices 106 include storage device 108, storage device 112, and storage device 114 that may be any suitable storage medium such as a single internal disk, multiple external disks or even a RAID cabinet.

[0064] Storage devices 108 and 114 are directly connected to computers 105 and 110, respectively while storage device 112 is directly connected to network 120 and, in the illustrated embodiment, is a RAID storage cabinet having multiple disks. Storage devices 106 have corresponding volume providers (not shown) to map logical storage volumes onto one or more storage devices 106 of storage network 100. These volume providers may be implemented in either software or hardware and may reside within the respective storage devices 108, 112 and 114 or within computers 105 and 110. As illustrated in detail below, the invention provides a seamless approach to managing the hardware and software volume providers of storage network 100.

[0065] FIG. 3 is a block diagram illustrating one embodiment of a storage management system 200 for managing various volume providers 203 of storage network 100 (FIG. 2). Storage management system 200 includes applications 210, common volume manager 202, and volume providers 203. Application 210 can be a management-type software application used by a system administrator to configure volumes or can be a user-type application that accesses the storage devices 106. As illustrated in FIG. 3, volume providers 203 consist of software volume providers 204 and hardware volume providers 206 that execute in user space 218. In other embodiments volume providers 203 execute in any combination of user space 218 and kernel space 220. Drivers 212 and 214 support run-time services that are provided by the operating system and execute in kernel space 220.

[0066] Common volume manager 202 integrates software providers 204 and hardware providers 206 in order to present a unified view for accessing and configuring storage devices 106. Common volume manager 202 receives volume management requests from applications 210 and issues commands to volume providers 203 accordingly. In so doing, common volume manager 202 enforces storage policies to ensure uniformity across providers 203 and provides high-level service routines for storage network 100. Examples include: (1) performing a data flush on a node of storage network 100 prior to breaking a mirror plex, (2) deciding whether to unbind a logical volume that spans multiple storage devices 106, (3) using the underlying characteristics of the storage devices 106 to allocate mirror copies of a volume based on pairs of devices that have similar seek and data-rate characteristics, (4) relocating volumes to a more appropriate storage device 106, (6) only allowing storage devices having similar characteristics to be striped, and (7) performing all security authentication and authorization. When a new storage device is added to storage network 100 its storage characteristics are analyzed, compared with the existing storage devices 106 and the new storage device is utilized accordingly. For example, if the new storage device supports mirrored volumes and has a seek and latency better than those of an existing pair of devices that currently implement a mirrored volume then common volume manager 202 can move the mirrored volume from the two storage devices 106 to the new storage device.

[0067] Volume providers 203 receive the commands from volume manager 202 and perform a variety of management tasks in response such as volume configuration, performance monitoring and asynchronous event handling. Volume providers 203 may include vendorspecific rules to optimize binding configurations, monitor and dynamically tune performance, automatically handle faults, or any other vendor-specific added functionality. In addition, volume providers 203 expose configuration data that identifies the physical resources comprising the logical volumes of storage network 100.

[0068] In order to integrate volume providers 203, common volume manager 202 presents an Application Programming Interface (“API”) 209 that provides a set of functions, or interfaces, by which applications 210, such as administrative tools, are able to manage volume providers 203 without having detailed knowledge of the volume providers 203 or the underlying storage devices 106. For example, applications 210 need not be aware of the underlying policies, physical characteristics, etc., of each volume provider 203. Applications need not know whether the provider 203 is a software provider 204 or a hardware provider 206. The invention allows applications 210 to monitor and track how I/O requests are distributed throughout storage devices 106 without individually examining each storage device 106. For example, even though storage devices 106 may be running different platforms and may be manufactured by different vendors, an application 210 is able to identify an overloaded storage device 106 and load balance across storage devices 106 via common volume manager 202.

[0069] Common volume manager 202 requires that each volume provider 203 conform to interface 208. Interface 208 supports a group of primitives that describe the configurations for the various storage devices 106 of storage network 100 such as a number of disks and their organization. At a minimum, volume providers 203 convert the functions of interface 208 to industry standard or vendor-specific protocol requests to the controller. In addition, interface 208 allows storage devices 106 to pass a variety of performance information to applications 210. As devices are added to storage devices 106, new volume providers 203 can be easily integrated into storage management system 200. In one embodiment, interface 208 and API 209 are implemented using Component Object Model (COM).

[0070] Each volume provider 203 within storage management system 200 has a corresponding hardware driver 214. In addition, a software volume provider 204 may interface with a corresponding software driver 212 or may may utilize a hardware volume provider 206 via common volume manager 202. Drivers 212 and 214 handle all communications with storage devices 106 and may implement one of a variety of protocols such as SCSI (“Small-Computer Systems Interface”), IP (“Internet Protocol”), etc.

[0071] Although the volume providers 203 must conform to interface 208, the invention places no restraints on how the volume providers 203 communicate with the software drivers 212 or hardware drivers 214 and can use any desired protocol. In this fashion, storage management system 200 requires no changes to conventional drivers 212 and 214. Thus, vendors of storage devices 106 are free to develop their own communication protocols.

[0072] In order to facilitate uniform communication to the various providers 203, common volume manager 202 identifies each logical volume, each storage device 106 and each volume provider 203 with a Globally Unique Identifier (GUID). In addition, API 209 provides abstracted volume types and defines default, wildcard, and error values. The following list illustrates one embodiment of abstracted volume types: Default, FaultTolerant, NotFaultTolerant, Simple, Span, Stripe, Mirror, Parity, Plex.

[0073] API 209 is extensible in the sense that volume providers 203 supports provider-specific extension for exposing provider-specific configuration attributes and parameters. Applications 210 that use these provider-specific extensions are responsible for interpreting these extensions and are assumed to have knowledge of their meaning. In one embodiment, each exposed attribute consists of a short name, a longer descriptive text and a current value. This embodiment allows applications 210 to generically accommodate arbitrary provider extensions.

[0074] Volume configuration and query operations invoked by applications 210 may take considerable time for processing by providers 203. As such, common volume manager 202 allows all functions of API 209 to be invoked asynchronously. Applications 210 provide a callback routine and parameter in order to handle the asynchronous event that is issued when the request has been processed. In one embodiment, applications 210 and common volume manager 202 handle the asynchronous events via a COM interface.

[0075] The system level overview of the operation of an exemplary embodiment of the invention has been described in this section of the detailed description. As described, the inventive volume management system presents a common view for accessing and configuring software providers and hardware volume providers.

[0076] In the previous section, a system level overview of the operation of an exemplary embodiment of the invention was described. In this section, the particular methods performed by a computer executing an exemplary embodiment are described by reference to a flowchart. The methods to be performed by a computer constitute computer programs made up of computer-executable instructions. Describing the methods by reference to a flowchart enables one skilled in the art to develop such programs including such instructions to carry out the methods on suitable computers (the processor of the computers executing the instructions from computer-readable media).

[0077] FIG. 4 is a flowchart 400 illustrating one exemplary method of operation of common volume manager 202 (FIG. 3) for managing various volume providers of storage network 100 (FIG. 2). Common volume manager 202 begins flowchart 400 with block 402 and proceeds to block 404. In block 404, common volume manager 202 receives a storage management request from an application 210 via API 209 as discussed in detail above.

[0078] In block 405 common volume manager 202 generates one or more commands necessary to execute the storage management request. In block 406, common volume manager 202 issues the commands to appropriate volume providers 203. If a command requires action by more than one provider 203 then common volume manager 202 communicates the command to all of the necessary providers 203. The volume providers 203 communicate the commands to storage devices 106 for processing. If, however, volume providers 203 are able to respond to the commands without assistance then volume providers 203 need not communicate the commands to the underlying storage devices 106 and can process the commands locally.

[0079] After processing the commands, in block 408 the volume providers 203 communicate response information to common volume manager 202. This response information can indicate whether the command was successful, it can contain current configuration information, or it can contain a variety of status information such as current loading and performance. In block 410 the common volume manager 202 aggregates related information. For example, in many cases common volume manager 202 issues commands to two or more volume providers 203. When these commands are completed, common volume manager 202 aggregates the response information in order to communicate a uniform response to the requesting application 210 in block 412.

[0080] Step 414 represents the completion of a single cycle in which an application 210 issues a storage request and receives resulting response information. As discussed above, because certain functions of interface 208 may require substantial processing time, interface 208 presented by common volume manager 202 also supports asynchronous event handling for receiving the response information.

[0081] This section describes in detail one embodiment of API 209 (FIG. 3) provided by common volume management 202. The functions presented by API 209 generally fall within three categories:

[0082] 1. Configuration operations that guide logical volume creation, deletion, modification, and migration between systems;

[0083] 2. Topology and state queries that allow discovery of the current configuration including the physical disks which comprise a given volume, the type of volume and volume status such as recovering after disk failure.

[0084] 3. Maintenance and monitoring operations for fault management, performance monitoring, and common site maintenance.

[0085] Listed below is one embodiment of specific functions supported by common volume manager 202 and accessible through API 209:

[0086] QueryLvmParameters—returns vendor-specific parameters that identify the providers 203, the underlying volume type and information regarding vendor extensions.

[0087] CancelVolumeOperation—cancels any previous issued asynchronous volume configuration operation or configuration query.

[0088] CompleteVolumeOperation—waits for the completion of a previously issued asynchronous volume configuration operation or configuration query.

[0089] BindVolume—creates and initially configures a volume.

[0090] UnbindVolume—Deletes and deconfigures the volume. All data is lost. All disk extents that contributed to the volume are freed for immediate reuse by the volume provider 203. The common volume manager 202 performs any coordination with the operating system prior to passing this request to the volume provider 203.

[0091] StripeVolume—Creates and configures a striped logical volume using extents from the specified logical volumes or disks. Stripe sets are constructed from equal length extents; equal size extents from each target (volume or disk) in the allocation array are consumed.

[0092] UnstripeVolume—Deletes and deconfigures the stripe set volume. All data is lost. All volume or disk extents that contributed to the volume are freed for immediate reuse by the stacking volume provider. Common volume manager 202 performs any coordination with the operating system prior to passing this request to the volume provider.

[0093] MapVolume—Configures a mapped volume. Volume extents are allocated in the order specified by the allocation array and concatenated. The resulting mapped volume is mounted by the operating system and a drive letter or mount point is assigned.

[0094] UnmapVolume—Deletes and deconfigures the mapped volume. This also removes the volume from use by the operating system and any associated disk number is deleted. Common volume manager 202 performs any coordination with the operating system prior to passing this request to the volume provider 203.

[0095] ExtendVolume—Grows the specified volume. The mechanism depends on the type of volume being extended. Simple spanned or mapped volumes are extended by appending volume extents. Striped volumes are extended by growing each contributing automagic volume. Plexed volumes are extended by growing each plex.

[0096] ShrinkVolume—Removes volume extents from the specified volume. Striped volumes are contracted by shrinking each contributing volume.

[0097] AddPlex—Adds a plex to the specified volume. The completion routine is invoked after the added plex has been synchronized with the original volume.

[0098] RemovePlex—Removes a previously added plex from the specified volume. Common volume manager 202 optionally synchronizes the file system prior to causing the plex to be broken. After removal, the plex is no longer held in synchronization with the original volume.

[0099] CreatePack—Creates a diskpack. The extent size must be a power of two disk sectors. If the extent size is not specified, common volume manager 202 will use 1% of the largest disk drive known to be in the configuration. For example, the extent size would default to 128 MB for configurations with 18 GB drives.

[0100] DeletePack—Deletes a diskpack.

[0101] AddDisksToPack—Adds disks to a pack. Any logical volume originally on the added disks is lost and not imported to the pack.

[0102] EvacuateDisks—This routine moves any volume extents from the disk array to other disks in the diskpack. Note that to be eligible for removal, any volumes occupying a disk must have been evacuated. In other words, the disk must contain no live data. The disks remain evacuated until explicitly declared ready for inhabit or hot spare.

[0103] FreeDisksFromPack—Removes disks from pack and makes them free agents. Note that to be eligible for removal, any volumes occupying a disk must have been evacuated. In other words, the disk must contain no live data.

[0104] ReplaceDisk—Substitutes one physical disk for another to allow media migration. Any contents of the replaced disk are migrated, although not necessarily to the new disk. At completion, the replaced disk is no longer in use and may be physically removed.

[0105] InhabitDisks—Declares the disks available for volume migration or other volume configuration operation.

[0106] ImportPlatter—Imports all volumes and adds all disks contained on the platter to the pack. This operation may fail or cause reconfiguration of the existing volumes if the volume allocation extent of the platter differs from that of the receivirig platter. If one or more disks have been lost in the movement, volumes contained on the platter may not be transitively closed. The imported volumes join all other volumes in the pack.

[0107] ExportPlatter—Marks all disks on the platter ready for export. As a side effect, the disks contained in the platter are recorded such that when the platter is subsequently imported, the receiving pack can determine if all disks are present.

[0108] MigratePlatter—Atomically moves the platter between packs. Both packs must be present on the same processor node in a cluster.

[0109] MoveVolumesToPlatter—Prepares a platter for migration by moving one or more volumes to one or more disks.

[0110] MoveVolumesFromPlatter—Explicitly moves volumes or evacuates disks and frees them from a platter.

[0111] ForgetPlatter—Cancels preparation of a platter for volume migration. Any volumes on the platter rejoin the disk pack and may migrate freely.

[0112] In addition to the above-listed functions, API 209 supports many queries that allow an application 210 to determine logical volume configuration including determination of the underlying physical resources of a volume provider.

[0113] QueryDisks—Returns all disks with the option of grouping or filtering by provider and/or pack.

[0114] OueryVolumes—Returns all volumes with optional “scoping” (grouping) by a specified criteria such as by provider, pack or type.

[0115] QueryVolumeExtents—Returns all volumes contributing one or more extents to this volume. Only one level of the stacking hierarchy is traversed; the query must be made at each stacking level to build up a complete view.

[0116] QueryVolumeDiskExtents—Returns all disk extents contributing to the volume, regardless of the stacking hierarchy. This routine provides a simple physical view of the resources consumed by the volume.

[0117] QueryVolumesUsingDisk—Finds all volumes with extents residing on the specified disk.

[0118] QuervVolumesUsingVolume—Finds all stacked volumes with extents residing on the specified volume.

[0119] QueryVolumeMount—Returns the operating system disk number or mount point for a mapped volume.

[0120] OuervVolumeDeviceObiect—Returns the lowest level logical identifiers for a disk or hardware RAID volume.

[0121] OueryVolumePlexes—Finds all plexes of the specified volume. The returned volume array contains plexes in plexld order.

[0122] OueryVolumesUsingPlex—Finds the base volume given a plex. The returned plexld is that of the original plex volume.

[0123] QueryPacks—Returns all diskpacks.

[0124] QueryPlatters—Returns all disk platters with optional scoping by pack.

[0125] QueryPackofPlatter—Returns the diskpack containing the specified platter.

[0126] QueryPlatterVolumes—Returns all volumes contained on the specified platter.

[0127] QueryVolumePack—Returns the pack that contains the volume.

[0128] QueryVolumePlatter—Returns the platter (if any) and pack which contains the volume. If the volume is not on a platter, the platter is returned as NO_PLATTER.

[0129] OueryPlatterDisks—Returns the disks (if any) contained on the platter.

[0130] QueryDiskPack—Returns the diskpack containing the disk. If the disk is a free agent, the returned pack is NO PACK.

[0131] OueryDiskPlatter—Returns the platter (if any) and pack which contains the disk. If the disk is not on a platter, the returned id is NO_PLATTER. If the disk is a free agent, the returned pack is NO_PACK.

[0132] In addition, API 209 supports additional queries regarding the status of a logical volume maintained by providers 203 including the following attributes: Access by OS (VOLUME_STATUS), fault recovery status (VOLUME_HEALTH), configuration stability (VOLUME_JELLO), disk pack membership (VOLUME_PACK), whether or not the volume is plexed, whether or not the volume logical mapping is fixed or dynamic, relative rebuild priority (high-low).

[0133] OueryVolumeAttributes—Returns volume type, provider, pack, size, and attributes.

[0134] QueryVolumeSize—Returns volume size.

[0135] QueryVolumeType—Returns volume type.

[0136] QueryVolumeStatus—Returns volume status.

[0137] OueryVolumeProvider—Returns volume provider.

[0138] QueryVolumeLbnRemap—Returns whether or not the volume may currently be dynamically reconfigured.

[0139] OueryVolumeUsingStatus—Returns all volumes with specified status with optional scoping by provider and/or pack and/or type.

[0140] OueryVolumeUsingHealth—Returns all volumes with specified health with optional scoping by provider and/or pack and/or type.

[0141] ForceVolumeHealthy—Forces volume to be healthy. Allows possibly dangerous override in the event of catastrophic disk failures.

[0142] ForceVolumeInitialize—Forces volume to be reinitialized. All data may be lost. Allows possibly dangerous override in the event of catastrophic disk failures.

[0143] ForceVolumeRebuild—Forces volume to be rebuilt. Allows possibly dangerous override in the event of catastrophic disk failures.

[0144] SetVolumeLbnRemap—Enables or disables remapping by the logical volume provider. Disabling remapping freezes the current logical to physical topology of the volume.

[0145] SetVolumeRebuildPrioritv—Sets the relative rebuild priority for the volume.

[0146] SetVolumeName—Renames the volume.

[0147] SetVolumeExtensions—Sets provider-specific extended attributes for the volume.

[0148] QueryDiskSize—Returns size in bytes of the specified disk.

[0149] QueryDiskConnection—Returns abstracted physical connection to disk.

[0150] OueryDiskProvider—Returns lowest level provider managing the disk.

[0151] QueryDiskStatus—Returns current access by the operating system.

[0152] SetDiskHotSpare—Declares disk to be used as a “hot” spare. If the disk current contributes to one or more logical volumes, this call will fail. The volumes must be first moved using ReplaceDisk.

[0153] QueryProviders—Returns all active logical volume providers.

[0154] QueryVolumeProviderName—Returns the name of the specified logical volume provider.

[0155] In addition, API 209 also provides routines that export an abstract view of the physical topology and hardware resources of the storage devices 106. For example, API 209 reveals the current condition of a hardware controller and the parameters affecting volumes configured using that controller are described by controller attributes including:

[0156] Current controller in active use and path to that controller.

[0157] Battery backup support.

[0158] Physical topology underlying the controller such as the number of disks and disk paths.

[0159] Controller capabilities such as logical block remapping, volume rebuild support.

[0160] Controller physical attributes such as cache size and firmware revision.

[0161] QueryVolumeController—Returns the provider, pack, and controller associated with the specified volume.

[0162] QueryDiskController—Returns the provider, pack (if any), and controller associated with the specified disk.

[0163] OueryControllerParameters—Returns the array of vendor-specific controller extended parameter values.

[0164] QueryControllerAttributes—Returns controller type, associated provider, any packs to which the controller contributes disks, whether the controller is currently online, controller health and attributes.

[0165] OueryControllerPath—Returns primary, secondary, and currently active paths for a dual pathed controller.

[0166] OueryControllerLbnRemap—Returns whether or not the controller is capable of dynamic volume reconfiguration and whether or not the controller is currently allowed to do so. If remapping is enabled, the provider can migrate volume extents at will.

[0167] ForceControllerHealthy—Forces controller to be healthy. Allows possibly dangerous override in the event of catastrophic controller or disk failures.

[0168] ForceControllerlnitialize—Forces controller to reinitialize.

[0169] ForceControllerRebuild—Forces all volumes configured behind the controller to be rebuilt.

[0170] ForceControllerPath—Forces active controller path to specified path.

[0171] SetControllerExtensions—Sets provider-specific extended attributes for the controller.

[0172] OueryDiskParameters—Returns the array of vendor-specific disk extended parameter values.

[0173] QueryDiskAttributes—Returns associated provider, pack (if any), abstracted connection type, controller, size, status, and vendor-specific extensions for the specified disk.

[0174] OueryControllerDisks—Returns an array of disks attached to the specified controller. The array identifies each disk path and the disks per path.

[0175] Common volume manager 202 also provides two kinds of maintenance operations via API 209:

[0176] Simple target identification and sanity checks. These functions allow access to a subset of site maintenance operations such as flashing a light on a disk drive. Disk drives, controllers, or logical volumes can be targeted by these functions.

[0177] Detailed inquiries of the controller and disk hardware status, including setting hardware alarm thresholds. In one embodiment this model follows the SCSI-3 SES protocol that is known to one skilled in the art. These functions eliminate the need for detailed knowledge of the underlying vendor-specific protocol.

[0178] The common volume manager 202 translates simple maintenance operations targeting logical volumes to operations on each contributing disk. In all cases, specifying nonsensical operations or operations unsupported by the volume providers 203 will cause the operation to fail with no side effects.

[0179] StartMaintenance—Initiates specified hardware maintenance operation. The operation will repeat until stopped.

[0180] StopMaintenance—Stops or cancels specified hardware maintenance operation. This stops any repeated operations such as blinking a light.

[0181] PulseMaintenance—Repeats specified hardware maintenance operation a specified number of times.

[0182] OueryMaintenanceElements—Returns the supported maintenance targets and instances of each. The maintenance element type and number of each populate the returned element array.

[0183] SetMaintenanceControl—Requests maintenance control operations.

[0184] GetMaintenanceStatus—Requests return of maintenance status.

[0185] SetMaintenanceThreshold—Requests maintenance threshold change operations.

[0186] GetMaintenanceThreshold—Requests return of maintenance thresholds.

[0187] Common volume manager 202 exposes performance tuning and monitors to applications 210. Volume providers 203 must implement these functions, but there are only minimal requirements on that implementation. Volume providers 203 could implement a proprietary performance tuner and expose only the required performance tuning or monitoring. A volume provider could also choose to be transparent and expose all sorts of tuning knobs and lots of performance monitoring, but take no provider-specific actions. All performance tuning parameters are assumed to be provider-specific.

[0188] QuervPerformanceAttributes—Returns common and vendor-specific performance attribute arrays.

[0189] EnablePerformanceCounter—Enables specified performance counters.

[0190] DisablePerformanceCounter—Disables specified performance counters.

[0191] ClearPerformanceCounter—Clears (sets to zero) specified performance counters.

[0192] QueryPerformanceData—Returns current performance counter value array.

[0193] StartPerformanceMonitor—Start performance counters.

[0194] StopPerformanceMonitor—Stop performance counters.

[0195] Various embodiments of the inventive volume management system have been described that present a unified view for accessing software providers and hardware volume providers. Several advantages of the invention have been illustrated such as providing a common interface by which applications are able to control or monitor the volume providers without requiring detailed knowledge of the volume providers or the underlying storage devices. Therefore, it is intended that only the claims and equivalents thereof limit this invention.