Abstract: A method of performing write operations that have been received by a data storage apparatus is provided. The method includes (a) storing page descriptors for received write operations within temporary storage, each page descriptor indicating respective data to be written; (b) upon storing each page descriptor, organizing that page descriptor into a shared working-set structure; and (c) operating a plurality of flushers to persist the data indicated by respective page descriptors to long-term persistent storage based on organization of the page descriptors in the shared working-set structure, each flusher accessing page descriptors via the shared working-set structure. An apparatus, system, and computer program product for performing a similar method are also provided.

Abstract: Successful storing of extent operations into corresponding records of a transaction log results in acknowledgement of completion of the extent operations being indicated to one or more hosts. In response to determining that the extent operations are unrelated to each other, the extent operations are flushed in parallel from the transaction log to back-end non-volatile data storage. During the flushing, dependencies between the extent operations and other operations stored in the transaction log are maintained. Dependency chains are identified within the transaction log, and at least one tree data structure representing the dependencies between each of the extent operations and the other operations stored in the transaction log may be generated and traversed in order to select the correct operations stored in the transaction log to flush.

Abstract: A method of performing write operations that have been received by a data storage apparatus is provided. The method includes (a) storing page descriptors for received write operations within temporary storage, each page descriptor indicating respective data to be written; (b) upon storing each page descriptor, organizing that page descriptor into a shared working-set structure; and (c) operating a plurality of flushers to persist the data indicated by respective page descriptors to long-term persistent storage based on organization of the page descriptors in the shared working-set structure, each flusher accessing page descriptors via the shared working-set structure. An apparatus, system, and computer program product for performing a similar method are also provided.

Abstract: Successful storing of extent operations into corresponding records of a transaction log results in acknowledgement of completion of the extent operations being indicated to one or more hosts. In response to determining that the extent operations are unrelated to each other, the extent operations are flushed in parallel from the transaction log to back-end non-volatile data storage. During the flushing, dependencies between the extent operations and other operations stored in the transaction log are maintained. Dependency chains are identified within the transaction log, and at least one tree data structure representing the dependencies between each of the extent operations and the other operations stored in the transaction log may be generated and traversed in order to select the correct operations stored in the transaction log to flush.

Abstract: A method performed by a computing device having memory is provided. The method includes (a) detecting corruption in a first page description block (PDB) of a plurality of PDBs stored in sequence in the memory, each PDB storing a set of page descriptors (PDs) that point to pages of data sequentially stored in the memory that are part of a single transaction, PDBs that represent the same transaction being contiguous within the sequence; (b) searching for a second PDB of the plurality of PDBs, the second PDB satisfying the following criteria: (1) it is not corrupted, and (2) it represents a same transaction as the first PDB; and (c) reconstructing the first PDB using the second PDB. An apparatus, system, and computer program product for performing a similar method are also provided.

Abstract: Techniques for creating snapshots of data storage objects that can perform certain operations (e.g., flushing dirty data, setting up extent pointers, allocating block storage space, etc.) during background (or deferred) processing. The disclosed techniques employ one or more extent copy trackers that can be created during processing of a transaction, while I/O request from host computers are suspended. The extent copy trackers are configured to perform some or all of the certain operations in the background, after the transaction has been committed and/or the processing of the transaction has been completed. By performing such operations during background processing, a processing time required to complete the snapshot transaction is reduced, thereby reducing latency in the resumption of the I/O requests from the host computers.

Abstract: Techniques for generating merge-friendly sequential IO patterns in shared logger page descriptor (PD) tiers. The techniques can be employed in an active-active clustered system that includes a primary storage node, a secondary storage node, a logger shared between the primary and secondary storage nodes, and a storage device such as a non-volatile memory (NVM) device. The techniques can include allocating at least a first trunk and a second trunk in a shared PD tier of the logger, sequentially writing PD metadata and/or data by the primary storage node and the secondary storage node to the first trunk and the second trunk, respectively, merging the PD metadata/data units sequentially written to each respective trunk together to obtain PD metadata/data having an increased size up to the size of the respective trunks, and storing the merged PD metadata/data to the NVM device.

Abstract: Techniques for generating merge-friendly sequential IO patterns in shared logger page descriptor (PD) tiers. The techniques can be employed in an active-active clustered system that includes a primary storage node, a secondary storage node, a logger shared between the primary and secondary storage nodes, and a storage device such as a non-volatile memory (NVM) device. The techniques can include allocating at least a first trunk and a second trunk in a shared PD tier of the logger, sequentially writing PD metadata and/or data by the primary storage node and the secondary storage node to the first trunk and the second trunk, respectively, merging the PD metadata/data units sequentially written to each respective trunk together to obtain PD metadata/data having an increased size up to the size of the respective trunks, and storing the merged PD metadata/data to the NVM device.

Abstract: A data storage system in which a transaction is generated that indicates at least one data block of a logical volume to be written to non-volatile data storage of a data, and in which the logical volume is accessible to multiple nodes in the data storage system. A system-wide lock is obtained for each data block indicated by the transaction. A new generation identifier is then created that is equal to a last transaction identifier that was created and stored during processing of a previously completed transaction. Each data block indicated by the transaction is stored into the non-volatile data storage of the data storage system together with the new generation identifier and the last transaction identifier is updated before each system-wide lock on each data block indicated by the transaction is released.

Abstract: A data storage system in which a transaction is generated that indicates at least one data block of a logical volume to be written to non-volatile data storage of a data, and in which the logical volume is accessible to multiple nodes in the data storage system. A system-wide lock is obtained for each data block indicated by the transaction. A new generation identifier is then created that is equal to a last transaction identifier that was created and stored during processing of a previously completed transaction. Each data block indicated by the transaction is stored into the non-volatile data storage of the data storage system together with the new generation identifier and the last transaction identifier is updated before each system-wide lock on each data block indicated by the transaction is released.

Abstract: Disclosed herein are techniques for use in managing data storage. For example, in one embodiment, the techniques comprise determining a size of the write request. The size of the write request equating to half or more non-parity data portions in a full stripe of data but less than all non-parity data portions in the full stripe.

Abstract: Disclosed herein are techniques for use in managing data storage. For example, in one embodiment, the techniques comprise determining a size of the write request. The size of the write request equating to half or more non-parity data portions in a full stripe of data but less than all non-parity data portions in the full stripe.

Abstract: A technique for maintaining RAID (redundant array of independent disks) configuration metadata across multiple SPs (storage processors) includes receiving a change request by a controller within a first SP, writing, by the first SP, a RAID configuration change described by the change request to a persistent intent log, and informing a second SP that the intent log has been written. The second SP, upon being informed of the write to the intent log, reads the RAID configuration change from the intent log and writes the RAID configuration change to a persistent configuration database. In this manner, the first SP and the second SP both receive the RAID configuration change and thus are both equipped to service reads and writes directed to a affected RAID storage.

Abstract: A technique configures data storage equipment to (i) allow host I/O operations to start on storage devices while a credit tally is less than a predefined credit quota and (ii) block host I/O operations from starting on the storage devices while the tally is greater than the quota. The technique further involves, while a rebuild procedure is not being performed on the storage devices, (i) allocating host I/O credits at equal weight to the tally upon starting host I/O operations and (ii) de-allocating the credits at equal weight from the tally upon completion of the operations. The technique further involves, while the rebuild procedure is being performed on the storage devices, (i) allocating host I/O credits at greater than equal weight to the tally upon starting host I/O operations and (ii) de-allocating the credits at greater than equal weight from the tally upon completion of the operations.