Data can be transmitted and represented by signal gaps in a transmission, the gaps having various attributes. In various examples, data points are encoded and represented by the attributes of said signal gaps. Various attributes of such gaps, including duration, pattern, quantity, time, and/or coordination with a gap in another signal can represent data.

Implementations disclosed herein include a method comprising receiving a TRIM request for a media cache in a storage media from a host, determining whether a TRIM range in the TRIM request overlaps with an active operation, invalidating the TRIM range responsive to determining that the TRIM range does not overlap with an active operation, and inserting at least one null node in the media cache. The method may comprise receiving a host read request, performing a media cache search for a read LBA range, and determining where data is located. If all the data is located in the media cache, the system reads from the media cache. If the data is located in a null node, patterning for the null node occurs. If the data is located partially in the main store, the media cache, or a null node, the data may be read, combined, and returned to the host.

Implementations disclosed herein include a method comprising receiving a TRIM request for a media cache in a storage media from a host, determining whether a TRIM range in the TRIM request overlaps with an active operation, invalidating the TRIM range responsive to determining that the TRIM range does not overlap with an active operation, and inserting at least one null node in the media cache. The method may comprise receiving a host read request, performing a media cache search for a read LBA range, and determining where data is located. If all the data is located in the media cache, the system reads from the media cache. If the data is located in a null node, patterning for the null node occurs. If the data is located partially in the main store, the media cache, or a null node, the data may be read, combined, and returned to the host.

A system includes a read/write module and a caching module. The read/write module is configured to access a first portion of a recording surface of a rotating storage device. Data is stored on the first portion of the recording surface of the rotating storage device at a first density. The caching module is configured to cache data on a second portion of the recording surface of the rotating storage device at a second density. The second portion of the recording surface of the rotating storage device is separate from the first portion of the recording surface of the rotating storage device. The second density is less than the first density.

Data can be encoded in physical medium and represented by shapes having many various physical attributes. In various examples, data points are encoded and represented by the physical shape, color, size, and/or structure of objects. In one embodiment, holes in memory surface substrates represent data. Various attributes of such holes, including depth, profile size, profile shape, and/or angle can represent data.

Systems and methods for maximizing shingled magnetic recording (SMR) drive capacity are described. In one embodiment, the SMR drive may include a main store to store user-accessible data, a media cache and media scratchpad to store internal data temporarily for internal operations, and a storage controller to process read and write requests. In some cases, the main store comprises a shingled media partition and an unshingled media partition. The storage controller may designate one or more data tracks from the shingled media partition as temporary data track guard bands. In some embodiments, a track range is selected based at least in part on at least one of an amount of data in the media cache, a size of the new data in the media cache, and an association between the new data in the media cache and data currently stored within the selected track range.

According to the embodiment, an HDC receives a plurality of data segments from a host, and executes generation and addition of a first code and output of a data segment to which the first code is added to each data segment. An HDC calculates exclusive OR with respect to the first codes, and outputs obtained first information. The RWC performs data conversion and calculation of exclusive OR on the plurality of data segments to which the first code is added, and outputs the plurality of data segments after the data conversion and a track parity obtained by the calculation of the exclusive OR. The RWC acquires the first code from the plurality of data segments. The RWC calculates exclusive OR with respect to a group of the second codes which are the acquired first codes to acquire second information. The RWC compares the first information with the second information.

A storage system includes a final level cache (FLC) module coupled to a storage medium. The storage medium includes a bulk storage portion having a higher data density than a cache storage portion. The cache storage portion is configured as an FLC cache accessed by the FLC module prior to accessing the bulk storage portion. The FLC module receives a request for data from a processor coupled to one or more levels of cache that are separate from the FLC cache. The processor generates the request if the data is not cached in the one or more levels of cache. The FLC module determines whether the data requested is cached in the FLC cache, retrieves the data from the FLC cache if the data is cached in the FLC cache, and retrieves the data from the bulk storage portion if the data is not cached in the FLC cache.

A data storage device includes one or more storage media that include multiple physical storage locations. The device also includes at least one cache memory having a logical space that includes a plurality of separately managed logical block address (LBA) ranges. Additionally, a controller is included in the device. The controller is configured to receive data extents addressed by a first LBA and a logical block count. The controller is also configured to identify at least one separately managed LBA range of the plurality of separately managed LBA ranges in the at least one cache memory based on LBAs associated with at least some of the received data extents. The controller stores the at least some of the received data extents in substantially monotonically increasing LBA order in at least one physical storage location, of the at least one cache memory, assigned to the identified at least one LBA range.

Implementations disclosed herein include a method comprising receiving a TRIM request for a media cache in a storage media from a host, determining whether a TRIM range in the TRIM request overlaps with an active operation, invalidating the TRIM range responsive to determining that the TRIM range does not overlap with an active operation, and inserting at least one null node in the media cache. The method may comprise receiving a host read request, performing a media cache search for a read LBA range, and determining where data is located. If all the data is located in the media cache, the system reads from the media cache. If the data is located in a null node, patterning for the null node occurs. If the data is located partially in the main store, the media cache, or a null node, the data may be read, combined, and returned to the host.