Abstract: A method for utilizing an object storage system (470) for storing and retrieving a volume of data, the volume of data including a plurality of data objects, the method includes the steps of accumulating the volume of data to an ingest area (474) provided within a non-taped-based storage medium; copying a first subset of the plurality of data objects to a first tape medium (472A); and copying a second subset of the plurality of data objects to a second tape medium (472B) that is independent of the first tape medium (472A).

Abstract: A nucleic acid storage system (100) that uses nanopore sequencing to read data values chemically embedded in oligonucleotides includes a membrane (102), a voltage source (108), and a nucleic acid strand (110). The membrane (102) has a plurality of nanopores (104) that are stacked upon one another in a multi-nanopore arrangement. The voltage source (108) is configured to direct voltage across the plurality of nanopores (104). The nucleic acid strand (110) including the oligonucleotides is threaded through each of the plurality of nanopores (104) within the membrane (102). A separate base signal (118) is generated from the nucleic acid strand (110) being threaded through each of the plurality of nanopores (104), and Recursive Neural Networks can be used to estimate a signal shape for each oligonucleotide. Recurrent Convolutional Neural Networks and noise predictive data detection algorithms can be used based on the estimated signal shapes to sequence the oligonucleotides.

Abstract: Nonvolatile data storage systems, methods, and devices are disclosed. In one example, a nonvolatile storage device includes a volatile memory, a controller electrically coupled to the volatile memory, a nonvolatile memory electrically coupled to the controller, and a backup power source electrically coupled to the controller, the volatile memory, and the nonvolatile memory. The controller is configured to read and write primary data from a primary host and mirrored data from a secondary host in the volatile memory. The backup power source is configured to store sufficient energy to power the nonvolatile storage device during a backup operation. The controller is configured to, in response to a backup signal, copy the primary data and the mirrored data stored in the volatile memory to the nonvolatile memory.

Abstract: A method for utilizing an object storage system (470) for storing and retrieving a volume of data, the volume of data including a plurality of data objects, the method includes the steps of accumulating the volume of data to an ingest area (474) provided within a non-taped-based storage medium; copying a first subset of the plurality of data objects to a first tape medium (472A); and copying a second subset of the plurality of data objects to a second tape medium (472B) that is independent of the first tape medium (472A).

Abstract: Nonvolatile data storage systems, methods, and devices are disclosed. In one example, a nonvolatile storage device includes a volatile memory, a controller electrically coupled to the volatile memory, a nonvolatile memory electrically coupled to the controller, and a backup power source electrically coupled to the controller, the volatile memory, and the nonvolatile memory. The controller is configured to read and write primary data from a primary host and mirrored data from a secondary host in the volatile memory. The backup power source is configured to store sufficient energy to power the nonvolatile storage device during a backup operation. The controller is configured to, in response to a backup signal, copy the primary data and the mirrored data stored in the volatile memory to the nonvolatile memory.

Abstract: Example apparatus and methods identify files that are so small or so large that they compromise the efficient operation of a file system that uses re-assignable one-to-one inodes and inode numbers. Small files are aggregated into collections of files and large files are subdivided into collections of smaller files. Information for locating multiple related files with fewer lookups is generated and stored in a folder. An inode having a new type of inode number is then created. The new type of inode number encodes information for finding the folder. The encoded information may include a folder identifier that acts as a primary key into a database that is configured to locate a member of the aggregated or subdivided files with a single lookup. A filter file system may be updated with the new inode. The new inode number is unique within the filter file system and may not be re-assigned.

Abstract: Systems, methods, and circuitries are provided for supporting multiple concurrent thread access to a storage array. In one example, a storage array includes a plurality of storage devices each divided into at least N subdivisions. A volume includes a set of subdivisions including a subdivision in each of M different storage devices. Memory management circuitry receives first data and second data for storing in the storage array and selects a first volume for storing the first data and a second volume for storing the second data. The second volume includes a different set of subdivisions than the first volume. The processor uses a first set of processor threads to process and store the first data in the first volume and uses a second set of processor threads to, concurrent with the processing and storing of the first data, process and store the second data in the second volume.

