Abstract: A processor may determine, for each subdevice of a set of subdevices of a storage enclosure device, one or more reliability measures of the subdevice. A processor may determine, based at least on the one or more reliability measures for the subdevices and a spatial layout rule, a set of striping groups that maximizes a reliability of the set of subdevices of the storage enclosure device, each of the striping groups including a respective subset of the set of subdevices, wherein the spatial layout rule prescribes a geometric layout of the subdevices within striping groups across the storage enclosure device. A processor may store output data of a data striping operation to a particular subset of subdevices associated with a particular striping group of the set of striping groups.

Abstract: Described are hard disk drives (HDDs) operable for archival applications and utilizing the same mechanical and electrical design of conventional HDDs. The capacity of a conventional HDD may be extended by up to 25% to 40% or more by employing multiple write and/or read spins before declaring success in write and read processes. The multiple write and/or read spins are designed to address the lower reliability that would otherwise result from high density packing of the data, at the cost of reducing performance. The result is an HDD with lower performance at higher capacity without sacrificing reliability and without altering conventional HDD mechanical or electrical design.

Abstract: A method includes receiving a piece of data at an upper-layer server of a multi-tiered storage system comprising the upper-layer server and a block server, and determining a signature for the piece of data. A first bloom filter stored on the upper-layer server is a copy of a second bloom filter stored on the block server. The first bloom filter is checked for the signature. When a match is found in the first bloom filter, the piece of data is sent for storage at the block server, and it is verified at the block server whether a match is present for the piece of data. When a match is present, the piece of data is deduplicated. When a match is not present, the piece of data is stored. When a match is not found in the first bloom filter, the piece of data is stored in the block server.

Abstract: A method includes receiving a piece of data for storage in a storage system, breaking the piece of data into a plurality of fixed size data portions, and determining a deduplication hash for each of the fixed size data portions. The method further includes checking for matching hashes already stored in the storage system, storing fixed size data portions unmatched to an already stored hash with metadata identifying the unmatched hash fixed size data portions in the storage system, and storing metadata for hash fixed size data portions already stored in the data storage system. The piece of data is reviewed for further deduplication using sliding window hashes during background activity of the data storage system.

Abstract: A method includes receiving a piece of data at an upper-layer server of a multi-tiered storage system comprising the upper-layer server and a block server, and determining a signature for the piece of data. A first bloom filter stored on the upper-layer server is a copy of a second bloom filter stored on the block server. The first bloom filter is checked for the signature. When a match is found in the first bloom filter, the piece of data is sent for storage at the block server, and it is verified at the block server whether a match is present for the piece of data. When a match is present, the piece of data is deduplicated. When a match is not present, the piece of data is stored. When a match is not found in the first bloom filter, the piece of data is stored in the block server.

Abstract: A method includes receiving a piece of data for storage in a storage system, breaking the piece of data into a plurality of fixed size data portions, and determining a deduplication hash for each of the fixed size data portions. The method further includes checking for matching hashes already stored in the storage system, storing fixed size data portions unmatched to an already stored hash with metadata identifying the unmatched hash fixed size data portions in the storage system, and storing metadata for hash fixed size data portions already stored in the data storage system. The piece of data is reviewed for further deduplication using sliding window hashes during background activity of the data storage system.

Abstract: A composite layout to store one or more extents of a data object in a first storage system and one or more extents of the data object in a second, different storage system. The first storage system may be configured for the efficient storage of small chunks of data such as, e.g., chunks of data small than the addressable block size of the storage devices used by the storage systems.

Abstract: Operations are monitored that involve a plurality of servers coupled to a plurality of data storage enclosures via a rack-level, storage networking fabric. The servers are operable to provide data storage services utilizing the data storage enclosures via a network. The data storage enclosures each have one or more data storage devices. The servers and the data storage enclosures are mounted within a data center rack. A failed unit determined that includes a failed one of the servers or a failed one of the data storage devices within a selected one of the data storage enclosures. A replacement is found for the failed unit within the data center rack, and the replacement is established for the failed unit within the data center rack. The establishment of the replacement involves establishing a new connection via the storage networking fabric.

