US 11,080,245 B2Granted

Multi-tier cloud file system

AssigneeDaStratum, Inc.

InventorsVijay Mohan Deshmukh, Kapil Kumar, Anil Kumar Sharma, Sudheer K. Rao Miryala

Life of this patent

Estimating the term…

Loading patent…

Abstract

The technology disclosed relates to a STRADL file system that transparently deploys file blocks across multiple tiers of storage. In a cloud-based storage platform, multiple storage tiers host data via file system APIs. This includes a volatile storage (VS) tier with a VS API, a reliable non-volatile storage (RNVS) tier with a RNVS API, and a highly reliable non-volatile storage (HRNVS) tier with a HRNVS API. The STRADL file system provides an intermediary file system API that presents to a host system a single interface and translates get, put, and other file system requests into commands compatible with the VS API, the RNVS API, and the HRNVS API, without host system awareness of which of the multiple tiers holds requested data and metadata.

Claims19

Dependent claims

A file system running on a node that transparently deploys file blocks across multiple tiers of storage, with flushing and synchronizing of data from volatile to first type and second type non-volatile storage, the system comprising one or more processors and memory storing instructions that, when executed by a processor of the one or more processors implement:

storing in multiple tiers of storage host data received from and provided to a host system via file system application programming interfaces (abbreviated APIs), the multiple tiers of storage including:
a volatile storage (abbreviated VS) tier with a VS API,
a first type non-volatile storage (abbreviated RNVS) tier with a RNVS API, and exhibiting a first reliability criterion, the first reliability criterion being greater than a reliability of the volatile storage;
and
a second type non-volatile storage (abbreviated HRNVS) tier with a HRNVS API, and exhibiting a second reliability criterion, the second reliability criterion being greater than the first reliability criterion, and
tracking staleness of each data block in the volatile storage tier that already has been copied to the first type non-volatile storage tier, and when a data block staleness has exceeded a criterion, expiring the data block from the volatile storage tier and updating a block table to indicate that the data block is to be retrieved from the first type non-volatile storage tier;
presenting to a host system a single interface for receiving data from the host for storage into the multiple tiers of storage or providing data retrieved from the multiple tiers of storage;
translating file system requests received via different access protocols into commands compatible with the VS API, the RNVS API, and the HRNVS API, without host system awareness of which of the multiple tiers holds requested data and metadata;
writing data received from the host via the single interface and destined for a file, by sending a message to the volatile storage tier and marking the data to be committed to the first type non-volatile storage tier;
periodically committing at least some data from the volatile storage tier to the first type non-volatile storage tier by writing received messages into a second dataspace while a first dataspace having reached a consistency point is emptied to the first type non-volatile storage tier;
and
periodically synchronizing at least some data from the first type non-volatile storage tier to the second type non-volatile storage tier by copying data detected as changed from the first type non-volatile storage tier to corresponding data in the second type non-volatile storage tier.

9 more elements

A method of transparently deploying file blocks across multiple tiers of storage, with flushing and synchronizing of data from volatile to first type and second type non-volatile storage, the method including:

hosting data received from and provided to a host system across multiple tiers of storage via file system application programming interfaces (abbreviated APIs), the multiple tiers of storage including:
a volatile storage (abbreviated VS) tier with a VS API,
a first type non-volatile storage (abbreviated RNVS) tier with a RNVS API, and exhibiting a first reliability criterion, the first reliability criterion being greater than a reliability of the volatile storage, and
a second type non-volatile storage (abbreviated HRNVS) tier with a HRNVS API, and exhibiting a second reliability criterion, the second reliability criterion being greater than the first reliability criterion;
tracking staleness of each data block in the volatile storage tier that already has been copied to the first type non-volatile storage tier, and when a data block staleness has exceeded a criterion, expiring the data block from the volatile storage tier and updating a block table to indicate that the data block into be retrieved from the first type non-volatile storage tier;
presenting to a host system, a single interface for receiving data from the host for storage into the multiple tiers of storage or providing data retrieved from the multiple tiers of storage;
translating file system requests received via different access protocols into commands compatible with the VS API, the RNVS API, and the HRNVS API, without host system awareness of which of the multiple tiers holds requested data and metadata;
writing data received from the host via the single interface and destined for a file, by sending a message to the volatile storage tier and marking the data to be committed to the first type non-volatile storage tier;
periodically committing at least some data from the volatile storage tier to the first type non-volatile storage tier;
and
periodically synchronizing data from the first type non-volatile storage tier to the second type non-volatile storage tier.

8 more elements

A non-transitory computer readable storage medium impressed with computer program instructions, the instructions, when executed on a processor, implement a file system that transparently deploys file blocks across multiple tiers of storage, with flushing and synchronizing of data from volatile to reliable and highly reliable non-volatile storage, the file system configurable to carry out a method comprising:

hosting data received from and provided to a host system across multiple tiers of storage via file system application programming interfaces (abbreviated APIs), including:
a volatile storage (abbreviated VS) tier with a VS API,
a first type non-volatile storage (abbreviated RNVS) tier with a RNVS API, and exhibiting a first reliability criterion, the first reliability criterion being greater than a reliability of the volatile storage, and
a second type non-volatile storage (abbreviated HRNVS) tier with a HRNVS API, and exhibiting a second reliability criterion, the second reliability criterion being greater than the first reliability criterion;
tracking staleness of each data block in the volatile storage tier that already has been copied to the first type non-volatile storage tier, and when a data block staleness has exceeded a criterion, expiring the data block from the volatile storage tier and updating a block table to indicate that the data block is to be retrieved from the first type non-volatile storage tier;
presenting to a host system a single interface for receiving data from the host for storage into the multiple tiers of storage or providing data retrieved from the multiple tiers of storage;
translating file system requests received via different access protocols into commands compatible with the VS API, the RNVS API, and the HRNVS API, without host system awareness of which of the multiple tiers holds requested data and metadata;
writing data received from the host via the single interface and destined for a file, by sending a message to the volatile storage tier and marking the data to be committed to the first type non-volatile storage tier;
periodically committing at least some data from the volatile storage tier to the first type non-volatile storage tier;
and
periodically synchronizing at least some data from the first type non-volatile storage tier to the second type non-volatile storage tier.

8 more elements

Dependencies are inferred from the claim text.

Facts

Application: 15/893,393Filed 9 Feb 2018 · us provisional application
Priority: 10 Feb 2017
Published: US 2018/0232395 A116 Aug 2018
Granted: 3 Aug 2021
Term ends: Not estimatedThe source records don’t support an estimate.

Classification12 codes

G06F 16/183
Implemented using Network-attached Storage [NAS] architecture: provision of network file services by network file servers, e.g. by using NFS, CIFS
G06F 3/0605
Improving or facilitating administration, e.g. storage management: by facilitating the interaction with a user or administrator
G06F 3/0617
Improving the reliability of storage systems: in relation to availability
G06F 3/0643
Organizing or formatting or addressing of data: management of files

Family

Application62/457,773Us provisional application · filed 10 Feb 2017
Application62/530,022Us provisional application · filed 7 Jul 2017
Application62/530,026Us provisional application · filed 7 Jul 2017
Application62/530,028Us provisional application · filed 7 Jul 2017
Application62/530,031Us provisional application · filed 7 Jul 2017
US 2018/0232395 A1Pre-grant publication · published 16 Aug 2018
US 11,080,245 B2This patent

From the US filing history. Foreign family members aren’t listed.