Pure Storage, Inc.

Andrew R Bernat

Ethan L Miller

Timothy W Brennan

Peter E Kirkpatrick

Benjamin Scholbrock

Wei Tang

Ronald S Karr

Mark L McAuliffe

John Colgrove

Gordon James Coleman

Alan Stuart Driscoll

Grigori Inozemtsev

Neil A Vachharajani

Radek Aster

Iris McLeary

Damian Pablo Yurzola

Neil Buda Vachharajani

Zoltan DeWitt

Anthony Niven

Ganesh Ramanarayanan

Eric D Seppanen

Steve Hodgson

Malcolm Sharpe

Prakash Darji

James Cihla

Jungkeun Kim

Tsu-Hao Chang

Constantine P Sapuntzakis

Marco Sanvido

Christopher Golden

Kiron Vijayasankar

Matthew Paul Fay

Xiaohui Wang

John Roper

Mark Fay

Eric Kelly Blanchard

Yunpeng Duan

Phillip Hord

Pushkar Mahesh Shirali

Robert H Lee

Taher Vohra

Benjamin P Borowiec

Boris Feigin

Andrew Kleinerman

Jimmy Chi-Wai Chui

Brandon Davis

Ashish Karkare

Yijie Zhao

Alexandre Xavier Duchâteau

Conner Haffner

John Adler

Hari Kannan

Yuhong Mao

Logan Jennings

David Whitlock

Randy Zhao

Phil Hord

Thomas Holland

Runmin Wang

Alexandre Duchâteau

Dominique Brych

Gavin Paes

Nicholas George Psaki

Zoltan Dewitt

Caleb Gum

Mark L Mcauliffe

Determining remaining hardware life in a storage system, including: receiving data about a plurality of hardware components including data describing the usage of each hardware component and the state of each hardware component; analyzing the data to determine a remaining hardware life for each hardware component in a group of components; and distributing workloads in order to balance wear amongst the hardware components in the group.

Determining remaining hardware life in a storage device

A command to relocate data from a first set of data blocks at the plurality of storage devices to a second set of data blocks while bypassing the storage controller is transmitted by the storage controller. The command includes address information associated with the second set of blocks to store the relocated data.

Optimized read request processing for relocated data

Recovering corrupted data through speculative bitflip and cross-validation, including altering a first data portion stored in a storage device, wherein the first data portion contains an error; calculating a hash value using the altered first data portion; comparing the hash value calculated using the altered first data portion to a stored hash value for the first data portion; and based on the comparing, determining whether the altering corrects the error in the first data portion.

Recover corrupted data through speculative bitflip and cross-validation

Data associated with a first set of managed flash storage devices of a cloud-based storage system is provided as an input to a machine learning model executed by a processing device that identifies one or more characteristics of the first set of managed flash storage devices from the data. A type of change associated with a second set of managed flash storage devices is determined by the machine learning model based on a comparison of the one or more characteristics of the first set of managed flash storage devices and one or more characteristics of the second set of managed flash storage devices. The type of change associated with the second set of managed flash storage devices is provided to a cloud services provider of the cloud-based storage system.

Utilizing machine learning for processing of managed flash storage devices

A method for rebuilding data when changing erase block sizes in a storage system is provided. The method includes determining one or more erase blocks to be rebuilt and allocating one or more replacement erase blocks, wherein the one or more erase blocks and the one or more replacement erase blocks have differing erase block sizes. The method includes mapping logical addresses, for the one or more erase blocks, to the one or more replacement erase blocks and rebuilding the one or more erase blocks into the one or more replacement erase blocks, in accordance with the mapping.

Allocation of differing erase block sizes

Performing a tune-up procedure on a storage device including determining, during a boot process, that a first storage device is available for a tune-up procedure, wherein the tune-up procedure prepares the first storage device for use after being offline; reserving the first storage device to perform the tune-up procedure, wherein reserving the first storage device prevents another system from performing the tune-up procedure on the first storage device; and executing the tune-up procedure on the first storage device.

