Shared namespace for storage clusters

• US 8,255,430 B2
• Filed: 08/24/2009
• Issued: 08/28/2012
• Est. Priority Date: 08/26/2008
• Status: Active Grant

• Current Assignee: DataCore Software Corporation (Flagship Ventures 2004 Fund LLC)
• Original Assignee: Caringo Incorporated
• Inventors: Dutton, James E., Morrison, James M., Arbilla, Laura, Casey, James B. Jr.
• Primary Examiner(s): AL HASHEMI, SANA A
• Application Number:
  US12/546,104
• Publication Number:
  US 20100070515A1
• Time in Patent Office: 1,100 Days
• Field of Search: 707/960, 707/804, 707/807, 707/803, 707/795, 707/793, 707/791, 707/737
• US Class Current: 707/807
• CPC Class Codes: G06F 16/13 File access structures, e.g. distributed indices arrangements of input from, or output to, record carriers G06F3/06
• CPC Class Codes: G06F 16/166 File name conversion

Abstract

Any client application uses a namespace application to resolve its pathname in order to reference a computer file. Computer files are stored in a fixed-content storage cluster and are accessed by retrieving a unique identifier for the computer file using the namespace application. Any type of pathname scheme from any client application is supported by the namespace. The namespace application uses a bindings table to record bindings between objects including the start date and end date for each binding, and direction and separator data used in the pathname scheme. An attribute table in the namespace keeps track of each attribute and its value for each object of the namespace including a start date and an end date for each attribute. The namespace provides syntactic generality in that any pathname scheme of a client application can be resolved to identify a unique computer file in the storage cluster. The namespace may be shared between applications because when one application modifies a file or its attributes using the namespace, another application using a different pathname scheme has access to the exact same data and modifications. The namespace provides a near instantaneous continuous backup for computer files in the storage cluster because of the use of start date and end dates for the bindings and attributes.

Claims

1. A method of adding a computer file to a storage cluster, said method comprising:

receiving a first pathname identifying a computer file that uses a first pathname scheme of a client software application;

parsing said first pathname by said client application into its constituent name portions;

constructing a representation in a database of said first pathname identifying said computer file using said name portions, said representation forming a path arranged to be traversed progressively from the most general name portion to the most specific name portion;

passing said computer file to said storage cluster and receiving a unique identifier from said storage cluster that uniquely identifies said computer file stored within said storage cluster;

storing said unique identifier in conjunction with an end of said representation of said first pathname in said database, whereby said computer file is uniquely represented in said database by said representation; and

forming a second path in said database using name portions from a second pathname that is different from said first pathname, said second path terminating at said end of said representation of said first pathname, whereby a traversal of said path and a traversal of said second path both terminate at said end where said unique identifier is stored.

4. A method as recited in claim 1 wherein said unique identifier is a universally unique identifier.

5. A method as recited in claim 1 wherein said representation is embodied by bindings in a bindings table.

6. A method as recited in claim 1 wherein said computer file may be retrieved from said storage cluster using said unique identifier alone.

7. A method as recited in claim 1 wherein said first pathname is not ordered from the most general to the most specific, said method further comprising:

reordering said constituent name portions in order to form said path.

8. A method as recited in claim 1 wherein said most specific name portion identifies a storage location of said end of said representation holding said stored unique identifier.

9. A method as recited in claim 1 wherein said parsing further includes:

parsing said first pathname into progressively more specific name portions.

10. A method as recited in claim 1 further comprising:

parsing said first pathname into said name portions, each name portion including a generality direction indicating in which direction said first pathname becomes more specific; and

storing said generality direction with said name portion in said database.

2. A method of adding a computer file to a storage cluster, said method comprising:

receiving a first pathname identifying a computer file that uses a first pathname scheme of a client software application;

parsing said first pathname by said client application into its constituent name portions;

constructing a representation in a database of said first pathname identifying said computer file using said name portions, said representation forming a path arranged to be traversed progressively from the most general name portion to the most specific name portion;

passing said computer file to said storage cluster and receiving a unique identifier from said storage cluster that uniquely identifies said computer file stored within said storage cluster;

storing said unique identifier in conjunction with an end of said representation of said first pathname in said database, whereby said computer file is uniquely represented in said database by said representation;

receiving a second pathname that uses a second pathname scheme that is different from said first pathname scheme; and

storing name portions of said second pathname in said database to form links that terminate at said end of said representation of said first pathname, whereby a traversal of said path and a traversal of said links both terminate at said end where said unique identifier is stored.

11. A method as recited in claim 2 wherein said computer file may be retrieved from said storage cluster using said unique identifier alone.

12. A method as recited in claim 2 wherein said first pathname is not ordered from the most general to the most specific, said method further comprising:

reordering said constituent name portions in order to form said path.

13. A method as recited in claim 2 wherein said most specific name portion identifies a storage location of said end of said representation holding said stored unique identifier.

14. A method as recited in claim 2 wherein said parsing further includes:

parsing said first pathname into progressively more specific name portions.

15. A method as recited in claim 2 further comprising:

parsing said first pathname into said name portions, each name portion including a generality direction indicating in which direction said first pathname becomes more specific; and

storing said generality direction with said name portion in said database.

3. A method of adding a computer file to a storage cluster, said method comprising:

receiving a first pathname identifying a computer file that uses a first pathname scheme of a first client software application;

calling a function of a namespace application and passing said first pathname, said first pathname including first pathname portions;

constructing a first representation in said namespace application of said first pathname identifying said computer file using said first pathname portions;

storing said computer file in said storage cluster and receiving a unique identifier from said storage cluster that uniquely identifies said computer file stored within said storage cluster;

receiving a second pathname identifying said computer file that uses a second pathname scheme of a second client software application;

calling said function of said namespace application and passing said second pathname, said second pathname including second pathname portions;

constructing a second representation in said namespace application of said second pathname identifying said computer file using said second pathname portions;

storing said unique identifier in conjunction with a termination of said representation of said first pathname and of said second pathname in said namespace application, whereby said computer file is uniquely represented in said namespace application by both of said representations.

16. A method as recited in claim 3 further comprising:

parsing said first pathname by said client application into its said constituent name portions, each name portion including a generality direction and a separator.

17. A method as recited in claim 3 further comprising:

using said generality directions and separators for each of said name portions to perform said step of constructing a first representation.

18. A method as recited in claim 3 wherein said unique identifier is a universally unique identifier.