Cloud based file system surpassing device storage limits

• US 9,811,329 B2
• Filed: 02/13/2014
• Issued: 11/07/2017
• 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): Coby, Frantz
• Application Number:
  US14/180,021
• Publication Number:
  US 20140164453A1
• Time in Patent Office: 1,363 Days
• Field of Search: 707707, 707770, 707661, 707600, 707609, 707822, 709203, 709201, 709204, 709213, 709219
• 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, comprising:

storing, at a computing device, metadata of a plurality of storage objects in a file system of the computing device without permanently storing content data of the plurality of storage objects, wherein a storage server stores the content data of the plurality of storage objects, wherein a file system manager controls the plurality of storage objects and handles file system operations to the plurality of storage objects, wherein the file system manager is capable of controlling storage objects having a total size exceeding a physical storage limit of the computing device;

visualizing a preview of one or more of the plurality of storage objects using the metadata of the one or more storage objects as if the content data of the one or more storage objects are stored locally at the computing device, wherein the metadata includes a sample presentation of the content data of the one or more storage objects, the sample presentation including at least one of;

one or more bytes of a set of streaming data corresponding to a portion of the content data, or

a reduced-data-rate version of the content data;

identifying, at the computing device, at least one storage object of the plurality of storage objects that has a high possibility to be read by the computing device;

retrieving content data of the at least one storage object from the storage server after the at least one storage object is identified; and

storing, at the computing device, the content data of the at least one storage object for a time period.

2. The method of claim 1, wherein at least one of the content data of the plurality of storage objects is not stored locally in the computing device such that a maximum size of the file system exceeds the 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.

17. The method of claim 1, further comprising:

determining the at least one storage object that has the high possibility to be read by the computing device based at least in part on a usage profile, wherein the usage profile includes information on past usage of the plurality of storage objects on the computing device and respective indicated physical locations of the computing device in the past when the respective storage objects were accessed.

18. The method of claim 17, further comprising:

determining the at least one storage object that has the high possibility to be read by the computing device based at least in part on the usage profile and a determined current physical location of the computing device.

4. A computing device having a file system that can surpass physical storage limit, comprising:

a processor configured to identify one of multiple files of the computing device that has a high probability to be read by the computing device;

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

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

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

wherein the storage component is further configured to store the retrieved content data of the file for a time period;

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

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, wherein the metadata includes a sample presentation of the content data of the file, the sample presentation including at least one of;

one or more bytes of a set of streaming data corresponding to a portion of the content data, or

a reduced-data-rate version of the content data.

5. The computing device of claim 4, further comprising:

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

6. The computing device of claim 4, 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, or an inode data structure of the file, encoding format of the content data of the file.

7. The computing device of claim 4, wherein the sample presentation of the content data of the file further includes at least one of:

a reduced-size version of the content data, or

a sample clip or image of the content data.

8. A computing device having a file system that can surpass physical storage limit, comprising:

a processor configured to identify one of multiple files of the computing device that has a high probability to be read by the computing device;

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

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

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;

wherein the file system manager handles a write request to a file by a process including;

determining whether the storage component stores the content data of the file on the computing device;

based on determining that the storage component does not store the content data of the file on the computing device;

recording, into a log data structure, a plurality of sequential changes to the content data based on the write request, and

sending the log data structure to the storage server so that the server applies the plurality of sequential changes to the content data of the file in the storage server based on the log data structure.

9. 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 file stored at the computing device;

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

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

retrieving, by the file system manager, the content data of the 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 application as if the local storage device stores the content data of the file;

identifying, by the file system manager, a file having a tendency to be read by the computing device in future based on a file access pattern discovered by the file system manager, wherein the file having the tendency to be read by the computing device in future can be identified further based on file access patterns discovered by other computing devices connected to the storage server, wherein greater weight is given to the file access patterns discovered by the other computing devices associated with respective users determined to be similar to a user of the computing device; and

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

10. The method of claim 9, further comprising:

presenting, via an output device of the computing device, the file as a file stored in the local storage device of the computing device based on the metadata of the file.

11. The method of claim 9, wherein the first application and the second application are the same application.

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

13. The method of claim 9, wherein applications running at the computing device read 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.

14. The method of claim 9, wherein the storage server stores at least a portion of the metadata of the file.

15. The method of claim 9, wherein the storage server stores at least a portion of content data blocks of the file.

16. The method of claim 9, wherein the file system manager stores the content data of the file at the computing device before transmitting the content data of the file to the storage server.

19. A method comprising:

storing, at a computing device, metadata of a plurality of storage objects in a file system of the computing device without permanently storing content data of the plurality of storage objects, wherein a storage server stores the content data of the plurality of storage objects, wherein a file system manager controls the plurality of storage objects and handles file system operations to the plurality of storage objects, the file system manager being capable of controlling storage objects having a total size exceeding a physical storage limit of the computing device;

storing, at the computing device, the content data of at least a portion of at least one of the plurality of storage objects;

identifying a storage object of the plurality of storage objects that has a high probability to be read by the computing device;

retrieving content data of the storage object from the storage server after the storage object is identified;

receiving a write request for a first storage object;

determining whether content data of the first storage object is stored at the computing device; and

based on determining that the content data of the first storage object is not stored at the computing device;

recording, into a log data structure, a plurality of sequential changes to the first storage object based on the write request, and

sending the log data structure to the storage server so that the storage server applies the plurality of sequential changes to the content data of the first storage object stored in the storage server based on the log data structure.