Western Digital Technologies, Inc.

Hgst Netherlands, B.v.

Samsung Electronics Co., Ltd.

Sandisk Technologies Inc.

Adam Manzanares

Cyril Guyot

Viacheslav Anatolyevich Dubeyko

Zvonimir Z Bandic

Lluis Pamies-Juarez

Erhard Theodor Schreck

Luiz M Franca-Neto

Bruno Jean Marchon

Dejan Vucinic

Robert Eugeniu Mateescu

Minghai Qin

Chao Sun

Koen De Keyser

Frank R Chu

Yuval Cassuto

Mark Christiaens

Mohammed Ghiath Khatib

Filip Blagojevic

Bridget Molly Davis

Qirui Yang

Devasena Inupakutika

Viacheslav Dubeyko

Noah Watkins

One or more embodiments of the present disclosure describe a storage system comprising a first storage medium, a second storage medium, and a controller configured to communicate with the first storage medium and the second storage medium. The controller is configured to receive a first request generated by a process associated with first data; determine that the first data is stored in the first storage medium; generate a signal based on the controller being configured to determine; identify a criterion based on the signal; select, based on the criterion, at least one of a first procedure or a second procedure for loading second data from the second storage medium to the first storage medium; and output the second data based on a second request generated by the process for the second data.

Systems and methods for managing a storage system

System and method of verifying validity of a metadata modification request to prevent improper metadata operations. During initialization of a volume in a storage device and once a metadata area is reserved for a metadata structure, information characterizing the metadata structure and metadata area is stored in the storage device, which may be in the form of an area legend composed of descriptors such as a magic signature, a node size, a clump size of reservation, and extent of the metadata area. Responsive to a request for operating on metadata, relevant information provided in the request is verified against the stored characteristic information. If the verification discovers an inconsistency between the information provided in the request and the stored characteristic information, the request modification is treated as invalid and blocked from operation.

Generalized verification scheme for safe metadata modification

A verification architecture described according to embodiments of the present invention validates changes made to metadata and may comprise one or more subsystems and phases. According to some embodiments, the 'mkfs' volume creation utility works in cooperation with the device driver to create a file system volume by means of reservation and initialization space for metadata structures inside the device's partition that is reserved for the specific file system volume. The storage device uses a verified area legend when checking write requests after the file system volume has been created. The verified area legends may be stored in a dedicated partition or inside the master boot record (MBR) or Globally Unique Identifier (GUID) partition table (GPT) or special memory chip (NAND flash, for example). Write requests that overlap with any extent of reserved metadata area must be verified to prevent metadata corruption.

Write operation verification method and apparatus

Modifying a page stored in a non-volatile storage includes receiving one or more requests to modify data stored in the page with new data. One or more lines are identified in the page that include data to be modified by the one or more requests. The identified one or more lines correspond to one or more respective byte ranges each of a predetermined size in the page. Encoded data is created based on the new data and respective locations of the one or more identified lines in the page. The encoded data is cached, and at least a portion of the cached encoded data is used to rewrite the page in the non-volatile storage to include at least a portion of the new data.

Page modification encoding and caching

A write request is received to write byte-addressable data corresponding to a first entry of a plurality of entries in a page table, and the byte-addressable data is written in a buffer of a host memory. A read request is received to read byte-addressable data corresponding to a second entry of the plurality of entries in the page table, and a read command is sent to a device using a memory device interface to read the byte-addressable data from a Storage Class Memory (SCM) of the device. According to another aspect, control circuitry of the device uses a block device interface for receiving commands from a host to read and write data in blocks in the SCM. The control circuitry also uses a memory device interface for receiving read commands from the host to read byte-addressable data from the SCM.

Storage class memory access

A Data Storage Device (DSD) includes a memory and a non-volatile storage. Data related to one or more write requests is received in a write buffer of the memory from a host to modify a file system volume stored in a file system volume area of the non-volatile storage. The data related to the one or more write requests is de-staged into the file system volume area in at least one block to be modified in the file system volume by the one or more write requests. The data related to the one or more write requests is compiled into a backup slice in a backup buffer of the memory, and de-staged into a backup archive area of the non-volatile storage.

Data storage device backup

A device having a controller configured to interface with a host, a storage class memory configured to interface with the controller and a flash memory configured to interface with the controller, wherein both the storage class memory and the flash memory are configured to store data, and wherein the controller is configured to separate the data according to latency critical data and non-latency critical data.

Quality of service aware storage class memory/NAND flash hybrid solid state drive

A method may include writing data to a hard drive. In some examples, the method may include receiving, by an extent allocator module, a command to write data. The command may include data and a logical block address (LBA) specified by the host. The method may also include mapping, by the extent allocator module, the LBA specified by the host to a drive LBA. The method may further include sending, from the extent allocator module, a command to write the data at the drive LBA.

Logical block address mapping for hard disk drives

Generalized write operations verification method

Metadata area legends are stored at a first location, such as a dedicated partition of a persistent data storage device (PDSD). The metadata area legends have a number of descriptors that describe a number of reserved metadata areas that lie at a second location that is logically separate from the first location, such as a regular partition of the PDSD. Requests to delete the metadata area legends, as well as requests to add new metadata area legends, can be verified to prevent the metadata area legends from being accidentally or maliciously changed.

Method of preventing metadata corruption by using a namespace and a method of verifying changes to the namespace

Small objects are efficiently stored with erasure codes by combining a small object with other small objects and/or large objects to form a single large object for chunking, and providing early notification of permanent storage to the sources of the objects to prevent small objects from becoming stale while waiting for additional objects to be combined.

Storage cluster and method that efficiently store small objects with erasure codes

The present disclosure relates to a system and methods of controlling a system of storage devices. In particular, the present disclosure relates to methods of controlling peak power and energy consumption in storage systems due to storage devices while maintaining data availability. The system implements a method for maintaining data availability in a storage subsystem by determining a plurality of storage devices to include in a fixed set of storage devices based on a fault tolerance system. The storage devices included in the fixed set are prevented from transitioning between RPM spin modes. The method further involves controlling peak power and energy consumed by the storage subsystem which may include transitioning the storage devices not included in the fixed set from a high RPM operational mode to a low RPM operational mode to reduce peak power and energy consumption.

Variable-RPM hard disk drive control

A head-assisted magnetic recording-shingled magnetic recording (HAMR-SMR) type storage device is described that includes a control module and one or more magnetic recording layers partitioned into zones. The control module is configured to write initial data beginning at an initial logical address of a zone. The initial logical address of the zone corresponds to an initial physical address of the zone. Responsive to receiving a command from a host associated with the HAMR-SMR type storage device to reset the zone and write subsequent data, the control module is further configured to reset the initial logical address of the zone to a subsequent physical address of the zone, and after resetting the initial logical address, write the subsequent data beginning at the initial logical address of the zone.

Growing community of inventors

San Jose, CA, United States of America

Adam Manzanares