Efficient storage device tune-up

Selecting storage resources based on data characteristics, including: determining, for data that is stored within a storage system that includes multiple types of data storage, a storage type to use for the data, wherein: the data is associated with one more snapshots that are stored in the storage system, and the determination is based on whether the data that is stored in at least one volume in the storage system, wherein one storage type is selected if the data is stored in at least one volume and another storage type is selected if the data is not stored in at least one volume; and storing the data in a storage device associated with the determined storage type.

Selecting storage resources based on data characteristics

A method of using flash storage devices with different sized erase blocks is provided. The method includes allocating a plurality of erase blocks of heterogeneous erase block sizes to a RAID stripe, to form a tile pattern having the heterogeneous erase block sizes in the RAID stripe. The method includes writing the RAID stripe across the flash storage devices in accordance with the allocating, and stopping the writing the RAID stripe, responsive to contents of the RAID stripe reaching a threshold.

Pattern forming for heterogeneous erase blocks

Rekeying in a storage system, including: receiving a request to rekey a first storage location of a storage system, wherein the first storage location is associated with a first cryptographic key; acknowledging completion of the request to rekey the first storage location without re-encrypting data stored at the first storage location of the storage system; and mapping a second cryptographic key identified by the request to rekey to the first storage location of the storage system.

Instant rekey in a storage system

Data protection in a storage system that includes a plurality of Non-Volatile Memory Express ('NVMe') Solid State Drives (‘SSDs’), including: retrieving, from a plurality of NVMe SSDs (‘Non-Volatile Memory Express Solid State Drives’) of a storage system, one or more unencrypted shares of a master secret; reconstructing the master secret using the shares of the master secret; decrypting one or more encrypted device keys using the master secret; and using the decrypted device keys to perform a plurality of accesses to one or more of the NVMe SSDs.

Encrypting data in a storage device

A set of blocks of a storage device are allocated for storage of data, wherein the set of blocks of the storage device is selected based on a power requirement that is based on a number of partially programmed blocks stored in the cache. Subsequent data to be stored at the storage device is assigned to the set of blocks for storage at the storage device.

Allocation of blocks based on power loss protection

A storage system is provided. The storage system includes a plurality of non-volatile memory modules and a storage system controller. One or more non-volatile memory modules include a multiplane die. A processing device of the storage system controller is configured to determine that a number of planes of the multiplane die used simultaneously for accessing data should be changed. In response to determining that the number of planes the multiplane die used simultaneously for accessing data should be changed, the processing device is configured to move one or more portions from an existing erase block to a new erase block, the existing erase block being a different size than the new erase block.

Dynamic plane selection in data storage system

A storage array controller may receive data to be programmed to a solid-state storage device of a plurality of solid-state storage devices. The storage array controller may identify a type of the data and determine whether to program the data to a low latency portion of the solid-state storage device based on the type of the data. In response to determining to program the data to the low latency portion of the solid-state storage device, the storage array controller may program the data to the low latency portion of the solid-state storage device.

Programming frequently read data to low latency portions of a solid-state storage array

Periodically re-encrypting user data stored on a storage device, including: determining that data stored in a first location of a storage device is encrypted with a data encryption key that has been decommissioned; re-encrypting the data utilizing a current data encryption key; and writing the data that is encrypted utilizing the current data encryption key to a second location of the storage device.

Re-keying the contents of a storage device

A storage system has zones in solid-state storage memory, with power loss protection. The system identifies portions of data for processes that utilize power loss protection. The system determines to activate or deactivate power loss protection for the portions of data for the processes. The system tracks activation and deactivation of power loss protection in zones in the solid-state storage memory, in accordance with the portions of data having power loss protection activated or deactivated.

Intelligent power loss protection allocation

Growing community of inventors

Mountain View, CA, United States of America

Andrew R Bernat