Intelligent file system with transparent storage tiering

US2018349409A1 · US · A1

Patent metadata
FieldValue
Publication numberUS-2018349409-A1
Application numberUS-201816056085-A
CountryUS
Kind codeA1
Filing dateAug 6, 2018
Priority dateDec 15, 2014
Publication dateDec 6, 2018
Grant date

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

A file system manager implemented at a provider network identifies a storage device of a first group of storage devices of a provider network as an initial location of a file system object. Based on an access metric associated with the object, the file system manager initiates a transfer of contents of the object to a second storage device of a different storage device group, without receiving a client request specifying the transfer. In response to an access request received via a file system programmatic interface, contents of the object are provided from the second storage device. Based on a second access metric, the object is transferred back to the first group of storage devices.

First claim

Opening claim text (preview).

1 - 22 . (canceled) 23 . A system, comprising: a file system manager implemented at one or more computing devices; and a plurality of groups of storage devices, including a first group of storage devices with a first capability level and a second group of storage devices with a different capability level; wherein the one or more computing devices: identify, by the file system manager, at least a first storage device of the first group of storage devices as an initial location of a file system object; collect one or more metrics associated with the file system object, including a first metric; and initiate, by the file system manager, a first transfer, based at least in part on the first metric, of at least a portion of contents of the file system object from the initial location to a second storage device of the second group of storage devices, without receiving a transfer request specific to the file system object. 24 . The system as recited in claim 23 , wherein the file system manager is configured to: include, in a listing of file system objects of the particular file system provided subsequent to the first transfer, the first file system object, without providing an indication that the at least a portion of the first file system object has been transferred to the second storage device. 25 . The system as recited in claim 23 , wherein the file system manager is configured to: initiate, based at least in part on a second metric, a second transfer of the at least a portion of contents of the first file system object from the second group to the first group, without receiving a transfer request specific to the file system object. 26 . The system as recited in claim 23 , wherein an initiation of the first transfer is based at least in part on a transfer policy indicated via a programmatic interface. 27 . The system as recited in claim 26 , wherein the transfer policy includes an indication of an expected access pattern. 28 . A method, comprising: identifying, by a file system manager, at least a first storage device of a first group of storage devices as an initial location of a file system object, wherein the file system manager has access to a plurality of groups of storage devices with respective capability levels including the first group and a second group; initiating, by the file system manager, a first transfer, based at least in part on a first metric, of at least a portion of contents of the file system object from the initial location to a second storage device of the second group, without receiving a transfer request specific to the file system object; and providing, from the second storage device subsequent to the first transfer, contents of the file system object in response to a request received via a programmatic interface. 29 . The method as recited in claim 28 , further comprising: collecting one or more metrics associated with the file system object, including the first metric. 30 . The method as recited in claim 28 , further comprising: initiating, by the file system manager, a second transfer, based at least in part on a second metric, of the at least a portion of contents of the file system object from the second group to the first group, without receiving a transfer request specific to the file system object. 31 . The method as recited in claim 28 , further comprising: modifying, by the file system manager, one or more transfer policies associated with contents of the file system object, based at least in part on a machine learning-based analysis of one or more metrics. 32 . The method as recited in claim 28 , wherein the file system object is part of a particular file system, further comprising: determining, by the file system manager, an accessibility mode of the particular file system, wherein the accessibility mode is selected from a set which includes at least (a) a private mode enabling access to the particular file system from a single compute instance and (b) a shared mode enabling access to the particular file system from a plurality of compute instances; wherein the identifying of the initial location of the first storage object is based at least in part on the accessibility mode of the particular file system. 33 . The method as recited in claim 28 , wherein a particular group of the first and second groups of storage devices comprises: (a) locally-attached solid state drives (SSD) of instance hosts, (b) locally-attached rotating magnetic disk drives of instance hosts, (c) network-accessible solid state drives of a service implementing a block-level programmatic interface, (d) network-accessible magnetic disk drives of a service implementing a block-level programmatic interface, (e) devices of an object storage service implementing a web-services interface, (f) devices of a third-party storage service, or (g) storage devices attached to un-virtualized hosts. 34 . The method as recited in claim 28 , wherein the initiating the first transfer is based at least in part on a transfer policy indicated programmatically. 35 . The method as recited in claim 28 , further comprising: identifying, by the file system manager, a second file system object whose contents are to be copied to the second storage device group from an initial location in the first storage device group; initiating, by the file system manager, a copy of contents of the second file system object to the second storage device group, without deleting the contents from the first storage device group; storing, by the file system manager, metadata indicating that the second file system object is a candidate for eviction from the first storage device group; and in response to a subsequent access request directed to the second file system object, determining, by the file system manager, that contents of the second file system object have not yet been evicted from the first storage device group; and providing, from the first storage device group by the file system manager, contents of the second file system object. 36 . The method as recited in claim 35 , further comprising: determining, by the file system manager after providing the contents of the second file system object in response to the subsequent access request, that an amount of free space available at a particular storage device of the first storage device group has fallen below a threshold level; and deleting the contents of the second file system object from the first storage device group. 37 . The method as recited in claim 35 , wherein the metadata includes an indication that after the second file system is designated as a candidate for eviction from the first storage device group, billing for the presence of the second file system object in the first storage device group is not to be performed. 38 . The method as recited in claim 28 , further comprising: storing, by the file system manager, an encrypted version of the file system object at the first storage device after identifying at least the first storage device as the initial location of the file system object. 39 . A non-transitory computer-accessible storage medium storing program instructions that when executed on one or more processors cause the one or more processors to: identify, by a file system manager, at least a first storage device of a first group of storage devices as an initial location of a file system object, wherein the file system manager has access to a plurality of groups of storage devices with respective capability levels including the first group and a second group; collect one o

Assignees

Inventors

Classifications

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US2018349409A1 cover?
A file system manager implemented at a provider network identifies a storage device of a first group of storage devices of a provider network as an initial location of a file system object. Based on an access metric associated with the object, the file system manager initiates a transfer of contents of the object to a second storage device of a different storage device group, without receiving …
Who is the assignee on this patent?
Amazon Tech Inc
What technology area does this patent fall under?
Primary CPC classification G06F17/30203. Mapped technology areas include Physics.
When was this patent published?
Publication date Thu Dec 06 2018 00:00:00 GMT+0000 (Coordinated Universal Time) (A1). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 8 related publications on this page (citations in our corpus or others sharing the same primary CPC).