Hydration and dehydration with placeholders

• US 9,166,866 B2
• Filed: 04/30/2013
• Issued: 10/20/2015
• Est. Priority Date: 04/30/2013
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Novak, Michael John, Guzak, Chris, Ranjit, Sangeeta, Hoogerwerf, Scott David, Govrin, Amnon Itamar, Reiniger, Kiernon, Shekel, Oded Yehuda
• Primary Examiner(s): Truong, Lan Dai T
• Application Number:
  US13/874,474
• Publication Number:
  US 20140324945A1
• Time in Patent Office: 903 Days
• Field of Search: 703/203, 703/232, 703/236, 703/231, 703/234, 703/244, 703/246
• US Class Current: 1/1
• CPC Class Codes: G06F 16/1744 using compression, e.g. sparse files
• CPC Class Codes: G06F 3/0604 Improving or facilitating administration, e.g. storage management
• CPC Class Codes: G06F 3/0649 Lifecycle management
• CPC Class Codes: G06F 3/067 Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes

Abstract

Aspects of the subject matter described herein relate to file system placeholders. In aspects, placeholders may be used by a client to represent remote file system objects. The placeholders may include metadata and may also include none, some, or all of the content of the represented remote file system objects. In conjunction with placeholders and based on one or more factors, a client may hydrate or dehydrate file system objects of the client to follow user directives, inferred user intent, and storage policies of the client.

Claims

1. A method implemented at least in part by a computer, the method comprising:

receiving an indication of a file system object of a local file system of a client, the client structured to synchronize the local file system with a remote storage system;

evaluating one or more factors to determine an action to take with respect to the file system object, the action selected from actions that include;

to hydrate, to dehydrate, and to do nothing with respect to the file system object; and

if the action is to dehydrate the file system object, performing dehydration actions, the dehydration actions comprising;

creating or maintaining a placeholder to represent the file system object, the placeholder being stored on the local file system, the local file system structured to obtain metadata of the file system object from the placeholder, the metadata sufficient to allow the client, while offline with respect to the remote storage system, to obtain namespace information about the file system object from the placeholder, the placeholder including data that identifies the remote storage system from which content of the file is obtainable,

updating the placeholder to indicate that the file system object is dehydrated, and purging the content of the file system object from the local file system while maintaining the metadata of the file system object in the placeholder.

2. The method of claim 1, wherein evaluating one or more factors to determine an action to take with respect to the file system object comprises determining to perform the dehydration actions based on a communication with the remote storage system, the communication indicating that the file system object is stale, the file system object having been edited on another client that also utilizes placeholders.

3. The method of claim 1, wherein evaluating one or more factors to determine an action to take with respect to the file system object comprises determining that a user has indicated that the file system object is to remain available while the client is offline with respect to the remote storage system and maintaining the file system object on the local file system regardless of other of the one or more factors.

4. The method of claim 1, wherein evaluating one or more factors to determine an action to take with respect to the file system object comprises inferring that the file system object is to remain available while the client is offline based on an observed user action with respect to the file system object.

5. The method of claim 4, wherein the observed user action with respect to the file system object comprises creating or editing the file system object.

6. The method of claim 4, wherein the observed user action with respect to the file system object comprises opening the file in at least write mode.

7. The method of claim 1, wherein evaluating one or more factors to determine an action to take with respect to the file system object comprises determining that space is needed on the local file system of the client and that the file system object includes video and is of a size that is greater than a configurable threshold and determining that the action is to dehydrate the file system object.

8. The method of claim 1, wherein evaluating one or more factors to determine an action to take with respect to the file system object is triggered by a requested action with respect to the file system object and further comprising determining to hydrate the file system object, the requested action comprising a request to move the file system object from a namespace associated with the remote storage system to a namespace associated with another remote storage system.

9. The method of claim 1, wherein if the action is to hydrate the file system object, performing hydration actions, the hydration actions comprising:

accessing the placeholder that represents the file system object;

obtaining from the placeholder the data that identifies the remote storage system;

obtaining the content from the remote storage system; and

storing the content on the local file system.

10. The method of claim 9, wherein the hydration actions further comprise:

storing file system metadata for the file system object in the file system;

deleting the placeholder after the file system object is fully hydrated;

