Abstract: The storage processor of a data storage system such as a storage array automatically uses a first portion of an accelerator cache storage device for an accelerator cache and a second portion of the accelerator cache storage device for a physical storage tier upon detecting the presence of the accelerator cache storage device installed in the data storage system, such as when a storage device is plugged into a designated slot of the data storage system, without requiring any user configuration of the accelerator cache or physical storage tier and without specification by the user of the type(s) of data to be cached in the accelerator cache or stored in the physical storage tier.

Abstract: The storage processor of a data storage system such as a storage array automatically uses a first portion of an accelerator cache storage device for an accelerator cache and a second portion of the accelerator cache storage device for a physical storage tier upon detecting the presence of the accelerator cache storage device installed in the data storage system, such as when a storage device is plugged into a designated slot of the data storage system, without requiring any user configuration of the accelerator cache or physical storage tier and without specification by the user of the type(s) of data to be cached in the accelerator cache or stored in the physical storage tier.

Abstract: The storage processor of a data storage system such as a storage array automatically configures one or more accelerator caches (“AC”) upon detecting the presence of one or more solid-state storage devices (e.g., SSD drives) installed in the data storage system, such as when a storage device is plugged into a designated slot of the data storage system, without requiring any user configuration of the AC or specification by the user of the type(s) of data to be cached in the AC. The AC therefore provides a zero configuration cache that can be used to cache any of various types of data in the data storage system. The AC cache can be used in any of a wide variety of data storage systems including, without limitation, file servers, storage arrays, computers, etc. Multiple ACs may be created to cache different types of data.

Abstract: One embodiment is a method that divides a cluster file system into multiple segments with each segment including one or more local counters. The method then checks for inconsistencies and corrects discovered inconsistencies in each of the local counters while the file system remains online and available for use.

Abstract: The storage processor of a data storage system such as a storage array automatically configures one or more accelerator caches (“AC”) upon detecting the presence of one or more solid-state storage devices (e.g., SSD drives) installed in the data storage system, such as when a storage device is plugged into a designated slot of the data storage system, without requiring any user configuration of the AC or specification by the user of the type(s) of data to be cached in the AC. The AC therefore provides a zero configuration cache that can be used to cache any of various types of data in the data storage system. The AC cache can be used in any of a wide variety of data storage systems including, without limitation, file servers, storage arrays, computers, etc. Multiple ACs may be created to cache different types of data.

Abstract: One embodiment is a server in a cluster storage system. The server includes a Global Lock Manager (GLM) that receives requests for lock priorities for transactions from local lock manager (LLMs) in the cluster storage system. The GLM prevents deadlocks in the cluster storage system by issuing groups of priorities for transactions to the LLMs.

Abstract: One embodiment is a method that uses a hierarchical bitmap tree in a storage system to store where available and unavailable memory space exists. Bitmap blocks are retrieved from the hierarchical bitmap tree to locate the available memory space.

Abstract: One embodiment is a method that uses a hierarchical bitmap tree in a storage system to store where available and unavailable memory space exists. Bitmap blocks are retrieved from the hierarchical bitmap tree to locate the available memory space.

Abstract: One embodiment is a server in a cluster storage system. The server includes a Global Lock Manager (GLM) that receives requests for lock priorities for transactions from local lock manager (LLMs) in the cluster storage system. The GLM prevents deadlocks in the cluster storage system by issuing groups of priorities for transactions to the LLMs.

Abstract: One embodiment is a method that divides a cluster file system into multiple segments with each segment including one or more local counters. The method then checks for inconsistencies and corrects discovered inconsistencies in each of the local counters while the file system remains online and available for use.

Abstract: A system and method are disclosed for providing journal recovery in a multi-node environment which comprises determining whether a block was updated by a first node; determining whether the block is associated with a lock held by a second node; and writing the block to a final location if the block is not associated with a lock held by the second node.

Abstract: A system and method are disclosed for providing multi-node environment comprising a first node associated with a first operating system; a second node associated with a second operating system, wherein the second operating system is independent of the first operating system; a storage; and an interconnect coupling the first node with the storage and coupling the second node with the storage; and wherein the first node directly accesses the storage and the second node directly accesses the storage.

Abstract: A system and method are disclosed for providing journaling in a computer environment. An embodiment of the present invention comprises providing a first node and a second node; providing a journal wherein the journal is accessible by the first node and the second node; requesting a change in lock status by the first node; and executing a task by the second node in response to the request for the change in lock status by the first node.

Abstract: A system and method are disclosed for providing journal recovery in a multi-node environment which comprises determining whether a block was last updated by a first node; determining whether the block is associated with a lock held by a second node; and writing the block to a final location if the block is not associated with a lock held by the second node. In another embodiment, a system and method are disclosed for providing journal recovery in a multi-node environment which comprises determining whether a block is associated with metadata; determining whether the block is associated with a lock held by a surviving node; and writing the block to a final location if the block is not associated with a lock held by the surviving node.

Abstract: A system and method are disclosed for accessing data in a multi-node system comprising providing a first node associated with a first operating system; providing a second node associated with a second operating system, wherein the second operating system is independent of the first operating system; providing a storage, wherein the first node directly accesses the storage and the second node directly accesses the storage; requesting a lock for a block by the first node to the second node; obtaining the lock from the second node; and obtaining the block the from the second node.

Abstract: A system and method are disclosed for providing journaling in a computer environment. An embodiment of the present invention comprises providing a first node and a second node; providing a journal wherein the journal is accessible by the first node and the second node; requesting a change in lock status by the first node; and executing a task by the second node in response to the request for the change in lock status by the first node.

Abstract: A system and method are disclosed for providing multi-node environment comprising a first node associated with a first operating system; a second node associated with a second operating system, wherein the second operating system is independent of the first operating system; a storage; and an interconnect coupling the first node with the storage and coupling the second node with the storage; and wherein the first node directly accesses the storage and the second node directly accesses the storage.