A source storage unit of a storage network operates by: sending a slice to migrate from the source storage unit to a destination storage unit; sending a slice verification request to the destination storage unit, wherein the slice verification request includes one or more of: a slice identifier, the slice, a revision indicator, a verification method indicator, or a nonce; receiving an integrity value from the destination storage unit; determining when the integrity value compares favorably to the slice verification request by determining when a hash of the slice and a nonce matches the integrity value or determining when a decrypted signature of the integrity value matches a hash of the slice and the nonce or the slice and the nonce; when the integrity value compares favorably to the slice verification request, updating a slice identifier assignment associated with a slice identifier corresponding to the slice, wherein updating the slice identifier assignment associates the destination storage unit with the slice identifier and disassociates the source storage unit from the slice identifier.

In various embodiments, methods and systems for implementing distributed data object management are provided. The distributed data object management system includes a distributed storage system having a local metadata-consensus information store in and one or more remote metadata-consensus information stores. A metadata-consensus information store is configured to store metadata-consensus information. The metadata-consensus information corresponds to erasure coded fragments of a data object and instruct on how to manage the erasure coded fragments. The distributed storage system further includes a local data store and one or more remote data stores for the erasure coded fragments. The distributed data object management system includes a distributed data object manager for operations including, interface operations, configuration operations, write operations, read operations, delete operations, garbage collection operations and failure recovery operations. The distributed data object management system is operates based on metadata paths and data paths, operating in parallel, for write operations and read operations.

Techniques are provided for processing user input/output (I/O) write requests in a fault-tolerant data storage system (e.g., a RAID storage system) by selecting between performing a degraded write operation or a write operation to spare capacity, when the fault-tolerant data storage system is operating in a degraded mode. A method includes receiving a user I/O write request comprising data to be written to a RAID array operating in a degraded mode, and determining whether spare capacity has been allocated for rebuilding missing data of an inaccessible storage device of the RAID array and whether a missing data block, which is associated with I/O write request, has been rebuilt to the spare capacity. A degraded write operation is performed without using the spare capacity, when the missing data block, which is associated with the data of the I/O write request, has not been rebuilt to the allocated spare capacity.

A method for backing up data, that includes making a detection, by a volatile storage firmware, that data communication to a volatile storage component is degraded, initiating a direct memory access (DMA) engine to copy the data from the volatile storage component to a non-volatile storage device, and in response to initiating copying of the data, initiating a shutdown of the volatile storage component.

A method may include, in an operating system of an information handling system: responsive to a determination that a storage resource of the information handling system is experiencing a predictor of a failure of the storage resource, issuing a command to the storage resource to reload firmware code of the storage resource; responsive to the storage resource reloading the firmware code and reset of the storage resource following reloading of the firmware code, determining whether the predictor persists; and responsive to determining whether the predictor persists, performing a responsive action.

A method, computer program product, and computer system for identifying a bit for an allocation unit. It may be determined if data has been modified on the allocation unit while degraded. A rebuild of the allocation unit may be executed when the bit is a first value. The rebuild of the allocation unit may be skipped when the bit is a second value.

An indication that a selected data set stored on a selected tape storage media is associated with a failure is received. An error correction data set group for the selected data set is identified, and wherein the error correction data set group includes a plurality of data sets and each data set included in the error correction data set group is stored on a different tape storage media. One or more data sets other than the selected data set that are included in the error correction data set group are selectively obtained from one or more corresponding tape storage media other than the selected tap storage media without reading entire contents of the one or more corresponding tape storage media. The obtained one or more data sets are utilized to recover at least a portion of the selected data set associated with the failure.

Embodiments of the present disclosure provide method, device and computer program product for managing a storage system. The storage system includes a disk having a plurality of extents. The method comprises obtaining metadata associated with an RAID stripe in a first RAID of a first type, the first RAID including at least a part of extents from the plurality of extents. The method also comprises allocating an additional extent to the RAID stripe. The method further comprises converting, based on the allocated additional extent and by modifying the metadata, the first RAID of the first type into a second RAID of a second type in a degraded mode. Additionally, the method comprises initiating, based on the modified metadata, a rebuilding process for the second RAID, so as to convert the second RAID from the degraded mode to a normal mode.

An autonomous RAID data storage system includes a RAID storage controller device that communicates with RAID data storage devices in order to configure them to perform direct command operations with each other. A first RAID data storage device receives a multi-step command from the RAID storage controller device and performs a first subset of operations associated with the multi-step command, while also performing direct command operations with a second RAID data storage device in order to cause it to perform a second subset of operations associated with the multi-step command, When the first RAID data storage device completes the first subset of operations and receives a first completion communication from the second RAID data storage device that indicates that the second subset of operations are completed, it sends a second completion communication to the RAID storage controller device that indicates that the multi-step command is completed.

A system and method for providing erasure code protection across multiple storage devices. A data switch in a storage system connects a plurality of storage devices to a remote host. Each storage device is also connected to a controller, e.g., a baseboard management controller. During normal operation, read and write commands from the remote host are sent to respective storage devices through the data switch. When a write command is executed, the storage device executing the command sends a copy of the data to the controller, which generates and stores erasure codes, e.g., on a storage device that is dedicated to the storage of erasure codes, and invisible to the remote host. When a device fails or is removed, the controller reconfigures the data switch to redirect all traffic addressed to the failed or absent storage device to the controller, and the controller responds to host commands in its stead.