Abstract: A Data Storage Device (DSD) includes a Non-Volatile Memory (NVM) for storing data and a first processor configured to execute a firmware for retrieving data from the NVM and storing data in the NVM. A second processor of the DSD executes an application Operating System (OS) to interface with the first processor. The second processor sends a command to the first processor using the application OS to retrieve data from the NVM or store data in the NVM.

Abstract: A data storage system includes a plurality of Data Storage Devices (DSDs). A write command is sent to each DSD of the plurality of DSDs to each store one or more erasure coded shards of an overprovisioned number of shards. The overprovisioned number of shards is generated from an erasure coding on data to provide at least a predetermined level of data reliability. Write complete indications are received for a threshold number of shards less than the overprovisioned number of shards, with each write complete indication indicating that one or more shards of the overprovisioned number of shards has been stored in a DSD. It is determined that the data has been written with at least the predetermined level of data reliability after receiving write complete indications for the threshold number of shards, but before receiving write complete indications for all of the overprovisioned number of shards.

Abstract: A collective latency indicator is determined that is associated with a latency in retrieving multiple erasure coded shards generated from an erasure coding on initial data. The collective latency indicator is compared to a latency limit, and a number of erasure coded shards to retrieve is adjusted based on the comparison of the collective latency indicator to the latency limit.

Abstract: An individual latency indicator is determined for each Data Storage Device (DSD) or memory portion of a DSD storing one or more erasure coded shards generated from an erasure coding on initial data. Each individual latency indicator is associated with a latency in retrieving an erasure coded shard stored in a respective DSD or memory portion. At least one collective latency indicator is determined using determined individual latency indicators, with the at least one collective latency indicator being associated with a latency in retrieving multiple erasure coded shards. The at least one collective latency indicator is compared to a latency limit, and a subset of erasure coded shards is selected to retrieve based on the comparison of the at least one collective latency indicator to the latency limit.

Abstract: Embodiments of network devices for content distribution are described. In some embodiments, an edge network device integrates network coding for content distribution with erasure coding for data storage. Embodiments of methods of integrating network coding and erasure coding are also disclosed. In some embodiments, an edge network device can determine content distribution and storage for content based on one or more penalty functions that assess storage capacity, computational power, user demand, and/or network bandwidth for optimal resource usage. In some embodiments, an edge network device creates fragments of content and transmits a subset of the fragments for early distribution. In response to a user request for the content, the edge network device can transmit the remaining fragments to the user device for the user device to reconstruct the original content.

Abstract: A Data Storage Device (DSD) includes a Non-Volatile Memory (NVM) for storing data, a network interface for communicating on a network, and a processor. According to one aspect, a command is received via the network interface for storing data in the NVM. A data writing methodology is dynamically selected for how the data will be physically stored in the NVM from among a plurality of data writing methodologies based at least in part on whether the command is to be performed using a first interface or a second interface for accessing data in the NVM. According to another aspect, respective storage capacities of the NVM and/or respective rates of consumption of different types of storage media in the NVM are assigned to the first interface and to the second interface.

Abstract: At least one attribute defined by a host is used to identify data and/or a location for a destination portion for relocating data from a source portion to the destination portion. The data is relocated from the source portion to the destination portion in accordance with the identification of the data to be relocated and/or the location for the destination portion, and it is determined if a change was made to relevant data stored in the source portion while relocating the data from the source portion to the destination portion. If a change was made to relevant data stored in the source portion while relocating the data to the destination portion, the changed relevant data is relocated from the source portion to the destination portion.

Abstract: Managing data stored in at least one Data Storage Device (DSD) includes generating a Linear Tape File System (LTFS) write or read command including an LTFS block address. The generated LTFS command is for writing or reading data in an LTFS data partition, writing or reading metadata in the LTFS data partition, or writing or reading metadata in an LTFS index partition. The LTFS block address is translated to a device address for the at least one DSD using state metadata representing a state of the LTFS data partition and/or a state of the LTFS index partition. The data or the metadata is written or read in the at least one DSD at the device address.

Abstract: A Data Storage Device (DSD) includes a first memory for storing data and a Storage Class Memory (SCM) for storing data. The SCM has at least one characteristic of being faster than the first memory in storing data, using less power to store data than the first memory, and providing a greater usable life than the first memory for repeatedly storing data in a same memory location. At least a portion of the SCM is allocated or reserved for use by a host, and logical addresses assigned to the SCM are mapped to device addresses of the first memory identifying locations for storing data in the first memory. The host is provided with an indication of the logical addresses assigned to the SCM to allow the host to retrieve data from and store data in the DSD or to directly access data using the logical addresses assigned to the SCM.

