Method and system for implementing a global name space service

• US 7,689,715 B1
• Filed: 12/20/2002
• Issued: 03/30/2010
• Est. Priority Date: 12/20/2002
• Status: Expired due to Fees

• Current Assignee: Veritas Technologies, LLC (Whitehouse Group Ltd.)
• Original Assignee: Symantec Operating Corporation (Gen Digital Inc.)
• Inventors: Czarnik, Paul, Krumel, Andrew, Slaughter, Gregory L., Wong, Kai, Muth, John
• Primary Examiner(s): Flynn; Nathan
• Assistant Examiner(s): Siddiqi; Mohammad A
• Application Number:
  US10/327,544
• Time in Patent Office: 2,657 Days
• Field of Search: 709212-216, 709227-229, 709/245, 709/201, 707/10
• US Class Current: 709/245
• CPC Class Codes: G06F 16/134 Distributed indices

Abstract

A method and system for implementing a global name space service. The method may include receiving a file system unique identifier corresponding to a particular file and a human-readable name corresponding to the same file. The method may further include binding the human-readable name to the file system unique identifier, thereby creating a mapping between the human-readable name and the file system unique identifier. The system may include a processor coupled to a memory and to a global name space service manager. The global name space service manager may be configured to receive a file system unique identifier corresponding to a particular file and a human-readable name corresponding to the same file. The global name space service manager may be further configured to bind the human-readable name to the file system unique identifier, thereby creating a mapping between the human-readable name and the file system unique identifier.

Claims

1. A computer implemented method for implementing a global name space service for a distributed file system, said method comprising:

receiving a file system unique identifier corresponding to a particular file;

receiving a human-readable name corresponding to said particular file;

binding said human-readable name to said file system unique identifier;

wherein said binding creates a mapping between said human-readable name and said file system unique identifier; and

creating a mapping file including a table having a plurality of entries, each including a given human-readable name and a file system unique identifier corresponding to said given human-readable name;

wherein said given human-readable name comprises a pathname; and

wherein in response to receiving a given pathname including one or more pathname components;

accessing a first mapping file using a computer, wherein the first mapping file corresponds to a root component of said pathname, wherein the first mapping file provides a first file system unique identifier corresponding to a first component of said pathname and wherein the first mapping file is organized in a hierarchy based upon a first set of one or more possible components of the pathname; and

accessing a second mapping file using a computer, wherein the second mapping file corresponds to said first component of said pathname using said first file system unique identifier, wherein the second mapping file provides a second file system unique identifier corresponding to a second component of said pathname and wherein the second mapping file is organized in a hierarchy based upon a second set of one or more possible components of the pathname.

2. The method as recited in claim 1 further comprising in response to receiving said given human-readable name, accessing said mapping file and providing said corresponding file system unique identifier.

3. The method as recited in claim 1 further comprising in response to receiving said given human-readable name, accessing said mapping file and returning said corresponding file system unique identifier and deleting said entry including said given human-readable name.

4. The method as recited in claim 1, wherein said given human-readable name is a pathname.

5. The method as recited in claim 4 further comprising in response to receiving a given pathname, accessing said mapping file and returning a list of components, wherein each of said components is an entry in said table.

6. A storage media comprising executable instructions that, when executed by a processor, cause the processor to perform a method comprising:

receiving a file system unique identifier corresponding to a particular file;

receiving a human-readable name corresponding to said particular file;

binding said human-readable name to said file system unique identifier;

wherein said binding creates a mapping between said human-readable name and said file system unique identifier; and

creating a mapping file including a table having a plurality of entries, each including a given human-readable name and a file system unique identifier corresponding to said given human-readable name;

wherein said given human-readable name comprises a pathname; and

wherein in response to receiving a given pathname including one or more pathname components;

accessing a first mapping file corresponding to a root component of said pathname, wherein the first mapping file provides a first file system unique identifier corresponding to a first component of said pathname and wherein the first mapping file is organized in a hierarchy based upon a first set of one or more possible components of the pathname; and

accessing a second mapping file corresponding to said first component of said pathname using said first file system unique identifier, wherein the second mapping file provides a second file system unique identifier corresponding to a second component of said pathname and wherein the second mapping file is organized in a hierarchy based upon a second set of one or more possible components of the pathname.

7. The storage media as recited in claim 6, wherein said method further comprising in response to receiving said given human readable name, accessing said mapping file and providing said corresponding file system unique identifier.

8. The storage media as recited in claim 6, wherein said method further comprising in response to receiving said given human readable name, accessing said mapping file and returning said corresponding file system unique identifier and deleting said entry including said given human-readable name.

