Abstract: Systems and methods for data storage device firmware updates in a composable infrastructure are described. Recomposition of a system in a composable infrastructure may include downloading a firmware update to a data storage device, activating the firmware update in the data storage device, and receiving a reset command at the data storage device. The reset command may include a step to flush a virtual-to-physical (V2P) mapping table from a volatile memory in the data storage device to non-volatile memory devices in the data storage device. Responsive to a flag that is set and the received reset command, the data storage device may forgo the step of flushing the V2P mapping table.

Abstract: Systems and methods for predicting whether a nonvolatile memory block is likely capable of being securely erased to be eligible for composing into another composable infrastructure are described. A management module receives a secure-erase command to erase at least one nonvolatile memory block, determines health parameters of the nonvolatile memory block, calculates a failure index based on the health parameters, and, based on the failure index, either securely erases the block of memory or retires the nonvolatile memory block.

Abstract: Systems and methods for storage operation processing during data migration using selective block migrated notifications are disclosed. A host system may be configured with connections to a source storage node and a destination storage node while a data migration is moving data blocks from the source to the destination. The host may send a storage request to the source storage node and receive a block migrated notification from the source storage node. The host may then store a migrated indicator for that data block in a migration table and direct future storage requests to the destination storage node.

Abstract: Systems and methods for distributed storage systems using synchronous discovery logs for fabric subsystem discovery. Storage nodes may be configured with fabric services and a management service may provide synchronization of discovery logs across fabric subsystems and between peer fabric nodes. The peer fabric nodes may communicate with one another using a fabric network protocol and corresponding fabric subsystems may communicate with each peer fabric node. When a target subsystem fabric node updates its discovery log, the updated discovery log is sent to the corresponding peer fabric node. The corresponding peer fabric node sends the updated discovery log to each subsystem fabric node and to each peer fabric node for synchronization across all subsystem fabric nodes. A host may contact any subsystem fabric node for the updated discovery log.

Abstract: Systems and methods for failover port forwarding between peer storage nodes are described. Storage nodes may include separate data ports for host network communication and peer network communication. In the event of host port failure, host nodes may be configured to send failover storage requests to a different storage node and that storage node may forward the failover storage request through the peer ports to reach the target storage node.

Abstract: Systems and methods for storage operation processing during data migration using selective block migrated notifications are disclosed. A host system may be configured with connections to a source storage node and a destination storage node while a data migration is moving data blocks from the source to the destination. The host may send a storage request to the source storage node and receive a block migrated notification from the source storage node. The host may then store a migrated indicator for that data block in a migration table and direct future storage requests to the destination storage node.

Abstract: Systems and methods for connection virtualization in data storage device arrays are described. A host connection identifier may be determined for a storage connection request. A target storage device and corresponding completion connection identifier may be determined for a storage command including the host connection identifier. A command tracker may be stored that associates the storage command with the host connection identifier and the completion connection identifier and the storage command may be sent to the processing queue associated with the completion connection identifier.

Abstract: Systems and methods for predicting whether a nonvolatile memory block is likely capable of being securely erased to be eligible for composing into another composable infrastructure are described. A management module receives a secure-erase command to erase at least one nonvolatile memory block, determines health parameters of the nonvolatile memory block, calculates a failure index based on the health parameters, and, based on the failure index, either securely erases the block of memory or retires the nonvolatile memory block.

Abstract: Systems and methods for data storage device firmware updates in a composable infrastructure are described. Recomposition of a system in a composable infrastructure may include downloading a firmware update to a data storage device, activating the firmware update in the data storage device, and receiving a reset command at the data storage device. The reset command may include a step to flush a virtual-to-physical (V2P) mapping table from a volatile memory in the data storage device to non-volatile memory devices in the data storage device. Responsive to a flag that is set and the received reset command, the data storage device may forgo the step of flushing the V2P mapping table.

Abstract: Systems and methods for connection virtualization in data storage device arrays are described. A host connection identifier may be determined for a storage connection request. A target storage device and corresponding completion connection identifier may be determined for a storage command including the host connection identifier. A command tracker may be stored that associates the storage command with the host connection identifier and the completion connection identifier and the storage command may be sent to the processing queue associated with the completion connection identifier.

Abstract: Systems and methods for managing queue limit overflow for data storage device arrays are described. Host storage connections are allocated by host connection identifier and storage device processing queues are allocated by completion connection identifier through a connection virtualization layer. Storage commands may be directed to a processing queue based on the host connection identifier. Responsive to determining that the processing queue has reached its queue depth limit, another processing queue is determined for receiving the storage command without indicating processing queue overflow to the host device.

Abstract: Systems and methods for capped allocation of storage resources based on connection type are described. A new storage connection request from a host system to a group of data storage devices includes a connection type, such as a remote direct memory access connection or transmission control protocol connection. Based on the connection type, a subset of a pool of allocated storage resources for that connection type is determined. If the new connection request does not exceed the maximum number of connections allocated to the subset, a new storage connection is established. If the new connection request exceeds the maximum number of connections allocated to the subset, the new storage connection request fails.

Abstract: Systems and methods for managing queue limit overflow for data storage device arrays are described. Host storage connections are allocated by host connection identifier and storage device processing queues are allocated by completion connection identifier through a connection virtualization layer. Storage commands may be directed to a processing queue based on the host connection identifier. Responsive to determining that the processing queue has reached its queue depth limit, another processing queue is determined for receiving the storage command without indicating processing queue overflow to the host device.

Abstract: Systems and methods for capped allocation of storage resources based on connection type are described. A new storage connection request from a host system to a group of data storage devices includes a connection type, such as a remote direct memory access connection or transmission control protocol connection. Based on the connection type, a subset of a pool of allocated storage resources for that connection type is determined. If the new connection request does not exceed the maximum number of connections allocated to the subset, a new storage connection is established. If the new connection request exceeds the maximum number of connections allocated to the subset, the new storage connection request fails.

Abstract: Systems and methods for failover port forwarding between peer storage nodes are described. Storage nodes may include separate data ports for host network communication and peer network communication. In the event of host port failure, host nodes may be configured to send failover storage requests to a different storage node and that storage node may forward the failover storage request through the peer ports to reach the target storage node.

Abstract: Systems and methods for distributed storage systems using synchronous discovery logs for fabric subsystem discovery. Storage nodes may be configured with fabric services and a management service may provide synchronization of discovery logs across fabric subsystems and between peer fabric nodes. The peer fabric nodes may communicate with one another using a fabric network protocol and corresponding fabric subsystems may communicate with each peer fabric node. When a target subsystem fabric node updates its discovery log, the updated discovery log is sent to the corresponding peer fabric node. The corresponding peer fabric node sends the updated discovery log to each subsystem fabric node and to each peer fabric node for synchronization across all subsystem fabric nodes. A host may contact any subsystem fabric node for the updated discovery log.