Abstract: Adaptive pre-fetching devices can predict data placement to improve the operating and/or electrical efficiency of a data storage system. A future input/output operation can be predicted from a current input/output operation, the state of the data storage apparatus, relationships between data currently being processed and data previously processed, or other factors. The apparatus and methods can improve data storage efficiency by selectively pre-fetching data, relocating data on the data storage apparatus, the backing storage, or within a plurality of data storage apparatus based on working set predictors to reduce cache misses or outperform fetch processes from the backing storage.

Abstract: Systems, methods, and circuitries are provided for supporting multiple concurrent thread access to a storage array. In one example, a storage array includes a plurality of storage devices each divided into at least N subdivisions. A volume includes a set of subdivisions including a subdivision in each of M different storage devices in the plurality of storage devices. Memory management circuitry is configured to receive first data and second data for storing in the storage array and select a first volume for storing the first data and a second volume for storing the second data. The second volume includes a different set of subdivisions than the first volume. The processor is configured to use a first set of processor threads to process and store the first data in the first volume and use a second set of processor threads to, concurrent with the processing and storing of the first data, process and store the second data in the second volume.

Abstract: Embodiments include a data aware deduplicating object store. The data aware deduplicating data store includes a consistent hashing logic that manages a consistent hashing architecture for the object store. The consistent hashing architecture includes a metadata ring and a bulk ring. The consistent hashing architecture may be a multiple ring architecture comprising a metadata ring and two or more bulk rings. A bulk ring may include a key/value (k/v) data store, where a k/v data store stores a shard of an index and a reference count that facilitates the individual approach to garbage collection or data reclamation. The data aware deduplicating data store also includes a deduplication logic that provides data deduplication for data to be stored in the object store. The deduplication logic performs variable length deduplication and provides a shared nothing approach.

Abstract: Embodiments provide adaptive storage management for optimizing multi-tier data storage. A storage manager may interact with storage decision advisors. The manager may adaptively make storage management decisions (e.g., flush, evict, recall, delete) after considering recommendations from and the credibility of the storage decision advisors. The manager may update the credibility of storage decision advisors based on how their recommendations affected optimization. The manager may adaptively choose when to rebalance or reconfigure the credibility of the storage decision advisors. Storage decision advisors may themselves be adaptive. Storage decision advisors may examine credibility feedback from the storage manager to determine which recommendations were useful and which were not. Storage decision advisors may then change when they will make a recommendation, when they will abstain from making a recommendation, the type of recommendation provided, or other behavior.

Abstract: Example apparatus and methods identify files that are so small or so large that they compromise the efficient operation of a file system that uses re-assignable one-to-one inodes and inode numbers. Small files are aggregated into collections of files and large files are subdivided into collections of smaller files. Information for locating multiple related files with fewer lookups is generated and stored in a folder. An inode having a new type of inode number is then created. The new type of inode number encodes information for finding the folder. The encoded information may include a folder identifier that acts as a primary key into a database that is configured to locate a member of the aggregated or subdivided files with a single lookup. A filter file system may be updated with the new inode. The new inode number is unique within the filter file system and may not be re-assigned.

Abstract: Example methods and apparatus asynchronously verify data stored in a cloud data storage system. One embodiment comprises a monitoring circuit that determines if a data auditing condition associated with a cloud storage system or archived data stored in the cloud storage system has been met, a metadata mirror circuit that controls a metadata mirror to provide metadata, including a first checksum, associated with the archived data to the apparatus, a checksum circuit that computes a second checksum based on the archived data, a verification circuit that generates an audit of the first checksum and the second checksum by comparing the second checksum with the first checksum, and a reporting circuit that generates a log of the audit, that provides the log to the data storage system, and that provides a notification of a data integrity failure to a user associated with the archived data.

Abstract: Example apparatus and methods identify files that are so small or so large that they compromise the efficient operation of a file system that uses re-assignable one-to-one inodes and inode numbers. Small files are aggregated into collections of files and large files are subdivided into collections of smaller files. Information for locating multiple related files with fewer lookups is generated and stored in a folder. An inode having a new type of inode number is then created. The new type of inode number encodes information for finding the folder. The encoded information may include a folder identifier that acts as a primary key into a database that is configured to locate a member of the aggregated or subdivided files with a single lookup. A filter file system may be updated with the new inode. The new inode number is unique within the filter file system and may not be re-assigned.