Abstract: Operations are monitored that involve a plurality of servers coupled to a plurality of data storage enclosures via a rack-level, storage networking fabric. The servers are operable to provide data storage services utilizing the data storage enclosures via a network. The data storage enclosures each have one or more data storage devices. The servers and the data storage enclosures are mounted within a data center rack. A failed unit determined that includes a failed one of the servers or a failed one of the data storage devices within a selected one of the data storage enclosures. A replacement is found for the failed unit within the data center rack, and the replacement is established for the failed unit within the data center rack. The establishment of the replacement involves establishing a new connection via the storage networking fabric.

Abstract: Each disk drive in an array includes a housing that encloses a motor and at least one magnetic disk. The housing also encloses first and second actuators each with respective first and second heads that independently access the magnetic disk. The first actuator is mapped to a first logical unit and the second actuator is mapped to a second logical unit. A host interface of each disk drive facilitates access to the first and second logical units. A system includes a first storage controller attached to all of the first logical units as a first active server and attached to all of the second logical units as a first passive server. A second storage controller operates redundantly with the first storage controller. The second storage controller is attached to all of the second logical units as a second active server and attached to all of the first logical units as a second passive server.

Abstract: A first data storage rack has a first computing unit coupled to a first plurality of storage drives via a first storage controller. A second data storage rack has a second computing unit coupled to a second plurality of storage drives via a second storage controller. A first rack-to-rack storage link cable couples the first computing unit to the second storage controller such that the first computing unit can provide access to the second plurality of drives in response to a failure that prevents the second computing unit from providing access to the second plurality of drives via a system network.

Abstract: A first data storage rack has a first computing unit coupled to a first plurality of storage drives via a first storage controller. A second data storage rack has a second computing unit coupled to a second plurality of storage drives via a second storage controller. A first rack-to-rack storage link cable couples the first computing unit to the second storage controller such that the first computing unit can provide access to the second plurality of drives in response to a failure that prevents the second computing unit from providing access to the second plurality of drives via a system network.

Abstract: A data storage erasure system may have a host connected to a plurality of data storage devices via a network controller with each of the plurality of data storage devices and the network controller connected to a pods controller and each of the plurality of the data storage devices having a device controller. A rebuild strategy can be generated with a rebuild module connected to the plurality of data storage devices, the network controller, and the pods controller. The rebuild strategy may be directed to minimize data rebuild times in the event of a failure in the plurality of data storage devices by executing the rebuild strategy in response to a detected or predicted failure in at least one data storage device of the plurality of data storage devices.

Abstract: A composite layout to store one or more extents of a data object in a first storage system and one or more extents of the data object in a second, different storage system. The first storage system may be configured for the efficient storage of small chunks of data such as, e.g., chunks of data small than the addressable block size of the storage devices used by the storage systems.

Abstract: A data storage erasure system may have a host connected to a plurality of data storage devices via a network controller with each of the plurality of data storage devices and the network controller connected to a pods controller and each of the plurality of the data storage devices having a device controller. A rebuild strategy can be generated with a rebuild module connected to the plurality of data storage devices, the network controller, and the pods controller. The rebuild strategy may be directed to minimize data rebuild times in the event of a failure in the plurality of data storage devices by executing the rebuild strategy in response to a detected or predicted failure in at least one data storage device of the plurality of data storage devices.

Abstract: Each disk drive in an array includes a housing that encloses a motor and at least one magnetic disk. The housing also encloses first and second actuators each with respective first and second heads that independently access the magnetic disk. The first actuator is mapped to a first logical unit and the second actuator is mapped to a second logical unit. A host interface of each disk drive facilitates access to the first and second logical units. A system includes a first storage controller attached to all of the first logical units as a first active server and attached to all of the second logical units as a first passive server. A second storage controller operates redundantly with the first storage controller. The second storage controller is attached to all of the second logical units as a second active server and attached to all of the first logical units as a second passive server.