Abstract: Methods, computer systems, and computer readable medium are described for low latency reads using cached deduplicated data, including: receiving a request to read data from a storage system; query, using a generated hash value associated with the request to read data, one or more deduplication tables that corresponds to the hash value; and responsive to determining that the one or more deduplication tables includes an entry that corresponds to the hash value, using a mapping contained in the entry to perform the requested to read data, wherein the mapping includes a pointer to a physical location where at least a portion of the data is stored.

Abstract: A processing system of a storage network operates by receiving a write request associated with a data object; identifying dispersed storage error encoding parameters; and determining a number of available storage units. When the number of available storage units is determined to exceed a first number, the processing system operates by: determining a first write threshold number in accordance with the dispersed storage error encoding parameters; dispersed error encoding the data object to produce a first write threshold number of encoded data slices; and writing, to available storage units, the first write threshold number of encoded data slices.

Abstract: A storage system switching between mediation models within a storage system, where the switching between mediation models includes: determining, among one or more of the plurality of storage systems, a change in availability of a mediator service, wherein one or more of the plurality of storage systems are configured to request mediation from the mediator service in response to a fault; and communicating, among the plurality of storage systems and responsive to determining the change in availability of the mediator service, a fault response model to be used as an alternate to the mediator service among one or more of the plurality of storage systems.

Abstract: A storage controller includes a processing device to send a storage command to a queue without routing the storage command through a kernel space. The queue is reserved for direct access by the application and may be associated with a set of permissions, a set of quality-of-service parameters, and/or a set of blocks on the storage devices of a storage system.

Abstract: Use of multivariate data backup retention policies, including: generating a snapshot of a dataset; identifying respective subsets of the dataset that correspond to respective retention policies of a plurality of retention policies; and generating tracking information indicating the respective subsets of the dataset corresponding to the respective retention policies of the plurality of retention policies.

Abstract: A first set of blocks of storage memory is allocated as durable and a second set of blocks of the storage memory is allocated as semi-durable. The durable first set of blocks are provided power loss protection (PLP) and the semi-durable second set of blocks lack PLP. Data generated by one or more background operations of the storage system is identified. The data generated by the one or more background operations is stored in one or more blocks of the semi-durable second set of blocks.

Abstract: Write requests to store data at one or more solid-state storage devices are received by a storage controller from clients external to a storage system. A number of open segments in the storage system is identified. A determination as to whether to open one or more subsequent segments for the write requests is made based on the number of open segments and a target parallelism for the storage system. In response to determining that the one or more subsequent segments are to be opened based on the number of open segments and the target parallelism, the one or more subsequent segments are opened.

Abstract: Converting data formats in a storage system: converting first data in a first format to second data in a second format, wherein second data in the second format includes a reference to the first data, wherein the first data and the second data are associated with a dataset, including updating the second data to include: a reference to first data associated with a portion of the dataset that precedes a data-converted portion of the dataset; second data associated with the data-converted portion of the dataset, wherein the second data associated with the data-converted portion of the dataset is in the second data format; and a reference to first data associated with a portion of the dataset that follows the data-converted portion of the dataset; and replacing first data associated with the data-converted portion of the dataset with a reference to the second data associated with the data-converted portion of the dataset.

Abstract: The embodiments provide for a method and system for dynamic configuration of a storage system to facilitate independent scaling of resources. The method and system include detecting a change to a topology of a storage system consisting of different sets of storage nodes, where at least one of the different sets of storage nodes has solid-state memory having differing storage capacities. Responsive to detecting the change, the storage system reconfigures to change an allocation of resources to one or more authorities that control a range of identifiers.

Abstract: An indication that a die of the solid-state storage device has been marked as likely to fail based on a number of failed input/output (I/O) operations performed on the die satisfying a threshold may be received by a storage system controller from a solid-state storage device. In response to receiving the indication, one or more remedial actions associated with the die of the solid-state storage device may be performed.

