Managing objects for a data file

Abstract

Managing file objects in a data storage system includes providing a plurality of metadata servers, each metadata server having information for only a subset of file objects in the storage system, each subset for each of the metadata servers being less than a total number of file objects for the system and includes providing at least one metadata location server, where an entity accessing a specific file object of the system determines which of the metadata servers contains data for the specific file object by first accessing the at least one metadata location server. Information for the subset of file objects may include a table having file identifiers and metadata location information. The metadata location information may point to data storage for a metadata object for a file.

1 .- 25 . (canceled) 
     
     
         26 . A method of managing objects for a data file, comprising:
 determining a specific metadata server that handles a particular metadata object for the data file by providing a call to a metadata location server which returns the specific metadata server that handles the particular object according to an identifier for the object;   obtaining the metadata object for the data file from the specific metadata server;   determining if the metadata object indicates that a portion of the data file includes synchronous mirrors; and   in response to a write of new data to the data file, writing the new data to each synchronous mirror.   
     
     
         27 . A method, according to  claim 26 , wherein data objects of the data file may be in one of four states: current, stale, empty, and immutable. 
     
     
         28 . A method, according to  claim 27 , wherein, in response to a read operation and the corresponding data object being in a stale state, data is read for a corresponding synchronous mirror that is in a current state. 
     
     
         29 . A method, according to  claim 26 , wherein the metadata object is provided through a Web Services interface that includes at least one of: a SOAP interface and a REST interface. 
     
     
         30 . A method, according to  claim 26 , wherein the metadata object is provided through a direct file object interface that allows an application to directly access file objects at the same time that file objects are being accessed using at least one other interface. 
     
     
         31 . A method, according to  claim 26 , further comprising:
 providing file name services that translate file names into file object identifiers, wherein the file name services are accessed by at least one of: a file system interface and a Web Services interface.   
     
     
         32 . Computer software, provided in a computer-readable medium, that manages objects for a data file, the software comprising:
 executable code that determines a specific metadata server that handles a particular metadata object for the data file by providing a call to a metadata location server which returns the specific metadata server that handles the particular object according to an identifier for the object;   executable code that obtains a metadata object for the data file from the specific metadata server;   executable code that determines if the metadata object indicates that a portion of the data file includes synchronous mirrors; and   executable code that writes new data to each synchronous mirror in response to a write of new data to the data file.   
     
     
         33 . Computer software, according to  claim 31 , wherein data objects of the data file may be in one of four states: current, stale, empty, and immutable. 
     
     
         34 . Computer software, according to  claim 33 , wherein, in response to a read operation and a corresponding one of the data objects being in a stale state, executable code causes data to be read for a corresponding synchronous mirror that is in a current state. 
     
     
         35 . Computer software, according to  claim 32 , wherein the metadata object is provided through a Web Services interface that includes at least one of: a SOAP interface and a REST interface. 
     
     
         36 . Computer software, according to  claim 32 , wherein the metadata object is provided through a direct file object interface that allows an application to directly access file objects at the same time that file objects are being accessed using at least one other interface. 
     
     
         37 . Computer software, according to  claim 32 , further comprising:
 executable code that provides file name services that translate file names into file object identifiers, wherein the file name services are accessed by at least one of: a file system interface and a Web Services interface.