File service using a shared file access-rest interface

Patent metadata

Field	Value
Publication number	US-10536523-B2
Application number	US-201514708286-A
Country	US
Kind code	B2
Filing date	May 10, 2015
Priority date	May 11, 2014
Publication date	Jan 14, 2020
Grant date	Jan 14, 2020

Abstract

In various embodiments, methods and systems for providing access to file systems are provided. An SFA-based operation having an operation modifier for a file in a file system is received. The SFA-based operation is defined based on a file-representational state transfer (REST) interface. The SFA-REST interface comprises integrated functionality of an SFA protocol and REST protocol. The SFA-based operation is executed using the operation modifier. A REST-based operation for the file in the distributed file storage is received. The REST-based operation is defined based on the SFA-REST interface. The operation modifier is referenced in order to execute the REST-based operation. The REST-based operation based on the SFA-REST interface. A schema can be implemented for accessing the file system. The schema includes tables to store files, the table comprises fields corresponding to elements of a SFA-REST interface. A snapshot component can be implemented to backup file shares in the file system.

First claim

The invention claimed is:

1. A system for executing REST-based operations and SFA-based operations in distributed file systems, the system comprising:
one or more hardware processors and computer storage media storing computer-executable instructions and components that, when executed, by the one or more hardware processors, cause the one or more hardware processors to execute:
a Shared File Access-Representational State Transfer (SFA-REST) interface component configured for:
receiving one or more SFA-based operations for files in a distributed file system;
processing the one or more SFA-based operations based on an SFA-REST interface, wherein the SFA-REST interface comprises integrated functionality of an SFA protocol and REST protocol;
receiving one or more REST-based operations for files in the distributed file system;
processing the one or more REST-based operations based on the SFA-REST interface;
executing an SFA-based operation on a first file;
executing an SFA-based operation on a second file; and
executing a REST-based operation on the second file based in part on referencing the currently executing SFA-based operation accessing the second file.

2. The system of claim 1 , wherein the SFA interface component further comprises a data access component configured for:
returning a handle corresponding to the first file for the SFA-based operation; and
not returning a handle corresponding to the second file for the REST-based operation.

3. The system of claim 1 , wherein the SFA interface component further comprises a lease access component configured for:
granting a REST lease for the second file, wherein the REST lease supports exclusive write shared read access to the second file; and
granting shared access to files based on REST leases or handles of operation modifiers associated with the files, wherein the one or more SFA-based operations include operation modifiers that define a constraint that modifies the one or more SFA-based operations.

4. The system of claim 1 , wherein the SFA interface component further comprises a cache component configured for:
identifying an opportunistic lock associated with operation modifiers of the one or more SFA-based operations, wherein the opportunistic lock indicates that a latest state of files is cached on an SFA client associated with the SFA-based operation;
determining to break the opportunistic lock of the SFA-based operation based on referencing the operation modifiers; and
performing an opportunistic lock break operation such that the one or more REST-based operations are executed.

5. The system of claim 1 , wherein the SFA interface component further comprises a time stamp component configured for:
generating a plurality of timestamps for files in the distributed file system for both the one or more SFA-based operations and the one or more REST-based operations, wherein the plurality of time stamps include at least an entity tag (ETAG) timestamp and one or more of: a creation time, a last modify time, a last write time, and a last access time, wherein the ETAG timestamp is updated for both the one or more REST-based operations and the one or more SFA-based operations to support optimistic concurrency.

6. The system of claim 1 , wherein the SPA interface component further, comprises:
a metadata component configured for providing a restricted name set for metadata corresponding to the one or more SFA-based operations and the one or more REST-based operations; and
a name and referencing component configured for implementing case insensitive and case preserving directory names and file names system.

7. The system of claim 1 , wherein the SFA interface component further comprises a byte lock component configured for:
rejecting read operations or write operations through the one or more REST-based operations when a conflict exists with a logic of the one or more SFA-based operations byte range lock, wherein an SFA-based byte range lock defines read and write access to regions of tiles.

8. The system of claim 1 , wherein the SFA interface component further comprises a locking component configured for executing locking operation modifiers associated with the one or more SFA-based operations, wherein access to files is processed based on locking operation modifiers of the one or more SFA-based operations.

9. The system of claim 1 , further comprising a file service schema comprising a plurality of tables, wherein the plurality of tables store states of files in the distributed file system, and wherein the plurality tables comprise fields corresponding to elements of the SFA-REST interface.

10. The system of claim 1 , further comprising a snapshot component configured for:
snapshotting a file share to back-up the contents of the file share, wherein the file share comprises changes to the file share written to the file share using a copy-on-write type pattern such that a previous version at each snapshot can be accessed independently, and wherein snapshotting the file share is based one of:
an atomic snapshot operation comprising a two-pass-notification and write instruction operation;
a non-atomic snapshot operation comprising a single-pass write instruction operation; or
a cross-share atomic snapshot comprising snapshotting multiple file shares.

11. The system of claim 1 , further comprising a snapshot component comprising a share table having a schema that represents the files and snapshots of the file share, wherein the share table comprises an entry for the file share and one or more entries for snapshots of the file share.

12. A system for executing REST-based operations and SFA-based operations in distributed file systems, the system comprising: one or more hardware processors and computer storage media storing computer-executable instructions and components that, when executed, by the one or more hardware processors, cause the one or more hardware processors to execute:
a file service schema comprising a plurality of tables, wherein the plurality of tables store states of files in the distributed file system, and wherein the plurality of tables comprise fields corresponding to elements of an a Shared File Access-Representational State Transfer (SFA-REST) interface,
wherein the SFA-REST interface comprises integrated functionality of an SFA protocol and REST protocol for referencing between one or more REST-based operations and one or more SFA-based operations concurrently executing to access files in the file system.

13. The system of claim 12 , wherein the file service schema further comprises hierarchical tables for storing files and directories based on corresponding names of the files and directories, wherein files and directories are retrieved using lookups to a namespace table storing a plurality of file identifiers.

14. The system of claim 12 , further comprising a namespace table, wherein the name space table is a primary table of the file service schema.

15. The system of claim 12 , further comprising a file information table, wherein the file information table stores information about the content of files, wherein the file information table comprises a plurality of timestamps fields for files.

16. The system of claim 12 , further comprising a file page range table, wherein the file page range table comprises data associated with files, wherein a key for the table comprises a file identifier and an offset size of a page range stored for a file.

17. The system of claim 12 , further comprising a handle table, wherein the handle table comprises one or more open handles for the one or more S

Assignees

• Microsoft Technology Licensing Llc

Inventors

• Calder Bradley Gene
• Ghanem Jean
• Edwards Andrew James
• Aroya Ishai Ben
• Goebel David Allen
• Wu Jiesheng
• Haridas Jaidev
• Ganguly Shuvabrata
• Hendel Matthew Douglas
• Demir Ozan

Classifications

• H04L67/1097 Primary

  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 title

• G06F16/176 Primary

  Support for shared access to files; File sharing support · CPC title

• G06F16/1774

  Locking methods, e.g. locking methods for file systems allowing shared and concurrent access to files · CPC title

• G06F16/182

  Distributed file systems · CPC title

• G06F11/1464

  for networked environments · CPC title