US 7,689,715 B1Granted

Method and system for implementing a global name space service

AssigneeSymantec Operating Corporation

InventorsGregory L. Slaughter, Paul Czarnik, John Muth, Kai Wong, Andrew Krumel

Life of this patent

Estimating the term…

Loading patent…

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.

Claims17

Dependent claims

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.

9 more elements

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.

9 more elements

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.

12 more elements

Dependencies are inferred from the claim text.