9. The storage media as recited in claim 6, wherein said given human-readable name is a pathname.

10. The storage media as recited in claim 9, wherein said method further comprising in response to receiving a given pathname, accessing said mapping file and returning a list of components, wherein each of said components is an entry in said table.

11. A system comprising:

a plurality of nodes interconnected via a network, wherein each of said nodes includes;

a processor configured to execute program instructions;

a memory coupled to said processor, said memory including said program instructions executable to implement a method of;

receiving a file system unique identifier corresponding to a particular file;

receiving a human-readable name corresponding to said particular file; and

binding said human-readable name to said file system unique identifier;

wherein said binding creates a mapping between said human-readable name and said file system unique identifier; and

wherein said mapping includes a mapping file including a table having a plurality of entries, each including a given human-readable name and a file system unique identifier corresponding to said given human-readable name;

wherein said given human-readable name comprises a pathname; and

wherein in response to receiving a given pathname including one or more pathname components;

accessing a first mapping file corresponding to a root component of said pathname, wherein the first mapping file provides a first file system unique identifier corresponding to a first component of said pathname and wherein the first mapping file is organized in a hierarchy based upon a first set of one or more possible components of the pathname; and

accessing a second mapping file corresponding to said first component of said pathname using said first file system unique identifier, wherein the second mapping file provides a second file system unique identifier corresponding to a second component of said pathname and wherein the second mapping file is organized in a hierarchy based upon a second set of one or more possible components of the pathname.

12. A system comprising:

a plurality of nodes interconnected via a network, wherein each of said nodes includes;

a processor configured to execute program instructions;

a memory coupled to said processor and configured to store said program instructions;

a global name space service manager coupled to said processor and configured to;

receive a file system unique identifier corresponding to a particular file;

receive a human-readable name corresponding to said particular file;

bind said human-readable name to said file system unique identifier and create a mapping between said human-readable name and said file system unique identifier; and

create a mapping file including a table having a plurality of entries, each including a given human-readable name and a file system unique identifier corresponding to said given human-readable name;

wherein said given human-readable name comprises a pathname; and

wherein in response to receiving a given pathname including one or more pathname components, said global name space service manager is further configured to;

access a first mapping file corresponding to a root component of said pathname, wherein the first mapping file provides a first file system unique identifier corresponding to a first component of said pathname and wherein the first mapping file is organized in a hierarchy based upon a first set of one or more possible components of the pathname; and

access a second mapping file corresponding to said first component of said pathname using said first file system unique identifier, wherein the second mapping file provides a second file system unique identifier corresponding to a second component of said pathname and wherein the second mapping file is organized in a hierarchy based upon a second set of one or more possible components of the pathname.

13. The system as recited in claim 12, wherein said global name space service manager is further configured to access said mapping file and to provide said corresponding file system unique identifier in response to receiving said given human-readable name.

14. The system as recited in claim 12, wherein said global name space service manager is further configured to access said mapping file, to return said corresponding file system unique identifier and to delete said entry including said given human-readable name in response to receiving said given human-readable name.

15. The system as recited in claim 12, wherein said global name space service manager of a given node is further configured to replicate and store on said given node a mapping file created on another node.

16. The system as recited in claim 15, wherein said global name space service manager of said given node is further configured to delete said replicated mapping file in response to a mapping file replacement timeout.

17. A system comprising:

a plurality of nodes interconnected via a network, wherein each of said nodes includes;

a processor configured to execute program instructions;

a memory coupled to said processor and configured to store said program instructions;

means for receiving a file system unique identifier corresponding to a particular file;

means for receiving a human-readable name corresponding to said particular file; and

means for binding said human-readable name to said file system unique identifier;

wherein said binding creates a mapping between said human-readable name and said file system unique identifier; and

wherein said mapping includes a mapping file including a table having a plurality of entries, each including a given human-readable name and a file system unique identifier corresponding to said given human-readable name;

wherein said given human-readable name comprises a pathname; and

wherein in response to receiving a given pathname including one or more pathname components;

accessing a first mapping file corresponding to a root component of said pathname, wherein the first mapping file provides a first file system unique identifier corresponding to a first component of said pathname and wherein the first mapping file is organized in a hierarchy based upon a first set of one or more possible components of a pathname; and

accessing a second mapping file corresponding to said first component of said pathname using said first file system unique identifier, wherein the second mapping file provides a second file system unique identifier corresponding to a second component of said pathname and wherein the second mapping file is organized in a hierarchy based upon a second set of one or more possible components of the pathname.