until the file system object is dehydrated again, using the file system metadata for subsequent accesses to the file system object.

11. The method of claim 9, wherein the hydration actions further comprise updating the placeholder to indicate that the file system object is fully hydrated.

12. The method of claim 1, further comprising executing a maintenance process that iterates files of the local file system to determine, based on the factors, whether to hydrate, dehydrate, partially hydrate, or do nothing to each of the files.

13. A computing device comprising:

storage hardware and processing hardware;

the storage hardware storing computer storage elements that maintain file system metadata for local file system objects of a local file system and that maintain placeholders for remote file system objects of a remote storage system, the placeholders including metadata of the remote file system objects without requiring that content of the remote file system objects exist in the storaqe hardware;

a placeholder manager, stored by the storage hardware and structured to, when executed by the processing hardware, create, populate, and maintain the placeholders to ensure that a placeholder exists for each remote file system object in the namespace at least if the content of the remote file system object does not completely exist on the storage hardware; and

a hydration/dehydration manager stored by the storage hardware, the hydration/dehydration manager structured to, when executed by the processing hardware, evaluate one or more factors to determine an action to take with respect to the local file system objects, the action selected from actions that include;

to hydrate, to partially hydrate, to dehydrate, and to do nothing with respect to the local file system object,

the hydration/dehydration manager further structured to perform, when executed by the processing hardware, dehydration actions with respect to the local file system object, the dehydration actions comprising;

causing a placeholder to be created or maintained on the storage hardware, the placeholder representing the local file system object, the local file system structured to obtain file metadata of the local file system object from the placeholder, the file metadata sufficient to allow the computing device, while offline with respect to the remote storage system, to obtain namespace information about the local file system object from the placeholder, the placeholder including data that identifies the remote storage system from which content of the local file system object is obtainable;

updating the placeholder to indicate that the local file system object is dehydrated; and

purging the content of the local file system object from the local file system while maintaining the file metadata of the local file system object in the placeholder.

14. The computing device of claim 13, wherein the hydration/dehydration manager is further structured to perform hydration actions, the hydration actions comprising:

accessing a second placeholder that represents a second file system object;

obtaining from the second placeholder data that identifies the remote storage system;

obtaining content of the second file system object from the remote storage system; and

storing the content of the second file system object in the local file system.

15. The computing device of claim 14, wherein the hydration/dehydration manager is further structured to perform additional hydration actions, the additional hydration actions comprising:

storing file system metadata for the second file system object in the local file system;

causing the second placeholder to be deleted after the second file system object is fully hydrated;

until the second file system object is dehydrated, using the file system metadata for the second file system object for subsequent accesses to the second file system object.

16. The computing device of claim 14, wherein the hydration/dehydration manager is further structured to perform additional hydration actions, the additional hydration actions comprising causing the second placeholder to be updated to indicate that the second file system object is fully hydrated and causing the second placeholder and to be maintained on the local file system while the second file system object is fully hydrated.

17. The computing device of claim 14, wherein the hydration/dehydration manager is further structured to periodically iterate files of the local file system to determine, based on the factors, whether to hydrate, dehydrate, or partially hydrate each of the files.

18. The computing device of claim 14, wherein the hydration/dehydration manager is further structured to infer whether the local file system object is to remain available while the computing device is offline with respect to the remote storage system based on an observed user action with respect to the local file system object.

19. A computer storage medium having computer-executable instructions, which when executed perform actions, comprising:

receiving a request for content of a file system object indicated by a client, the client having a client file system, the client file system having file system objects in which all content is located on the client file system and file system objects in which less than all content is located on the client file system, the client having at least placeholders that represent the file system objects in which less than all content is located on the client file system, the client structured to evaluate one or more factors to determine an action to take with respect to a file system object, the action selected from actions that include;

to hydrate, to dehydrate, and to do nothing with respect to the file system object, the file system object being dehydrated on the client file system based on the one or more factors, the file system object being represented on the client file system via a placeholder at least while the file system object is dehydrated on the client file system; and

providing the content of the file system object from a remote storage system.

20. The computer storage medium of claim 19, further comprising sending a message to the client to indicate that the file system object is stale, the client further structured to determine to dehydrate the file system object based on whether the file system object is stale.