Abstract: A driver model is generated that describes the configuration of one or more driver objects. The driver model and developer driver code are compiled to generate a driver including a machine readable driver model and compiled developer driver code, wherein the machine readable driver model and the complied developer driver code are independently serviceable.

Abstract: A system that facilitates the storage of data using a write barrier. The system interfaces to a hardware component that stores data, and includes a write barrier component that dynamically employs instructions compatible with the hardware component to ensure data integrity during storage of the data. The write barrier component is independent of at least an operating system and an application and can operate in a least one of a user mode and a kernel mode. The write barrier component includes at least one of software instructions, routines, and methods, the selection of one or more of which is based on hardware data extracted from the hardware component. A selection component interrogates the hardware component for hardware data to facilitate selection of one or more instructions most suitable for interfacing to the hardware component. A coalescing component combines cache synchronization requests into a single set of instructions, which set is processed to flush a disk cache in one process.

Abstract: A system, methodology and/or computer architecture that facilitates processing device interrupts (including level-triggered interrupts) in a user-mode process is provided. The kernel interrupt handler can cause a dedicated thread in the process to wake and invoke the driver interrupt service routine. This thread can then return control to the kernel interrupt handler. In addition to processing interrupts in an isolated mode, the context switching technique could be used in any isolated environment to process interrupts via dedicated execution context methods.

Abstract: A system, methodology and/or computer architecture that facilitates processing device interrupts (including level-triggered interrupts) in a user-mode process is provided. The kernel interrupt handler can cause a dedicated thread in the process to wake and invoke the driver interrupt service routine. This thread can then return control to the kernel interrupt handler. In addition to processing interrupts in an isolated mode, the context switching technique could be used in any isolated environment to process interrupts via dedicated execution context methods.

Abstract: A mount manager and supporting data structures enable automatic identification and re-establishment of logical volumes on non-removable storage devices in a computer system across multiple reboots and reconfigurations. The mount manager generates a redirected name for a new logical volume when a unique volume identifier is presented to the mount manager by the operating system. The mount manager stores the unique volume identifier and the associated redirected name in a persistent mount manager data structure. The mount manager establishes a symbolic link between the persistent redirected name and a non-persistent device name used by the operating system. During the boot process, the mount manager uses the data structure entries identified by the unique volume identifiers of the arriving logical volumes to reconstruct the symbolic links so that references to the redirected name will resolve to the correct non-persistent device name.

Abstract: A mount manager and supporting data structures enable automatic identification and re-establishment of logical volumes on non-removable storage devices in a computer system across multiple reboots and reconfigurations. The mount manager generates a redirected name for a new logical volume when a unique volume identifier is presented to the mount manager by the operating system. The mount manager stores the unique volume identifier and the associated redirected name in a persistent mount manager data structure The mount manager establishes a symbolic link between the persistent redirected name, which is used by higher layers of the operating system and user applications to address the logical volume, and a non-persistent device name used by the operating system.

Abstract: A partition manager enables the dynamic creation, reconfiguration, and deletion of logical volumes as non-removable storage devices are connected, reconfigured, or disconnected in a computer system by assigning partitions on a connected device to volume managers which create the logical volumes, and by removing the assignment when the device is disconnected or reconfigured. The partition manager receives notification from the operating system of the arrival of new volume managers in a system. When new partitions are created on a non-removable storage device in the system by a device driver, the partition manager intercepts the partitions before they can be registered with the operating system. The partition manager queries each volume manager, in order of their arrival in the system, as to whether the volume manager handles a particular new partition and assigns control of the partition to the appropriate volume manager.

Abstract: A mount manager and supporting data structures enable automatic identification and re-establishment of logical volumes on non-removable storage devices in a computer system across multiple reboots and reconfigurations. The mount manager generates a redirected name for a new logical volume when a unique volume identifier is presented to the mount manager by the operating system. The mount manager stores the unique volume identifier and the associated redirected name in a persistent mount manager data structure The mount manager establishes a symbolic link between the persistent redirected name, which is used by higher layers of the operating system and user applications to address the logical volume, and a non-persistent device name used by the operating system.

Abstract: A system and method are described to programmatically manage access between one or more nodes and a plurality of associated devices, such as shared storage units. Each node is programmed to include a data structure, which identifies whether an associated device is to be within the scope of the respective node. The data structure and may include persistent and/or temporary lists. Each device may be programmatically masked relative to the node by dynamically modifying the data structure of the node, such as by employing a predetermined interface.

Abstract: A partition manager enables the dynamic creation, reconfiguration, and deletion of logical volumes as non-removable storage devices are connected, reconfigured, or disconnected in a computer system by assigning partitions on a connected device to volume managers which create the logical volumes, and by removing the assignment when the device is disconnected or reconfigured. The partition manager receives notification from the operating system of the arrival of new volume managers in a system. When new partitions are created (“enumerated”) on a non-removable storage device in the system by a device driver, the partition manager intercepts the partitions before they can be registered with the operating system. The partition manager queries each volume manager, in order of their arrival in the system, as to whether the volume manager handles a particular new partition and assigns control of the partition to the appropriate volume manager.

Abstract: A mount manager and supporting data structures enable automatic identification and re-establishment of logical volumes on non-removable storage devices in a computer system across multiple reboots and reconfigurations. The mount manager generates a redirected name for a new logical volume when a unique volume identifier is presented to the mount manager by the operating system. The mount manager stores the unique volume identifier and the associated redirected name in a persistent mount manager data structure The mount manager establishes a symbolic link between the persistent redirected name, which is used by higher layers of the operating system and user applications to address the logical volume, and a non-persistent device name used by the operating system.

Abstract: A method and system for detecting and reporting storage hardware failure prediction is disclosed. The method and system provide a standardized mechanism for any type of storage device to predict and report storage failures. This includes SMART SCSI devices, SMART ATA/ATAPI devices, non-SMART SCSI devices, non-SMART ATA/ATAPI devices, proprietary storage devices, and others such as CD-ROM drives, DVD ROMs, tape drives, and RAM disks. A device driver obtains failure prediction status information and propagates it to a management application. The information may be propagated via a failure prediction filter driver used to perform statistical analysis or proprietary access to the hardware. In a Windows operating environment, information is propagated from the device driver through a Windows Management Instrumentation component.