Classifications

• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F9/00—Arrangements for program control, e.g. control units
  • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
  • G06F9/46—Multiprogramming arrangements
  • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
  • G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
  • G06F9/5011—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resources being hardware resources other than CPUs, Servers and Terminals
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
  • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
  • G06F3/0601—Interfaces specially adapted for storage systems
  • G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
  • G06F3/0604—Improving or facilitating administration, e.g. storage management
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
  • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
  • G06F3/0601—Interfaces specially adapted for storage systems
  • G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
  • G06F3/0629—Configuration or reconfiguration of storage systems
  • G06F3/0631—Configuration or reconfiguration of storage systems by allocating resources to storage systems
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
  • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
  • G06F3/0601—Interfaces specially adapted for storage systems
  • G06F3/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
  • G06F3/067—Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F9/00—Arrangements for program control, e.g. control units
  • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
  • G06F9/46—Multiprogramming arrangements
  • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
  • G06F9/5061—Partitioning or combining of resources
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F2209/00—Indexing scheme relating to G06F9/00
  • G06F2209/50—Indexing scheme relating to G06F9/50
  • G06F2209/505—Clust

Definitions

• This invention relates generally to data storage devices, and more particularly to an arbitration mechanism for logical quorums resources within a storage network.
• data storage devices such as magnetic or optical disks.
• 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.
• the storage devices can be separate or co-located in a single cabinet.
• a storage network is a collection of interconnected computing systems, referred to as nodes, operating as a single storage resource.
• a storage network allows a system to continue to operate during hardware or software failures, increases scalability by allowing nodes to be easily added and simplifies management by allowing an administrator to manage the nodes as a single system.
• Cluster software exists on each node and manages all cluster-specific activity of a storage network.
• the cluster software often executes automatically upon startup of the node. At this time the cluster software configures and mounts local, non-shared devices.
• the cluster software also uses a 'discovery' process to determine whether other members of the storage network are operational.
• the cluster software discovers an existing cluster, it attempts to join the cluster by performing an authentication sequence.
• a cluster master of the existing cluster authenticates the newcomer and returns a status of success if the joining node is authenticated. If the node is not recognized as a member then the request to join is refused.
• a quorum resource can be a logical resource, such as a volume, that includes one or more physical quorum resources.
• a volume is a logical storage unit that can be a fraction of a disk, a whole disk, fractions of multiple disks or even multiple disks.
• Inventive cluster management software and volume management software execute on the nodes of a storage network and operate in cooperation with the underlying operating system in order to arbitrate for logical quorum resources such as a quorum volume.
• the cluster management software arbitrates for logical quorum resources and forms a storage network without having knowledge of the underlying physical quorum resources.
• the cluster management software is not hardware specific.
• the cluster management software need not be aware of how the logical quorum resource is formed from the underlying physical quorum resources.
• the volume management software manages is solely responsible for forming and mounting the logical quorum volume. The volume management software performs volume management without having detailed knowledge of the arbitration process and the determination of ownership.
• FIG. 1 shows a diagram of the hardware and operating environment in conjunction with which embodiments of the invention can be practiced
• 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
• FIG. 3 is a block diagram illustrating one embodiment of a software system having cooperating software components that cleanly separates the responsibilities of cluster arbitration from the management of volumes and the underlying storage devices;
• FIG. 4 is a flowchart illustrating one mode of operation of the software system of FIG. 3 in which the system arbitrates for logical quorum resources according to the invention.
• Configuration data - describes the mapping of physical resources to logical volumes.
• Directed configuration - provider is explicitly provided with rules for choosing logical block remapping.
• Disk platter - a subset of a diskpack, used for exporting or importing volumes from a diskpack.
• Diskpack a collection of logical volumes and underlying disks.
• a diskpack is the unit of transitive closure for a volume.
• Export - Move a disk platter and all volumes contained on that platter out of one diskpack.
• Exposed - a volume is exposed to an operating system when the volume has an associated volume name (drive letter) or mount point.
• the volume can be made available to a file system or other data store.
• Free agent drive - a disk drive which is not a member of a disk pack. Free agent drives cannot contain logical volumes that are exposed.
• a volume can be initializing, healthy, compromised, unhealthy, or rebuilding.
• Logical quorum resource - a logical resource that is necessary to form a storage network.
• the logical quorum resource such as a logical volume, comprises one or more physical quorum resources, such as a disk
• Logical volume - a logical storage unit that can be a fraction of a disk, a whole disk, a fraction of multiple disks or even multiple disks.
• Logical volume provider - software which exposes logical volumes.
• a provider includes runtime services, configuration data, and management services.
• Mapped volume a simple linearly logical block mapping which concatenates volumes to expose a single larger volume.
• 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.
• Plexed volume - dynamic 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.
• Runtime service - software that executes on a per-IO request basis.
• 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.
• Striped volume - a logical block mapping which distributes contiguous logical volume extents across multiple volumes. Also termed RAID 0.
• 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 configuration stability whether volume logical to physical mapping is undergoing change. A volume may be stable, extending, shrinking, plexing, or remapping.
• Volume extent a contiguous range of logical blocks contained on a volume. Volume extents are the smallest managed logical volume unit. Volume status - current use of a volume by the system. A volume may be unused, hot spare, mapped, used, or unknown.
• 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.
• 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.
• program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types.
• 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.
• program modules can be located in both local and remote memory storage devices.
• 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.
• 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.
• CPU central-processing unit
• parallel processing environment commonly referced to as a parallel processing environment.
• the computer 20 can be a conventional computer, a distributed computer, or any other type of computer; the invention is not so limited.
• the system bus 23 may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, and 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.
• ROM read only memory
• RAM random access memory
• 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.
• 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.
• 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 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.
• computers typically include other peripheral output devices (not shown), such as speakers and printers.
• the computer 20 may operate in a networked environment using logical connections to one or more remote computers, such as remote computer 49.
• 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.
• LAN local-area network
• WAN wide-area network
• the computer 20 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.
• the computer 20 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.
• 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.
• 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.
• 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.
• FIG. 2 is a block diagram illustrating a system-level overview of storage network 100 that includes node 105 communicatively coupled to node 110 via network 120.
• Nodes 105 and 110 represent any suitable computing system such as local computer 20 or remote computer 49 depicted in FIG. 1.
• Storage network 100 further includes storage subsystem 106 that comprise storage device 107, storage device 108, and storage device 109. These devices may be any suitable storage medium such as a single internal disk, multiple external disks or even a RAID cabinet.
• Storage subsystem 106 are coupled via bus 112, which is any suitable interconnect mechanism such as dual- connect SCSI ("Small-Computer Systems Interface”), fiber-channel, etc.
• nodes 105 and 110 arbitrate for a logical quorum resource such as a quorum volume.
• the logical quorum resource is illustrated as a quorum volume that is collectively formed by physical quorum resources 111, which in this embodiment are data storage extents within data storage device 108 and data storage device 109. If either node 105 or 110 is successful at obtaining ownership of all physical quorum resources 111, the successful node may form storage network 100.
• inventive cluster management software and volume management software execute on each node and resolve situations where ownership of physical quorum resources 111 is split between nodes 105 and 110. On each node, the cluster management software and the volume management software cooperate with the underlying operating system to form storage network 100.
• arbitration and management responsibilities are divided between the cluster management software and the volume management software such that cluster management software handles the arbitration process without knowing the details of volume management and storage subsystem 106.
• the volume management software handles the configuration and management of storage subsystem 106 without knowing how storage network 100 is formed.
• FIG. 3 is a block diagram illustrating one embodiment of a node 200, such as node 105 or node 110 of FIG. 2, in which various cooperating software components carryout the inventive arbitration technique.
• cluster manager 202 oversees all cluster specific activity and communicates to bus 112 (FIG. 2) of storage subsystem 106 via disk controller 206.
• bus 112 FIG. 2
• cluster manager 202, volume manager 204 and operating system 35 cooperatively manage the quorum volume for storage network 100 and the conesponding physical quorum resources 111. More specifically, cluster manager 202 handles the arbitration process without knowing the details of volume management and storage subsystem 106.
• Volume manager handles all volume mapping and the configuration of storage subsystem 106 of storage network 100.
• Disk controller 206 handles all communications with storage subsystem 106 and may implement one of a variety of data communication protocols such as SCSI, IP, etc.
• Applications 210 represent any user-mode software module that interacts with storage network 100. The system level overview of the operation of an exemplary embodiment of the invention has been described in this section of the detailed description.
• FIG. 4 illustrates how the present invention cleanly separates the responsibilities of cluster management from the responsibility of volume management.
• arbitration cycle 300 illustrates one embodiment of the inventive transformation arbitration method as performed by cluster manager 202 and volume manager on each node of storage network 100.
• Arbitration cycle 300 is invoked when storage network 100 has not yet been established, such as when either node 105 or 110 is the first to boot, or anytime storage network 100 had been previously formed but communication between the nodes 105 and 110 has broken down.
• the arbitration cycle 300 can be initiated by either node 105 or node 110 by proceeding from block 302 to block 304.
• cluster manager 202 (FIG. 3) terminates all cureent ownership of storage subsystem 106. In one embodiment this is accomplished by resetting bus 112. This action in turn forces all the other nodes of the storage network 100 to perform arbitration cycle 300 and places all volumes of into an off-line mode. In this mode, volume manager 204 blocks all access storage subsystem 106.
• the arbitrating nodes wait a predetermined delay period before proceeding with arbitration cycle 300 in order to ensure that all nodes of storage network 100 have entered arbitration.
• cluster manager 202 instructs volume manager 204 to scan all other nodes within storage network 100 in order to update configuration information for each new or removed storage device 106.
• the configuration information maintained by volume manager 204 is only partially complete because those that were owned by other nodes may have been changed.
• cluster manager 202 instructs volume manager 204 to generate a list that identifies those storage subsystem 106 that were previously owned by nodes of storage network 100.
• volume manager 204 reads and processes volume information from each storage device 106 of the generated list. Volume manager 204 rebuilds an internal configuration database.
• volume manager 204 has information regarding all storage subsystem 106 and all volumes thereon.
• cluster manager 202 requests that volume manager 204 identify all physical quorum resources 111 associated with the quorum volume.
• the volume manager 204 determines all storage subsystem 106 having physical quorum resources 111 and rebuilds quorum volume information for storage network 100. For example, referring to Figure 1 volume manager 204 identifies storage device 108 and 109 as necessary for ownership to ensure that a volume may be brought online.
• quorum volume information is consistent for all nodes of storage network 100.
• cluster manager 202 attempts to take ownership of storage devices 108 and 109.
• cluster manager 202 invokes conventional arbitration techniques provided by bus 112, such as techniques specified by the SCSI protocol, in order to arbitrate for the physical quorum resources, i.e., storage devices 108 and 109.
• conventional arbitration techniques provided by bus 112, such as techniques specified by the SCSI protocol, in order to arbitrate for the physical quorum resources, i.e., storage devices 108 and 109.
• either node 105 or 110 may own both storage devices 108 and 109 or the ownership of physical quorum resources 111 may be split due to race conditions present in the conventional arbitration techniques.
• volume manager 204 determines whether the local node, i.e. the node upon which cluster manager 202 is running, has successfully acquired ownership of both storage devices 108 and 109 necessary for the quorum volume. If so, volume manager 204 mounts the quorum volume and, in block 316, cluster manager 202 declares the local node to be the cluster master and informs the other nodes that storage network 100 has been formed. At this point, the other nodes terminate arbitration and join storage network 100.
• volume manager 204 proceeds from block 314 to block 318 and determines whether the local node has acquired ownership of any quorum volume resources, i.e., either storage device 108 or 109. If the local node does not have ownership of either then control passes to cluster manager 202 which, in block 320, terminates arbitration and waits for communication from another node that ultimately becomes the cluster master.
• volume manager 204 proceeds from block 318 to block 322 and determines whether the volume list is sufficient to form a quorum. Volume manager may use several different algorithms in determining whether the volume list is suitable such as a simple majority or a weighted voting scheme. If the volume list is not sufficient then volume manager 204 releases any quorum resources.
• Cluster manager 202 proceeds to block 320 and waits for communication from another node that ultimately becomes the cluster master.
• volume manager 204 determines whether it is safe to mount the quorum volume. This determination is based on volume specific information. For example, if the quorum volume uses concatenated or striped extents then volume manager 204 will always determine it unsafe to mount the quorum volume when only one extent is owned. As another example, when the quorum volume is a RAID V, then volume manager 204 may apply a "minus one" algorithm such that all but one of the extents are required. In addition, volume manager 204 may apply user selectable criteria. For example, if the quorum volume is a mirror then the user may configure volume manager 204 to require all extents or to require a simple majority. If volume manager 204 can safely mount the quorum volume then volume manager 204 mounts the quorum volume and cluster manager 202 proceeds to block 316 and declares the local node the cluster master.
• cluster manager 202 waits a predetermined amount of time. If in block 326 communication is not received from a cluster master within that time, cluster manager 202 jumps back to block 304 and repeats the inventive arbitration method. In one embodiment, the delay period increases with each iteration of arbitration cycle 300.

Landscapes

• Engineering & Computer Science (AREA)
• Theoretical Computer Science (AREA)
• Physics & Mathematics (AREA)
• General Engineering & Computer Science (AREA)
• General Physics & Mathematics (AREA)
• Software Systems (AREA)
• Human Computer Interaction (AREA)
• Hardware Redundancy (AREA)
• Multi Processors (AREA)

Priority Applications (2)

Applications Claiming Priority (2)

Publications (2)

Family

ID=23784686

Family Applications (1)

Country Status (4)

Cited By (8)

Families Citing this family (25)

Family Cites Families (3)

• 1999
  • 1999-11-29 US US09/449,579 patent/US6615256B1/en not_active Expired - Lifetime
• 2000
  • 2000-11-21 EP EP00980603A patent/EP1234240A2/en not_active Withdrawn
  • 2000-11-21 JP JP2001540586A patent/JP5185483B2/ja not_active Expired - Fee Related
  • 2000-11-21 WO PCT/US2000/031936 patent/WO2001038992A2/en not_active Ceased

Also Published As

Similar Documents

Legal Events