Transmitting filesystem changes over a network

US2016154818A1 · US · A1

Patent metadata
FieldValue
Publication numberUS-2016154818-A1
Application numberUS-201514960244-A
CountryUS
Kind codeA1
Filing dateDec 4, 2015
Priority dateSep 30, 2010
Publication dateJun 2, 2016
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.

Transmitting filesystem changes over a network is disclosed. A hash of data comprising a chunk of directory elements comprising one or more consecutive directory elements in a set of elements sorted in a canonical order is computed at a client system. One or more directory elements comprising the chunk are sent to a remote server in the event it is determined based at least in part on the computed hash that corresponding directory elements as stored on the remote server are not identical to the directory elements comprising the chunk as stored on the client system.

First claim

Opening claim text (preview).

1 . A method of synchronizing filesystem changes, comprising: sorting a list of directory elements, wherein each directory element includes a representation of metadata associated with a node in the filesystem; determining a chunk of directory elements comprising one or more consecutive directory elements by breaking up the sorted list of directory elements; computing at a client system a hash of data comprising the chunk of directory elements; determining based at least in part on the computed hash whether the corresponding directory elements as stored on the remote server match the directory elements comprising the chunk as stored on the client system; and in the event that the corresponding directory elements as stored on the remote server does not match the directory elements comprising the chunk as stored on the client system, sending, to the remote server, the computed hash and information from which the remote server computes a verification hash of data comprising one or more directory elements as is stored at the remote server; determining whether the verification hash matches the computed hash; and in the event that the verification hash does not match the computed hash, synchronizing the one or more directory elements comprising the chunk as stored on the client system with one or more corresponding directory elements as stored at the remote server. 2 . The method of claim 1 , wherein at least a portion of the one or more directory elements comprising the chunk that are sent to the remote server correspond to at least a subset of changes in data stored at the client system since a previous synchronization between the remote server and the client system. 3 . The method of claim 1 , further comprising receiving from the remote server an indication whether a corresponding hash corresponding to the computed hash and computed by the server based on corresponding filesystem information stored on the server matched the computed hash. 4 . The method of claim 3 , further comprising adding the computed hash to a hash cache if the response from the server indicates that the corresponding hash matched the computed hash. 5 . The method of claim 4 , further comprising adding the computed hash to the hash cache once the one or more directory elements comprising the chunk have been sent to the remote server in response to receiving from the server an indication that the corresponding hash computed at the server did not match the computed hash sent by the client system. 6 . The method of claim 1 , further comprising adding the computed hash to a span of consecutive chunks, if any, the respective hashes of which have been found in the hash cache, in the event the computed hash is found in a hash cache. 7 . The method of claim 6 , further comprising synchronizing the span and the chunk if the computed hash is not found in the hash cache. 8 . The method of claim 7 , wherein synchronizing the span includes sending to the remote server a hash of directory elements comprising chunks included in the span. 9 . The method of claim 8 , further comprising sending directory elements comprising chunks included in the span to the remote server in the event an indication is received that a corresponding hash computed based on directory elements stored on the server that correspond is to elements comprising the chunks included in the span as stored on the client system did not match the hash of directory elements comprising chunks included in the span sent by the client system. 10 . The method of claim 6 , further comprising: determining upon reaching an end of the set of elements that the span covers the entire set of elements; and ensuring that a hash of the entire set of elements is stored in the hash cache. 11 . The method of claim 10 , further comprising checking at the outset of a synchronization of the set of elements whether the hash of the entire set of elements is stored in the hash cache; and concluding without further processing that the set of elements are in sync between the client system and the remote server if the hash of the entire set of elements is found in the hash cache. 12 . The method of claim 10 , further comprising synchronizing the span if upon reaching the end of the set of elements it is determined that the span does not cover the entire set of elements. 13 . The method of claim 1 , wherein each of the directory elements comprises a canonical representation of metadata comprising filesystem information associated with a corresponding file in a directory with which the directory elements are associated. 14 . The method of claim 13 , further comprising generating the respective canonical representations. 15 . The method of claim 14 , further comprising sorting the directory elements in the canonical order. 16 . The method of claim 1 , wherein the information from which the server computes the verification hash comprises an offset of a first file represented by the chunk associated with the hash, and a number of files represented by the chunk associated with the hash. 17 . The method of claim 1 , wherein the verification hash is computed based at least in part on the information received from the client system and corresponding information stored at the remote server. 18 . A computer system, comprising: a processor configured to: sort a list of directory elements wherein each directory element includes a is representation of metadata associated with a node in the filesystem; determine a chunk of directory elements comprising one or more consecutive directory elements by breaking up the sorted list of directory elements; compute a hash of data comprising the chunk of directory elements comprising; determine based at least in part on the computed hash whether the corresponding directory elements as stored on the remote server match the directory elements comprising the chunk as stored on the client system; and in the event that the corresponding directory elements as stored on the remote server does not match the directory elements comprising the chunk as stored on the client system, send, to the remote server, the computed hash and information from which the remote server computes a verification hash of data comprising one or more directory elements as stored at the remote server; determine whether the verification hash matches the computed hash; and in the event that the verification hash does not match the computed hash, synchronizing the one or more directory elements comprising the chunk as stored on the client system with one or more corresponding directory elements as stored at the remote server; and a storage device coupled to the processor and configured to store data comprising the directory elements. 19 . The system of claim 18 , wherein at least a portion of the one or more directory elements comprising the chunk that are sent to the remote server correspond to at least a subset of changes in data stored at the client system since a previous synchronization between the remote server and the client system. 20 . The system of claim 18 , further comprising a communication interface couple to the processor and configured to be used by the processor to send the one or more directory elements comprising the chunk to the remote server. 21 . The system of claim 18 , wherein each of the directory elements comprises a canonical representation of metadata comprising filesystem information associated with a corresponding file in a directory with which

Assignees

Inventors

Classifications

  • Asynchronous replication or reconciliation · CPC title

  • Using snapshots, i.e. a logical point-in-time copy of the data · CPC title

  • Hash-based (content-based indexing of textual data G06F16/31) · CPC title

  • G06F16/178Primary

    Techniques for file synchronisation in file systems · CPC title

  • Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor · CPC title

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 US2016154818A1 cover?
Transmitting filesystem changes over a network is disclosed. A hash of data comprising a chunk of directory elements comprising one or more consecutive directory elements in a set of elements sorted in a canonical order is computed at a client system. One or more directory elements comprising the chunk are sent to a remote server in the event it is determined based at least in part on the compu…
Who is the assignee on this patent?
Emc Corp
What technology area does this patent fall under?
Primary CPC classification G06F16/178. Mapped technology areas include Physics.
When was this patent published?
Publication date Thu Jun 02 2016 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).