Abstract:
A cluster based file service may operate on a cluster of two or more independent devices that have access to a common data storage. The file service may have a namespace definition with each device in the cluster, but may be modified by any device operating the file service. Each instance of the file service may identify and capture a command that changes the namespace structure and cause the change to be propagated to the other members of cluster. If one of the devices in the cluster does not successfully perform an update to the namespace structure, that device may be brought offline. The cluster based file service may permit adding or removing devices from the cluster while the file service is operating, and may provide a high throughput and high availability file service.
Abstract:
A centralized service identifies a pool of devices that can be accessed by clients over a network. Devices can include a local or network-accessible device, and a configurable file that represents a portion of a device (e.g., a SCSI storage device). In some cases, the devices (or the file representing a portion of the device) can be identified by an assigned logical unit number. The centralized service assigns one or more devices to a target, and associates client information with the target. The centralized service also can also assign the target a logical unit number, and assign the target to a protocol-independent portal, which further operates through protocol-dependent miniports. In one embodiment, a client accesses a network device by accessing the appropriate port through an appropriate miniport protocol (e.g., Ethernet, fiber channel, etc.), and by submitting appropriate target authorization.
Abstract:
Coordinating methods of I/O access to a shared data store. A method includes at a node, in a distributed system, performing one or more I/O operations on the shared data store using direct I/O access on a virtual data container. Direct I/O access includes performing I/O operations directly from the node to the shared data store including not having an owner node perform the I/O operation on the shared data store on the node's behalf. The owner node is a different node than the node doing the direct I/O operation. The owner node accesses the shared data store through a local data container. The method further includes determining that one or more subsequent I/O operations should be performed using redirected I/O access, where I/O operations are directed through a centralized node. The method further includes indicating to nodes in the distributed system to switch to redirected I/O access method.
Abstract:
A frequency and phase estimator simultaneously estimates the frequency and phase of an MPSK modulated signal with a frequency uncertainty range on the order of the symbol rate. The estimator defines a plurality of contiguous bands within the frequency uncertainty range of the signal, estimates the frequency to one of the bands, and utilizes the frequency estimate to derive a phase estimate. In a preferred embodiment, a plurality of signal samples of the frequency shifted signal in each of said bands are accumulated to produce a vector for each band, and the frequency estimate is selected in one of said bands, based upon the magnitude of the corresponding vector. The phase is estimated from the argument of the corresponding vector. The present invention is particularly suited for burst modems or TDMA systems, where frequency and phase estimates must be derived reliably from a limited number of incoming symbols at the beginning of each burst.
Abstract:
The representation of storage devices on computers (e.g., as logical volumes) may be complicated by the pooling of multiple storage devices in order to apply redundancy plans such as mirroring and checksumming. Presented herein is a storage device driver configured to operate as a storage device interface generating representations of the storage regions of the storage devices; to claim those regions as a storage controller; and to expose pooled storage regions as logical disks. Additionally, the storage device driver may support the inclusion of storage devices in a cluster, comprising nodes that may be appointed as managers of the storage pool configuration; as managers of the storage devices; as owners having exclusive read/write access to the storage pool or cluster resources; and as cluster resource writers having exclusive write access to a cluster resource. The nodes of the cluster may interoperate to share the storage devices while avoiding write conflicts.
Abstract:
A centralized service identifies a pool of devices that can be accessed by clients over a network. Devices can include a local or network-accessible device, and a configurable file that represents a portion of a device (e.g., a SCSI storage device). In some cases, the devices (or the file representing a portion of the device) can be identified by an assigned logical unit number. The centralized service assigns one or more devices to a target, and associates client information with the target. The centralized service also can also assign the target a logical unit number, and assign the target to a protocol-independent portal, which further operates through protocol-dependent miniports. In one embodiment, a client accesses a network device by accessing the appropriate port through an appropriate miniport protocol (e.g., Ethernet, fiber channel, etc.), and by submitting appropriate target authorization.
Abstract:
A cluster based file service may operate on a cluster of two or more independent devices that have access to a common data storage. The file service may have a namespace definition with each device in the cluster, but may be modified by any device operating the file service. Each instance of the file service may identify and capture a command that changes the namespace structure and cause the change to be propagated to the other members of cluster. If one of the devices in the cluster does not successfully perform an update to the namespace structure, that device may be brought offline. The cluster based file service may permit adding or removing devices from the cluster while the file service is operating, and may provide a high throughput and high availability file service.
Abstract:
The invention includes a semiconductor device, comprising a silicon carbide substrate comprising micropipes, wherein the micropipes are filled with a dielectric, and a method of making such a device.
Abstract:
The present invention extends to methods, systems, and computer program products for implementing persistent reservation techniques for establishing ownership of one or more physical disks. These persistent reservation techniques can be employed to determine ownership of physical disks in a storage pool as well as in any other storage configuration. Using the persistent reservation techniques of the present invention, when a network partition occurs, a defender of a physical disk does not remove a challenger's registration key until the defender receives notification that the challenger is no longer in the defender's partition. In this way, pending I/O from applications executing on the challenger will not fail due to the challenger's key being removed until the proper ownership of the physical disk can be resolved.
Abstract:
A centralized service identifies a pool of devices that can be accessed by clients over a network. Devices can include a local or network-accessible device, and a configurable file that represents a portion of a device (e.g., a SCSI storage device). In some cases, the devices (or the file representing a portion of the device) can be identified by an assigned logical unit number. The centralized service assigns one or more devices to a target, and associates client information with the target. The centralized service also can also assign the target a logical unit number, and assign the target to a protocol-independent portal, which further operates through protocol-dependent miniports. In one embodiment, a client accesses a network device by accessing the appropriate port through an appropriate miniport protocol (e.g., Ethernet, fiber channel, etc.), and by submitting appropriate target authorization.