Abstract: Enabling data portability between systems, including: submitting, to a cloud-based metadata store storing metadata describing data stored in a plurality of storage systems each coupled for data communications with a corresponding on-premises cloud infrastructure of a plurality of on-premises cloud infrastructures, a query; selecting a subset of the data responsive to the query and stored in at least one first storage system coupled to at least one first on-premises cloud infrastructure; and storing, from the at least one first storage system to a second storage system coupled to a second on-premises cloud infrastructure, the subset of the data responsive to the query.

Abstract: Implementing guardrails for non-disruptive migration of workloads between storage arrays, the method comprising: initiating a non-disruptive migration of one or more workloads from a source storage array to a target storage array; validating, prior to completion of the non-disruptive migration, accessibility of the target storage array by one or more hosts; and completing, based on successfully validating the accessibility of the target storage array, the non-disruptive migration.

Abstract: Content including information describing an issue with a storage system is received. The content is analyzed by a generative artificial intelligence (AI) model to identify the issue described by the content. A solution for the issue is determined based on at least one of information associated with the storage system or information associated with one or more other storage systems. A response including a description of the solution for the issue is generated.

Abstract: Replicating data to the cloud includes a first dataset that is replicated from a first storage subsystem to the cloud, with only the changes made to the first dataset since a previous replication event being replicated to the cloud. Additionally, the data may be deduplicated and compressed before being replicated from the first storage subsystem to the cloud. In some cases, the first dataset may be replicated to the cloud in a stream format which is not directly usable and then, at a later point in time, loaded onto a second storage subsystem from the cloud.

Abstract: Creating a modifiable cloned image of a dataset, including: generating, based on a dataset stored within a source data repository, a tracking copy of replica data on a target data repository; generating, after receiving an indication to begin accepting modifications to the tracking copy of the replica data, a cloned image of the dataset that is modifiable without modifying the tracking copy of the replica data; and responsive to a storage operation directed to the target data repository, modifying the cloned image of the dataset without modifying the tracking copy of the replica data.

Abstract: Continuing replication during storage system transportation, including: replicating, between a first storage system and a second storage system, a dataset; connecting, by the first storage system during movement of the first storage system to a new physical location, to a communication network available at one or more intermediate physical locations; and continuing the replicating of the dataset between the first storage system at one or more of the intermediate physical locations and the second storage system over the communication network available at one or more of the intermediate physical locations.

Abstract: A first indication of an input/output (I/O) operation to be performed by a first storage system controller is stored in memory of a particular storage device storing data associated with the I/O operation by a second storage system controller. The first indication causes the particular storage device to store the data in a buffer of the first storage system controller. A second indication from the first storage system controller that the I/O operation has been completed is received via the particular storage device.

Abstract: Leveraging distinct storage tiers in a virtual storage system, including: receiving a request to write data to the virtual storage system; selecting, from amongst a plurality of tiers in the virtual storage system, a tier for receiving the data, wherein the plurality of tiers include a write-mostly tier and at least one other tier; and storing, within the selected tier within the virtual storage system, the data.

Abstract: Monitoring write amplification metrics for a flash-based storage system, including: generating, by a controller of a storage system, data describing write activity for each storage device of a plurality of storage devices of the storage system, wherein the data describing the write activity comprises data describing application write activity for each storage device of the plurality of storage devices; calculating, by the controller of the storage system, for each storage device of the plurality of storage devices, a corresponding write amplification metric; and providing, by the controller of the storage system, to each storage device of the plurality of storage devices, the corresponding write amplification metric.

Abstract: Determining effective space utilization in a storage system, including: identifying an amount of data stored within the storage system that is associated with a user-visible entity; identifying an amount of data stored within the storage system that is associated with all snapshots of the user-visible entity; and reporting, in dependence upon the an amount of data stored within the storage system that is associated with the user-visible entity and the amount of data stored within the storage system that is associated with all snapshots of the user-visible entity, a total capacity utilization associated with the user-visible entity.