Abstract: A write command is received to store data in a Data Storage Device (DSD). At least one of a Non-Volatile Random Access Memory (NVRAM) and a Storage Class Memory (SCM) is selected for storing the data of the write command based on a number of previously received write commands indicating an address of the write command or a priority of the write command. The SCM has at least one characteristic of being faster than the NVRAM in storing data, using less power to store data, and providing a greater usable life for repeatedly storing data in a same memory location. In one example, at least a portion of the SCM is allocated for use by a host. Logical addresses assigned to the SCM are mapped to device addresses of the NVRAM. The host is provided with an indication of the logical addresses assigned to the SCM.

Abstract: An object based storage cluster includes at least one Data Storage Device (DSD) with a plurality of media portions for storing data. Media mapping information is received from the at least one DSD with the media mapping information indicating addresses assigned to each media portion of the plurality of media portions. Each media portion of the plurality of media portions is identified as a separate Object Storage Device (OSD) in the object based storage cluster using the media mapping information.

Abstract: An individual latency indicator is determined for each Data Storage Device (DSD) or memory portion of a DSD storing one or more erasure coded shards generated from an erasure coding on initial data. Each individual latency indicator is associated with a latency in retrieving an erasure coded shard stored in a respective DSD or memory portion. At least one collective latency indicator is determined using determined individual latency indicators, with the at least one collective latency indicator being associated with a latency in retrieving multiple erasure coded shards. The at least one collective latency indicator is compared to a latency limit, and a subset of erasure coded shards is selected to retrieve based on the comparison of the at least one collective latency indicator to the latency limit.

Abstract: A collective latency indicator is determined that is associated with a latency in retrieving multiple erasure coded shards generated from an erasure coding on initial data. The collective latency indicator is compared to a latency limit, and a number of erasure coded shards to retrieve is adjusted based on the comparison of the collective latency indicator to the latency limit.

Abstract: During a startup process of a host, a request is sent to a DSD to identify storage media of the DSD. Identification information is received from the DSD before executing a driver on the host for interfacing with the DSD. The identification information identifies a first storage media of the DSD in response to the request. A second storage media is later identified using the driver.

Abstract: A data storage device is disclosed comprising a volatile memory, a primary and a secondary non-volatile memory (NVM), and control circuitry coupled to the volatile memory and the primary and secondary NVM and configured to write first data to the volatile memory, write the first data from the volatile memory to the secondary NVM before writing the first data to the primary NVM, attempt to write the first data to the primary NVM, wherein, during the attempt to write the first data to the primary NVM, after a portion of the first data has been successfully written to the primary NVM, a corresponding portion of the first data is released from the secondary NVM.

Abstract: A data storage device is disclosed comprising a volatile memory, a primary and a first secondary non-volatile memory (NVM), and control circuitry coupled to the volatile memory and the primary and first secondary NVM and configured to (a) write metadata and user data associated with a host write command to the volatile memory; (b) write the user data to the primary NVM; (c) continue to write metadata associated with each of one or more host write commands to the volatile memory, and when a first condition is met, write metadata that has accumulated in the volatile memory to the first secondary NVM; and (d) repeat (c), and when a second condition is met, then write at least a portion of the metadata that has accumulated in the first secondary NVM or the volatile memory to the primary NVM.

Abstract: Managing data stored in at least one Data Storage Device (DSD) includes generating a Linear Tape File System (LTFS) write or read command including an LTFS block address. The generated LTFS command is for writing or reading data in an LTFS data partition, writing or reading metadata in the LTFS data partition, or writing or reading metadata in an LTFS index partition. The LTFS block address is translated to a device address for the at least one DSD using state metadata representing a state of the LTFS data partition and/or a state of the LTFS index partition. The data or the metadata is written or read in the at least one DSD at the device address.

Abstract: A Data Storage Device (DSD) includes a Non-Volatile Memory (NVM) for storing data, a network interface for communicating on a network, and a processor. According to one aspect, a command is received via the network interface for storing data in the NVM. A data writing methodology is dynamically selected for how the data will be physically stored in the NVM from among a plurality of data writing methodologies based at least in part on whether the command is to be performed using a first interface or a second interface for accessing data in the NVM. According to another aspect, respective storage capacities of the NVM and/or respective rates of consumption of different types of storage media in the NVM are assigned to the first interface and to the second interface.

Abstract: Managing data stored in at least one data storage device (DSD) of a computer system where the at least one DSD includes at least one disk for storing data. A Linear Tape File System (LTFS) write or read command is generated including an LTFS block address. The LTFS block address is translated to a device address for the at least one DSD and data on a disk of the at least one DSD is written or read at the device address.

Abstract: In operating a Data Storage Device (DSD) in communication with a host, a reported write command log is maintained that includes entries identifying pending write commands reported as completed to the host but whose data is not yet stored in at least one Non-Volatile Memory (NVM) of the DSD. The reported write command log is maintained to persist over power cycles. A write command is received from the host to store data in the at least one NVM and the data for the write command is buffered in a volatile memory of the DSD for storage in the at least one NVM. The reported write command log is updated to account for the write command as a pending write command reported as completed, and an indication is sent to the host reporting completion of the write command before completing storage of the data in the at least one NVM.