Cloud based file system surpassing device storage limits

• US 10,042,623 B2
• Filed: 10/01/2013
• Issued: 08/07/2018
• Est. Priority Date: 10/02/2012
• Status: Active Grant

• Current Assignee: Razer (Asia-Pacific) Pte. Ltd. (Razer Incorporated)
• Original Assignee: Razer (Asia-Pacific) Pte. Ltd. (Razer Incorporated)
• Inventors: Chan, Michael A., Quan, Justin, Fleming, Michael K.
• Primary Examiner(s): Wong, Titus
• Application Number:
  US14/043,082
• Publication Number:
  US 20140108335A1
• Time in Patent Office: 1,771 Days
• Field of Search: 710 36
• CPC Class Codes: G06F 16/125 characterised by the use of retention policies retention policies for HSM systems G06F16/185
• CPC Class Codes: G06F 16/174 Redundancy elimination performed by the file system management of the data involved in backup or backup restore using de-duplication of the data G06F11/14
• CPC Class Codes: G06F 16/20 of structured data, e.g. relational data
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: G06F 16/273 Asynchronous replication or reconciliation
• CPC Class Codes: G06F 16/275 Synchronous replication
• CPC Class Codes: G06F 16/278 Data partitioning, e.g. horizontal or vertical partitioning
• CPC Class Codes: G06F 16/93 Document management systems
• CPC Class Codes: G06F 9/5038 considering the execution order of a plurality of tasks, e.g. taking priority or time dependency constraints into consideration scheduling strategies G06F9/4881 and subgroups
• CPC Class Codes: H04B 7/26 at least one of which is mobile
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04L 67/1097 for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
• CPC Class Codes: H04L 67/55 Push-based network services
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04M 1/72412 using two-way short-range wireless interfaces
• CPC Class Codes: H04M 2250/10 including a GPS signal receiver
• CPC Class Codes: H04M 2250/12 including a sensor for measuring a physical value, e.g. temperature or motion telephones including GPS signal receivers H04M2250/10
• CPC Class Codes: Y02D 10/00 Energy efficient computing, e.g. low power processors, power management or thermal management

Abstract

Technology is disclosed herein for a cloud based file system that can surpass physical storage limit. According to at least one embodiment, a computing device includes a file system having multiple storage objects. The metadata of the storage objects are stored in local storage of the computing device. A remote storage server is responsible for storing the content data of the storage objects. The computing device presents the storage objects via an output device as if the content data are stored locally in the computing device. The computing device identifies some of the storage objects that have a high possibility to be read by computer applications of the computing device, and caches the content data of these storage objects locally.

Claims

1. A method for managing a device file system integrated with a storage server, the method comprising:

storing, at a computing device, metadata of a plurality of storage objects in a file system of the computing device, wherein the storage server stores content data of the plurality of storage objects;

providing access to one or more of the plurality of storage objects as if the content data of the one or more storage objects are stored locally in the computing device;

receiving, at the computing device, a prefetching profile from a prefetching server, the prefetching profile specifying a set of the plurality of storage objects to be prefetched to the computing device, the prefetching profile comprising;

a likelihood of access within a first predetermined timeframe for each storage object of a first subset the set of storage objects; and

a likelihood of access within a second predetermined timeframe for each storage object of a second subset of the set of storage objects;

determining, at the computing device, at least one storage object of the set of storage objects that has the highest likelihood or the shortest predetermined timeframe of being accessed at the computing device based on the prefetching profile; and

caching, at the computing device, the content data of at least a portion of the at least one storage object.

2. The method of claim 1, wherein at least one of the content data of the plurality of storage objects are not stored locally in the computing device such that a maximum size of the file system exceeds a physical storage limit of the computing device.

3. The method of claim 1, wherein the metadata of a storage object include means of creation of data in the storage object, purpose of data in the storage object, time and date of creation of the storage object, creator or author of data of the storage object, location on the storage server where the content data of the storage object are stored, title of the content data of the storage object, an inode data structure of the storage object, version information or a sample presentation of the content data of the storage object.

4. The method of claim 1, wherein the prefetching profile is determined based on an access pattern to the plurality of storage objects on the computing device.

5. The method of claim 1, further comprising:

receiving a read request for an storage object from one of a plurality of computer applications;

determining whether content data of the storage object is cached at the computing device;

if the content data of the storage object is cached at the computing device, reading the content data of the storage object from its cached location at the computing device; and

if the content data of the storage object is not cached at the computing device, requesting the content data of the storage object from the storage server.

6. The method of claim 1, further comprising:

receiving a write request for an storage object from one of a plurality of computer applications;

determining whether content data of the storage object is cached at the computing device;