Abstract: Example apparatus and methods provide a file system that stores files in multiple different logical units. The logical units are associated with different classes of devices. The file system interacts with the logical units through block-based interfaces. The file system is a single file system that spans the multiple logical units. The multiple different logical units include data storage devices for which the file system manages block storage allocation and an object storage system that manages its own block storage allocation rather than having the file system manage its block storage allocation. The file system may maintain a single namespace, hierarchy, or directory structure for the multiple logical units. The object storage system may protect files using redundant copies, erasure codes, or other approaches. An archive process may selectively move files from other devices to the object storage system and leave a symbolic link behind.

Abstract: Adaptive pre-fetching devices can predict data placement to improve the operating and/or electrical efficiency of a data storage system. A future input/output operation can be predicted from a current input/output operation, the state of the data storage apparatus, relationships between data currently being processed and data previously processed, or other factors. The apparatus and methods can improve data storage efficiency by selectively pre-fetching data, relocating data on the data storage apparatus, the backing storage, or within a plurality of data storage apparatus based on working set predictors to reduce cache misses or outperform fetch processes from the backing storage.

Abstract: Example apparatus and methods provide a log structured block device for a hard disk drive (HDD). Data that is to be stored on an HDD is serialized and written as a series of data blocks using a sequential write. Information about where individual data blocks were supposed to be written (e.g., actual address, neighboring data blocks), where data blocks were actually written, and how often data blocks are accessed is maintained. During garbage collection, data blocks that are being accessed with similar frequencies may be relocated together, with the most frequently accessed (e.g., hottest) data blocks migrating to the outer cylinders of the disk and the least frequently accessed (e.g., coldest) data blocks migrating to the inner cylinders. Blocks stored in the same temperature regions that were intended to be located together when written may be repositioned to facilitate sequential reads.

Abstract: Storage conditioning for a data storage system having D data storage devices (DSDs) is provided. E erasure codes (ECs) for an object are stored in the system, D>E. A map of d E-sized vectors of the D DSDs is produced. A DSD appears in e vectors. The ratio d/e is the reduced form of D/E. A hash value is produced for the object. A destination vector for storing the ECs is selected using the hash value according to a pre-determined, substantially uniform distribution. A compromised vector affected by a first DSD becoming unable to store ECs is identified. An intact vector that is not affected by the first DSD is identified. A complete set of ECs is produced from an incomplete set of ECs in the compromised vector and is distributed to the intact vector then copied back when the compromised vector is once again intact.

Abstract: Example methods and apparatus asynchronously verify data stored in a cloud data storage system. One embodiment comprises a monitoring circuit that determines if a data auditing condition associated with a cloud storage system or archived data stored in the cloud storage system has been met, a metadata mirror circuit that controls a metadata mirror to provide metadata, including a first checksum, associated with the archived data to the apparatus, a checksum circuit that computes a second checksum based on the archived data, a verification circuit that generates an audit of the first checksum and the second checksum by comparing the second checksum with the first checksum, and a reporting circuit that generates a log of the audit, that provides the log to the data storage system, and that provides a notification of a data integrity failure to a user associated with the archived data.

Abstract: Embodiments provide adaptive storage management for optimizing multi-tier data storage. A storage manager may interact with storage decision advisors. The manager may adaptively make storage management decisions (e.g., flush, evict, recall, delete) after considering recommendations from and the credibility of the storage decision advisors. The manager may update the credibility of storage decision advisors based on how their recommendations affected optimization. The manager may adaptively choose when to rebalance or reconfigure the credibility of the storage decision advisors. Storage decision advisors may themselves be adaptive. Storage decision advisors may examine credibility feedback from the storage manager to determine which recommendations were useful and which were not. Storage decision advisors may then change when they will make a recommendation, when they will abstain from making a recommendation, the type of recommendation provided, or other behavior.