if the content data of the storage object is cached at the computing device, updating the storage object based on the write request; and

if the content data of the storage object is not cached at the computing device, recording a sequential list of changes to the storage object based on the write request into a log data structure.

7. The method of claim 6, further comprising:

sending the log data structure to the storage server so that the storage server applies the sequential list of changes to one or more storage objects stored in the storage server based on the log data structure.

8. A computing device having a file system able to surpass a physical storage limit, the computing device comprising:

a processor configured to identify a file of multiple files of the computing device based on a prefetching profile received at the computing device, the prefetching profile indicating a set of the multiple files to be preloaded at the computing device, the prefetching profile comprising;

a likelihood of access within a first predetermined timeframe for each file of a first subset of the set of files; and

a likelihood of access within a second predetermined timeframe for each file of a second subset of the set of files, the identified file having the highest likelihood or the shortest predetermined timeframe of being accessed at the computing device based on the prefetching profile;

a file system manager, when executed by the processor, controls the multiple files and handles file system operations to the multiple files;

a storage component configured to store metadata of the multiple files without permanently storing content data of the multiple files, wherein a storage server stores the content data of the multiple files; and

a networking component configured to retrieve the content data of the file from the storage server after the processor identifies the file,

wherein the file system manager is capable of controlling files having a total size exceeding a physical storage limit of the storage component.

9. The computing device of claim 8, wherein the storage component is further configured to cache the retrieved content data of the file for a time period.

10. The computing device of claim 8, further comprising:

an output component configured to present one or more of the multiple files as if content data of the one or more files are stored locally in the storage component.

11. The computing device of claim 8, wherein the metadata of a file include means of creation of data in the file, purpose of data in the file, time and date of creation of the file, creator or author of data of the file, location on the storage server where the content data of the file are stored, title of the content data of the file, an inode data structure of the file, encoding format of the content data of the file, or a sample presentation of the content data of the file.

12. The computing device of claim 11, wherein the sample presentation of the content data of the file includes a reduced-size version of the content data, a sample clip or image of the content data, the first few bytes of a set of streaming data or a reduced-data-rate version of the content data.

13. The computing device of claim 8, further comprising:

an output component configured to visualize a preview of at least one file of the files using the metadata of the file as if the content data of the file are stored locally in the storage component.

14. The computing device of claim 8, wherein the file system manager handles a write operation to a file by a process including:

determining whether the storage component caches the content data of the file;

if the storage component does not cache the content data of the file, forwarding the write operation to the storage server; and

if the storage component caches the content data of the file, applying the write operation to the cached content data of the file, and synchronizing the content data of the file in the storage component with the content data of the file in the storage server.

15. A method comprising:

receiving, at a file system manager of a computing device, an instruction from a first application running at the computing device to create a first file stored at the computing device;

creating, by the file system manager, the first file by storing metadata of the first file in a local storage device of the computing device and transmitting content data of the first file to a storage server, wherein the metadata include a link to a location where the storage server stores the content data of the first file;

receiving, at the file system manager, an instruction to read the first file from a second application running at the computing device;

retrieving, by the file system manager, the content data of the first file from the storage server based on the metadata including the link to the location;

providing, by the file system manager, the content data to the second application as if the local storage device stores the content data of the first file;

identifying, by the file system manager, a second file of a set of files based on a prefetching profile received from a prefetching server, the prefetching profile specifying the set of files to be stored at the computing device, the prefetching profile comprising;

a likelihood of access within a first predetermined timeframe for each file of a first subset of the set of files; and

a likelihood of access within a second predetermined timeframe for each file of a second subset of the set of files, the second predetermined timeframe being different from the first predetermined timeframe, the identified second file having the highest likelihood or the shortest predetermined timeframe of being accessed at the computing device based on the prefetching profile;

caching the identified second file in the local storage device by retrieving content data of the identified second file from the storage server.

16. The method of claim 15, wherein the second file is able to be identified further based on a file access pattern discovered by the file system manager.

17. The method of claim 16, wherein the second file is able to be identified further based on file access patterns discovered by other computing devices connected to the storage server.

18. The method of claim 15, wherein the first application and the second application are the same application.

19. The method of claim 15, wherein the file system manager maintains a file system including the files for the computing device having a total size larger than a storage limit of the local storage device of the computing device.

20. The method of claim 15, wherein applications running at the computing device read the files managed by the file system manager of the computing device as if the content data of the files are stored in the local storage device of the computing device.

21. The method of claim 15, wherein the storage server stores at least a portion of the metadata of the first file.

22. The method of claim 15, wherein the file system manager caches the content data of the first file at the computing device before transmitting the content data of the file to the storage server.

23. The method of claim 15, wherein the first file is the identified second file.