Source: http://www.google.com/patents/US8190741?dq=5343970
Timestamp: 2016-10-26 08:27:47
Document Index: 114705953

Matched Legal Cases: ['Application No. 200680032142', 'Application No. 04750678', 'Application No. 04750678', 'Application No. 04750678', 'Application No. 04', 'Application No. 2006']

Patent US8190741 - Customizing a namespace in a decentralized storage environment - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inPatentsSystems and methods to customize a namespace using a synthetic namespace. A NAS switch provides file migrations in a NAS storage network that are transparent to the clients. The NAS switch file handles are used to customize a namespace. More specifically, a synthetic namespace is generated from one or...http://www.google.com/patents/US8190741?utm_source=gb-gplus-sharePatent US8190741 - Customizing a namespace in a decentralized storage environmentAdvanced Patent SearchTry the new Google Patents, with machine-classified Google Scholar results, and Japanese and South Korean patents.Publication numberUS8190741 B2Publication typeGrantApplication numberUS 11/395,118Publication dateMay 29, 2012Priority dateApr 23, 2004Fee statusPaidAlso published asUS20060271598Publication number11395118, 395118, US 8190741 B2, US 8190741B2, US-B2-8190741, US8190741 B2, US8190741B2InventorsThomas K. Wong, Anand Iyengar, Panagiotis Tsirigotis, Chi Ming Wong, Yu Cheong Chan, Richard A. SimpkinsOriginal AssigneeNeopath Networks, Inc.Export CitationBiBTeX, EndNote, RefManPatent Citations (116), Non-Patent Citations (103), Referenced by (5), Classifications (6), Legal Events (3) External Links: USPTO, USPTO Assignment, EspacenetCustomizing a namespace in a decentralized storage environment
US 8190741 B2Abstract
Systems and methods to customize a namespace using a synthetic namespace. A NAS switch provides file migrations in a NAS storage network that are transparent to the clients. The NAS switch file handles are used to customize a namespace. More specifically, a synthetic namespace is generated from one or more file location tables that map the switch file handles to NAS file handles. The NAS file handles are independent of a physical export containing the objects referred to by the NAS file handles. In one example, the synthetic namespace presents a home directory corresponding to a location of a user.
1. A computer-implemented method for customizing a namespace in a storage network, comprising:
receiving one or more NAS (Network Attached Storage) file handles or path names from one or more exported physical file shares, the NAS file handles or path names each indicative of a location of an object on an exported physical file share;
receiving a plurality of configurations for creating a synthetic namespace from a network administrator or user, the plurality of configurations specifying an organization of, and criteria for selecting objects to be included in, the synthetic namespace;
maintaining a file location table for a plurality of selected objects that are selected according to the received plurality of configurations for the synthetic namespace, the file location table comprising mappings between each selected object's NAS file handle or path name and a corresponding switch file handle that remains independent of any location changes for the selected object, wherein the synthetic namespace comprises a subset of the objects on the one or more exported physical file shares; and
providing the switch file handles (or file handle) to a client, so that the selected objects are accessible by the client via the provided switch file handles, wherein providing the switch file handles (or file handle) to the client is associated with presenting to the client a customized namespace, the customized namespace comprising the synthetic namespace of the selected objects.
maintaining a second file location table configured in accordance with a second synthetic namespace of selected objects that are available to a second one or more clients.
3. The method of claim 1, wherein the synthetic namespace includes objects drawn from two or more of the exported physical file shares.
4. The method of claim 1, wherein maintaining the file location table comprises confirming the mappings of the switch file handles to the NAS file handles or path names at predetermined intervals to verify that the mappings are valid and/or to update the mappings in response to migration or replication of objects.
receiving a request having a received switch file handle from a client to access an object;
identifying a file location table based on the request; and
in the identified file location table, identifying a NAS file handle or a path name that is associated with the received switch file handle.
forwarding the request to the object location associated with the identified NAS file handle or path name.
7. The method of claim 6, wherein identifying a file location table is based on an exported physical file share or a user associated with the request.
8. The method of claim 1, wherein the synthetic namespace is organized based on one or more of a user, a group of users, a client, a location of a user, a document-type, a permission level, a date, a time, or a department, associated with selected objects.
9. A computer-implemented method for customizing a namespace in a storage network, comprising:
receiving one or more location-based pointers from one or more exported physical file shares, the one or more location-based pointers including locations of objects on the one or more exported physical file shares;
maintaining one or more file handle migration tables that map switch file handles to the one or more location based pointers, the switch file handles being independent of any changes in object locations, and a portion of entries in the one or more file handle migration tables configured in accordance with a synthetic namespace of selected objects that are available to one or more clients, the synthetic namespace comprising a subset of the objects on the one or more exported physical file shares,
wherein a portion of entries in the one or more file handle migration tables is configured to track objects that change locations, such that at least some entries in the one or more file handle migration tables are updated during a migration or replication process; and
providing a switch file handle to the one or more clients, the switch file handle designating the file location table or one or more of the objects,
wherein the switch file handle is used by one of the one or more clients to access one or more of the objects, and wherein providing the switch file handle to the one or more clients is associated with presenting to the one or more clients a customized namespace, the customized namespace comprising the synthetic namespace of the selected objects.
receive one or more NAS (Network Attached Storage) file handles or path names from one or more exported physical file shares, the NAS file handles or path names each indicative of a location of an object on an exported physical file share of a NAS file server;
receive a plurality of configurations for creating a synthetic namespace from a network administrator or user, the plurality of configurations specifying an organization of, and criteria for selecting objects to be included in, the synthetic namespace;
maintain a file location table for a plurality of selected objects that are selected according to the received plurality of configurations for the synthetic namespace, the file location table comprising mappings between each selected object's NAS file handle or path name and a corresponding switch file handle that remains independent of any location changes for the selected object, wherein the synthetic namespace comprises a subset of the objects on the one or more exported physical file shares; and
provide the switch file handles (or file handle) to a client, so that the selected objects are accessible by the client via the provided switch file handles, wherein providing the switch file handles (or file handle) to the client is associated with presenting to the client a customized namespace, the customized namespace comprising the synthetic namespace of the selected objects.
11. The apparatus of claim 10, wherein the processor is further operable to maintain a second file location table configured in accordance with a second synthetic namespace of selected objects that are available to a second one or more clients.
12. The apparatus of claim 10, wherein the synthetic namespace includes objects drawn from two or more of the exported physical file shares.
13. The apparatus of claim 10, wherein maintaining the file location table comprises confirming the mappings of the switch file handles to the NAS file handles or path names at predetermined intervals to verify that the mappings are valid and/or to update the mappings in response to migration or replication of objects.
14. The apparatus of claim 10, wherein the processor is further operable to:
receive a request from a client to access an object;
identify a user associated with the request; and
forward the request to a file location table based on the user.
15. The apparatus of claim 14, wherein the processor is further operable to:
identify a NAS file handle or path name in the file location table that is associated with the switch file handle; and
forward the request to the object location associated with the identified NAS file handle or path name.
16. The apparatus of claim 15, wherein the processor is further operable to:
responsive to not identifying a NAS file handle or path name associated with the request, forward the request to a file location table based on the exported physical file share associated with the request.
17. The apparatus of claim 14, wherein the processor is further operable to:
responsive to not identifying a user associated with the request, forward the request to a file location table based on the exported physical file share associated with the request.
18. A system for customizing a namespace in a storage network, comprising one or more computing devices configured to support:
a file server module to receive NAS (Network Attached Storage) file handles from one or more exported physical file shares, the NAS file handles including locations of objects on the exported physical file shares;
a synthetic namespace module to maintain one or more file location tables that map switch file handles to NAS file handles, the switch file handles being independent of object locations, the one or more file location tables configured in accordance with a synthetic namespace of selected objects that are available to the one or more clients, wherein the synthetic namespace is configured by a network administrator or user using a plurality of configurations, the plurality of configurations specifying an organization of, and criteria for selecting objects to be included in, the synthetic namespace, wherein the synthetic namespace comprises a subset of the objects on the one or more exported physical file shares; and
a client server module, coupled in communication with the file server module and the synthetic namespace module, the client server module configured to provide a switch file handle to the one or more clients, the switch file handle designating the file location table or one or more of the selected objects,
wherein the switch file handle is used by one of the one or more clients to access one or more of the selected objects, and wherein providing the switch file handle to the one or more clients is associated with presenting to the one or more clients a customized namespace, the customized namespace comprising the synthetic namespace of the selected objects.
19. At least one non-transitory computer readable storage medium comprising memory having computer program instructions stored thereon that are arranged to perform the following operations:
receiving one or more NAS (Network Attached Storage) file handles or path names from one or more exported physical file shares, the NAS file handles or path names each indicative of a location of an object on an exported physical file share of a NAS file server;
This application is a continuation-in-part to U.S. patent application Ser. No. 10/831,376, filed on Apr. 23, 2004, now U.S. Pat. No. 7,346,664, entitled “Transparent File Replication Using Namespace Replication,” by Thomas K. Wong et al., the contents of which are hereby incorporated by reference in its entirety.
This invention relates generally to storage networks and, more specifically, to a network device that generates a synthetic namespace to customize directories in a decentralized storage network.
By contrast, more expensive and powerful SAN (Storage Area Network) file servers use resources connected by Fibre Channel on a back-end, or a dedicated network. A SAN file system is part of the operating system or an application running on the client. But heterogeneous client operating systems may require additional copies of each file to be stored on the storage network to ensure compatibility on the SAN file server. Additionally, communication between file servers on a SAN use proprietary protocols and thus are typically provided by a common vendor. As a result, NAS file servers are preferred when price and ease of use are major considerations. However, the differences between NAS storage networks and SAN storage networks also have drawbacks.
One drawback with NAS file servers is that there is no centralized control. Accordingly, each client must maintain communication channels to each of the NAS file servers separately. When NAS file servers are either added or removed from the storage network, each client must mount or unmount directories for the associated storage resources as appropriate. This is particularly inefficient when there are changes in hardware, but not in the particular files available on the network, such as when a failing NAS file server is replaced with an identically configured back-up NAS file server.
A related drawback is that a client must be reconfigured each time a file is relocated within the storage network, such as during file migration or file replication. The client generates a NAS file handle that identifies a physical location of the directory or file object on the file server using a file handle or path name. To access the object, the client sends an object access request directly to the NAS file server. When the file is relocated to a different NAS file server, a new file handle is required.
An additional drawback with NAS file servers is that mounted directories are typically tied to the physical share. Different physical shares can be on different file servers. When mounted, the client views a namespace of the physical share to find a file or directory, and is limited to that particular physical share. However, related files and directories can be spread across different physical shares. In addition, an administrator may want to limit access or permissions of users within the physical shares.
Therefore, what is needed is a network device to customize a namespace with a synthetic namespace. Furthermore, the namespace should provide, for example, a per user or per location customization.
The present invention meets these needs by using a synthetic namespace to customized a namespace. More specifically, a synthetic namespace is generated from one or more file location tables that map switch file handles to NAS file handles. The NAS file handles can represent, an object such a file or directory, located on a file server. The NAS file handles are tied to an exported physical share, however, the switch file handles are independent of physical exports. In one example, the synthetic namespace presents a home directory corresponding to a location of a user. Other customizations on a per user, per group of users, or per location are possible.
A NAS switch, in the data path of a client and NAS file servers, reliably coordinates file migration of a source file server to a destination file server using namespace replication to track new file locations. Additionally, the NAS switch maintains data availability during time-consuming data transfers. The NAS switch in communication with the client on a front-end of the storage network, and both a source file server and a destination file server on a back-end. The NAS switch associates NAS file handles (e.g., NFS file handles or CIFS path names) received from the source and destination file servers with switch file handles that are independent of a location. The NAS switch then sends the switch file handles to the client. In response to subsequent object access requests from the client, the NAS switch substitutes switch file handles with appropriate NAS file handles for submission to the appropriate NAS file server.
In another embodiment, the NAS switch uses a file location table to generate and access synthetic namespaces. For example, each user or location can be assigned a different file location table. That file location table includes switch file handles and NAS file handles corresponding to documents selected to be part of the synthetic namespace. The file location table can be similar to a file handle migration table maintained by the NAS switch to track objects that are moved from one location on the storage network to another. While the handle migration tables typically track objects from a particular physical share, the file location tables allow namespaces to be customized without regard to physical shares containing the objects. Thus, to the NAS switch, the file location table appears to contain migrated objects.
FIG. 2 is a block diagram illustrating a network attached storage (NAS) file server module according to one embodiment of the present invention.
FIG. 11 is a flow chart illustrating a method of customizing a namespace with a synthetic namespace according to one embodiment of the present invention.
FIG. 12 is a flow chart illustrating a flow chart for retrieving objects from within the customized namespace according to one embodiment of the present invention.
FIG. 13 is a schematic diagram illustrating a synthetic namespace mapped to physical shares within a unified namespace according to one embodiment of the present invention.
Systems and methods for generating customized namespace are described. A namespace, as referred to herein, is specific to a physical share from which the namespace is exported. The namespaces of several physical shares can be combined and presented to clients as a unified namespace (also referred to as a “global namespace”). From the unified namespace, a synthetic namespace can be limited to a subset of designated objects that are independent of the physical share. For example, one synthetic namespace can be configured to include objects that are document files while another synthetic namespace can be configured to include objects that are graphical files. In another example, one synthetic namespace can be configured to include objects related to an engineering department while another synthetic namespace can be configured to include objects related to a marketing department. In other examples, synthetic namespaces can be segregated according to location, permissions (e.g., read only, read/write), date, time, etc. The synthetic namespaces and other namespaces presented to clients are managed by a NAS (Network Attached Storage) switch in the data path of a client and NAS file servers on the storage network.
Although many of the preferred embodiment and examples described herein refer to file handles used in NFS, the same embodiments and examples apply to path names used in CIFS, and generally, any other location-based pointer that is used in a public or proprietary protocol.
FIG. 1 is a high-level block diagram illustrating a storage network system 100 according to one embodiment of the present invention. The system 100 comprises a NAS switch 110 and a client 140 coupled to a network 195. The NAS switch 110, a synthetic namespace server 115, a source file server 120, and a destination file server 130, are each coupled in communication through a network 196. Note that there can be various configurations of the system 100, such as embodiments including additional clients 140, additional source and/or destination file servers 120, 130, and additional NAS switches 110. The system 100 components are implemented in, for example, a personal computer with an x86-type processor executing an operating system and/or an application program, a workstation, a specialized NAS device with an optimized operating system and/or application program, a modified server blade, etc. In one embodiment, the storage network 175 comprises a NAS using protocols such as NFS and CIFS. In another embodiment, the storage network 175 comprises a combination of NAS, SAN, and other types of storage networks. In yet another embodiment the storage network 175 comprises a decentralized standard or proprietary storage system other than NAS.
The NAS switch 110 provides continuous transparency to the client 140 with respect to object management. Specifically, the NAS switch can off-load tasks related to physical configurations, object management, object migration, object replication, efficient storage and/or other services on the storage network 175. Preferably, the NAS switch 110 emulates file server processes to the client 140 and emulates client processes to the file servers 120, 130. Accordingly, the client 140 is unaware of the NAS switch 110 since the NAS switch 110 is able to redirect NAS requests intended for the source file server 120 to appropriate locations on the destination file server 130. Thus, the client 140 submits object requests, such as file writes and directory reads, directly to the NAS switch 110. Likewise, the file servers 120, 130 could be unaware of the NAS switch 110 since the NAS switch 110 is able to resubmit requests, contained in server file handles, as if they originated from the client 140. To do so, the NAS switch 110 can use mapping, translating, bridging, packet forwarding, other network interface functionality, and other control processes to perform file handle switching, thereby relieving the client 140 of the need to track changes in a file's physical location.
In one embodiment, the NAS switch 110 comprises a client module 112 and a file server module 114 to facilitate communications and file handle switching. The file server module 114 receives exported file system directories from the file servers 120, 130 containing NAS switch handles. To create compatibility between the client 140 and the NAS switch 110, the client module 112 maps the file system directories to internal switch file systems which it sends to the client 140. To request an object, the client 140 traverses an exported switch file system and selects a switch file handle which it sends to the NAS switch 110 along with a requested operation.
In one embodiment, the file server module 114 also tracks reconfigurations resulting from migration, replication and other object relocation processes (e.g. adding or removing file server capacity) with a nested system of tables, or information otherwise linked to the switch file systems. The switch file handles are static as they are persistent through the relocation processes, but the associated NAS file handles can be dynamic as they are selected depending upon an object's current location. To track various copies of an object, the file server module 114 maintains a file handle migration table and a file handle replication table corresponding to each file system that maps NAS file handles of migrated and replicated objects to locations on the storage network 175. In one embodiment, the file server module 114 maintains a file location table corresponding to synthetic namespaces used for customization of namespaces as presented to the client 140 or a user of the client, as described in greater detail below. Further embodiments of the file server module 114 are described with respect to FIG. 2.
The client module 112 associates 310 a NAS server file handle or physical file handle (referred to herein as a NAS file handle), or a path name, with a switch file handle as described below with respect to FIG. 4. This enables the NAS switch 110 to act as an intermediary between the client 140 and the file servers 120, 130. The client 140 submits NAS requests using switch file handles as if the NAS switch 110 were a file server 120, 130, and, in turn, the file servers 120, 130 process NAS file handles from the NAS switch 110 as if they were submitted by the client 140.
In general, NAS file handles uniquely identify objects, such as a directory file server, on the file servers 120, 130, such as a directory or file, as long as that object exists. NAS file handles are file server specific, and are valid only to the file servers 120, 130 that issued the file handles. Under NFS, the process of obtaining a file handle from a file name is called a look-up, and under CIFS, the process of obtaining a path name from a file name is called an open. The NAS file handle may be formatted according to protocols such as NFS or CIFS as discussed in further detail below, e.g., with reference to Tables 1A and 1B. By contrast, a switch file handle identifies a directory or file object independent of location, making it persistent through file replications, migrations, and other data transfers. The switch file handle can be a modified NAS file handle that refers to an internal system within the NAS switch 110 rather than the source file server 120. This enables the NAS switch 110 to map persistent file handles to a choice of alternative NAS file handles. An original NAS file handle refers to an initial object location on the source file server 120, and a stored NAS file handle refers to a current object location.
Object access requests handled by the NAS switch 110 include, for example, directory and/or file reads, writes, creation, deletion, moving, copying, opening, or closing. A namespace access refers to an operation accessing or modifying the namespace such as look-up, rename, delete, or create. A file access refers to an operation accessing or modifying files such as read or write. An object can refer to a directory object or a file object. Directory objects can further comprise sub-directories and file objects within directory. As used herein, various terms are used synonymously to refer to a location of an object prior to migration (e.g., “primary”; “source”; “original”; and “first”) and various terms are used to refer to a location of the same object after migration (e.g., “replica”; “destination”; “substitute”; and “second”). Further embodiments of the NAS switch 110 and methods operating therein are described below.
The client 140 accesses resources on the file servers 120, 130 by submitting a switch file handle to the NAS switch 110. To find the switch handle, the client 140 first mounts an exported switch file system containing switch file handles. The client 140 looks-up an object to obtain its file handle and submits an associated request. From the perspective of the client 140, transactions are carried out by the NAS switch 110 having object locations that do not change. Thus, the client 140 interacts with the NAS switch 110 before and after a file replication in the same manner. A user of the client 140 can submit operations through a command line interface, a windows environment, a software application, or otherwise. In one embodiment, the NAS switch 110 further provides access to a storage network 175 other than a NAS storage network.
Optionally, the synthetic namespace server 115 is a dedicated physical share to store synthetic namespaces. The synthetic namespace server 115 contains a directory hierarchy of file location tables. To the NAS switch 110, the file location tables are similar to the file handle migration tables, although the objects referred to in the file location tables have not actually migrated. In other words, synthetic namespaces can be implemented by fake migrations. Because only metadata is stored, the directory can be replicated and distributed to multiple sites within an organization.
The network 195 facilitates data transfers between connected hosts (e.g., 110, 140). The connections to the network 195 may be wired and/or wireless, packet and/or circuit switched, and use network protocols such as TCP/IP (Transmission Control Protocol/Internet Protocol), IEEE (Institute of Electrical and Electronics Engineers) 802.11, IEEE 802.3 (i.e., Ethernet), ATM (Asynchronous Transfer Mode), or the like. The network, 195 comprises, for example, a LAN (Local Area Network), WAN (Wide Area Network), the Internet, and the like. In one embodiment, the NAS switch 110 acts as a gateway between the client 140, connected to the Internet, and the directory file server 120, and the shadow file servers 130, connected to a LAN. The network 196 is preferably a local area network providing optimal response time to the NAS switch 110. In one embodiment, the network 196 is integrated into the network 195.
FIG. 2 is a block diagram illustrating the file server module 114 according to one embodiment of the present invention. The file server module 114 comprises a file server interface 210, a migration module 220, and a redirection module 230. Generally, the file server interface 210 manages operations before migration, the migration module 220 maintains data availability during migration, and the redirection module 230 provides transparency to the client 140 after migration. Note that modules are merely exemplary groupings of functionality.
After file migration, the redirection module 230 looks-up switch file handles received from the client 140 in the file handle migration table. If an object has been migrated, the redirection module outputs a destination NAS file handle corresponding to a location on the destination file server 130. In one embodiment, the creation of synthetic namespaces appear to be migrations. Thus, the redirection module 230 looks-up switch file handles in the file location tables as well.
FIG. 4 is a flow chart illustration the method 310 of associating a NAS file handle with a switch file handle according to one embodiment of the present invention. Initially, the NAS switch 110 mounts 410 an exported directory of file systems from the primary server 120 in general, the file system organizes objects on the file servers 120, 130 into a directory hierarchy of NAS file handles. In one embodiment, the NAS switch 110 receives exported directories from associated source file servers 120 and, in turn, sends exported directories to associated clients 140.
Content of NFS Switch File Handle
=1 for NFS, type
12-size of
FIG. 11 is a flow chart illustrating a method 1100 of customizing namespaces according to one embodiment of the present invention. The NAS switch 110 receives 1110 configurations for a synthetic namespace from, for example, a network administrator or a user. The configurations can designate objects according to a user, a group of users, the client 140, a location, a document-type, etc. For example, Table 4 shows an exemplary file location table for users accessing /usr/local/bin from Boston while Table 5 shows an exemplary file location table for users accessing /usr/local/bin from London. To NAS switch 110, it /usr/local/bin appears to have migrated to different locations, depending on whether a user is in Boston or London. In one embodiment, the synthetic namespace can be configured from a union directory. The union directory results from a union of the contents of two or more member directories.
In response to the configurations, the file server module 112 generates 1120 a file location table to map switch file handles to file handles associated with selected objects. The objects can be independent of a physical share from which the object is stored. A back-end process can periodically verify that the mappings are valid, and update mappings responsive to, for example, migrated or replicated objects. The file location tables can also be updated automatically by the NAS switch 110 during migration or replication process, along with the file handle migration tables. The switch file handles are sent 1330 to the clients for use when accessing the selected objects.
FIG. 12 is a flow chart illustrating a method 1200 of retrieving an object from a customized namespace according to one embodiment of the present invention. The NAS switch 110 receives 1210 a switch file handle from the client module 140. The NAS switch 110 determines whether a user submitting the request has an associated file location table 1220. If so, the file location table is checked 1230 for an entry corresponding to the NAS file handle. If an entry is found, the NAS switch 110 maps 1240 to a NAS file handle and forwards the request to the physical share or file server storing the object, as indicated in the file location table. On the other hand, if the user does not have a customized namespace, or if there is no entry for the switch file handle, the request is forwarded 1250 to an appropriate physical share.
In one embodiment, the file handle migration table is checked, as described above, in addition to checking the file location tables.
FIG. 13 is a schematic diagram illustrating mapping between a synthetic namespace 1310 and physical shares 1320 a-c within a unified namespace 1330. The physical shares 120 a-c each have an associated namespace tied to, for example, a particular file server. The unified namespace 1330 combines the physical shares 120 a-c as a single namespace, providing transparency to the back-end system.
The synthetic namespace 1310 is organized to present a ‘users’ directory 1301 and a ‘appldata’ directory 1302. The ‘users’ directory 1301 is further segregated by first letters of a name (i.e., a, b, c, etc.). An ‘a’ directory 1303 is further segregated to an ‘an’ directory 1304 which contains an ‘anand’ directory 1305 that is associated with a user named Anand. As shown, the ‘anand’ directory 1305 is stored on the physical share 1320 a whereas an ‘andy’ directory 1306 is stored on the physical share 1320 b. Each physical share 1320 a,b,c can be stored on a separate device 1321 a,b,c, respectively.
Patent CitationsCited PatentFiling datePublication dateApplicantTitleUS5465335Jun 13, 1994Nov 7, 1995Hewlett-Packard CompanyHardware-configured operating system kernel having a parallel-searchable event queue for a multitasking processorUS5689701Dec 14, 1995Nov 18, 1997International Business Machines CorporationSystem and method for providing compatibility between distributed file system namespaces and operating system pathname syntaxUS5774715Mar 27, 1996Jun 30, 1998Sun Microsystems, Inc.File system level compression using holesUS5832261Nov 30, 1992Nov 3, 1998Fujitsu LimitedBarrier synchronizing mechanism for a parallel data processing control systemUS5890169Jun 30, 1998Mar 30, 1999Sun Microsystems, Inc.Disk fragmentation reduction using file allocation tablesUS5933825Jul 21, 1997Aug 3, 1999Apple Computer, Inc.Arbitrating concurrent access to file system objectsUS5951656Jan 31, 1997Sep 14, 1999Hewlett-Packard CompanyMethod and system for controlling queue deletions in which pointer corresponding to item to be deleted is moved back and pointers for items after deleted item are shiftedUS6070254Oct 17, 1997May 30, 2000International Business Machines CorporationAdvanced method for checking the integrity of node-based file systemsUS6101508Apr 15, 1998Aug 8, 2000Hewlett-Packard CompanyClustered file management for network resourcesUS6192408Sep 26, 1997Feb 20, 2001Emc CorporationNetwork file server sharing local caches of file access information in data processors assigned to respective file systemsUS6314460Oct 30, 1998Nov 6, 2001International Business Machines CorporationMethod and apparatus for analyzing a storage network based on incomplete information from multiple respective controllersUS6341302Sep 24, 1998Jan 22, 2002Compaq Information Technologies Group, LpEfficient inter-task queue protocolUS6353837Jun 30, 1998Mar 5, 2002Emc CorporationMethod and apparatus providing mass storage access from systems using different meta-data formatsUS6389427May 28, 1999May 14, 2002Redleaf Group, Inc.File system performance enhancementUS6408298Dec 15, 1999Jun 18, 2002Microsoft CorporationMethods and systems for copying and moving across virtual namespacesUS6442548Jun 25, 1999Aug 27, 2002International Business Machines CorporationDatabase interface for database unaware applicationsUS6453354Mar 3, 1999Sep 17, 2002Emc CorporationFile server system using connection-oriented protocol and sharing data sets among data moversUS6473401Apr 5, 1999Oct 29, 2002Iscale, Inc.Self-scaling method for exploiting cached resources across organizational boundaries to enhance user response time and to reduce server and network loadUS6606690Feb 20, 2001Aug 12, 2003Hewlett-Packard Development Company, L.P.System and method for accessing a storage area network as network attached storageUS6615365Mar 22, 2000Sep 2, 2003Powerquest CorporationStoring a computer disk image within an imaged partitionUS6633887Feb 26, 2002Oct 14, 2003Fujitsu LimitedInformation management apparatus dividing files into paragraph information and header information linked to the paragraph information and recording medium thereofUS6694431Oct 12, 1999Feb 17, 2004International Business Machines CorporationPiggy-backed key exchange protocol for providing secure, low-overhead browser connections when a server will not use a message encoding scheme proposed by a clientUS6697846Mar 20, 1998Feb 24, 2004Dataplow, Inc.Shared file systemUS6711625Jan 14, 2000Mar 23, 2004Hewlett-Packard Development Company, L.P.Kernel file I/O management system and methodUS6738883Sep 23, 2002May 18, 2004Matrix Semiconductor, Inc.Memory devices and methods for use therewithUS6931410Jan 11, 2002Aug 16, 2005International Business Machines CorporationMethod, apparatus, and program for separate representations of file system locations from referring file systemsUS6938039Jun 30, 2000Aug 30, 2005Emc CorporationConcurrent file across at a target file server during migration of file systems between file servers using a network file system access protocolUS6983379Jun 30, 2000Jan 3, 2006Hitwise Pty. Ltd.Method and system for monitoring online behavior at a remote site and creating online behavior profilesUS6985956Nov 2, 2001Jan 10, 2006Sun Microsystems, Inc.Switching systemUS6996714Dec 14, 2001Feb 7, 2006Cisco Technology, Inc.Wireless authentication protocolUS7054927Jan 29, 2002May 30, 2006Adaptec, Inc.File system metadata describing server directory informationUS7072917Apr 26, 2004Jul 4, 2006Neopath Networks, Inc.Extended storage capacity for a network file serverUS7089293Nov 2, 2001Aug 8, 2006Sun Microsystems, Inc.Switching system method for discovering and accessing SCSI devices in response to queryUS7092976Jun 24, 2003Aug 15, 2006International Business Machines CorporationParallel high speed backup for a storage area network (SAN) file systemUS7096253Aug 26, 2002Aug 22, 2006Stream Theory, Inc.Method and apparatus for streaming softwareUS7103628Jun 20, 2002Sep 5, 2006Jp Morgan Chase & Co.System and method for dividing computationsUS7120666Oct 30, 2002Oct 10, 2006Riverbed Technology, Inc.Transaction accelerator for client-server communication systemsUS7127477Nov 6, 2002Oct 24, 2006Everyware Solutions Inc.Method and system for access to automatically synchronized remote filesUS7254636Mar 14, 2003Aug 7, 2007Cisco Technology, Inc.Method and apparatus for transparent distributed network-attached storage with web cache communication protocol/anycast and file handle redundancyUS7272613Oct 26, 2001Sep 18, 2007Intel CorporationMethod and system for managing distributed content and related metadataUS7272654 *Mar 4, 2004Sep 18, 2007Sandbox Networks, Inc.Virtualizing network-attached-storage (NAS) with a compact table that stores lossy hashes of file names and parent handles rather than full namesUS7308473 *Jul 29, 2002Dec 11, 2007Rockwell Automation Technologies, Inc.System and methodology that facilitates client and server interaction in a distributed industrial automation environmentUS7308709Apr 27, 2000Dec 11, 2007Microsoft CorporationSystem and method for managing and authenticating services via service principal namesUS7313579Sep 21, 2004Dec 25, 2007Hitachi, Ltd.Network storage system and handover method between plurality of network storage devicesUS7324995Nov 17, 2003Jan 29, 2008Rackable Systems Inc.Method for retrieving and modifying data elements on a shared mediumUS7346664Apr 23, 2004Mar 18, 2008Neopath Networks, Inc.Transparent file migration using namespace replicationUS7386610Sep 18, 2000Jun 10, 2008Hewlett-Packard Development Company, L.P.Internet protocol data mirroringUS7441011Oct 23, 2003Oct 21, 2008Microsoft CorporationTruth on client persistent cachingUS7475142May 13, 2005Jan 6, 2009Cisco Technology, Inc.CIFS for scalable NAS architectureUS7512673Jan 2, 2003Mar 31, 2009Attune Systems, Inc.Rule based aggregation of files and transactions in a switched file systemUS7562110Jul 14, 2009F5 Networks, Inc.File switch and switched file systemUS7587422Apr 23, 2004Sep 8, 2009Neopath Networks, Inc.Transparent file replication using namespace replicationUS7587471Mar 14, 2003Sep 8, 2009Hitachi, Ltd.System and method for virtualizing network storages into a single file system viewUS7720796Jan 3, 2006May 18, 2010Neopath Networks, Inc.Directory and file mirroring for migration, snapshot, and replicationUS7831641Apr 26, 2004Nov 9, 2010Neopath Networks, Inc.Large file support for a network file serverUS7844646Nov 30, 2010Netapp, Inc.Method and apparatus for representing file system metadata within a database for efficient queriesUS20020013832Apr 13, 2001Jan 31, 2002Hubbard Edward A.Software-based network attached storage services hosted on massively distributed parallel computing networksUS20020111929Feb 15, 2001Aug 15, 2002Microsoft CorporationConcurrent data recall in a hierarchical storage environment using plural queuesUS20020120763Jan 10, 2002Aug 29, 2002Z-Force Communications, Inc.File switch and switched file systemUS20020133491Oct 26, 2001Sep 19, 2002Prismedia Networks, Inc.Method and system for managing distributed content and related metadataUS20020154645Jun 13, 2002Oct 24, 2002Hu Lee ChuanSystem for bypassing a server to achieve higher throughput between data network and data storage systemUS20020161855Dec 5, 2000Oct 31, 2002Olaf ManczakSymmetric shared file storage systemUS20020184244Jun 1, 2001Dec 5, 2002International Business Machines CorporationSystem and method for parallelizing file archival and retrievalUS20020199060Jul 1, 2002Dec 26, 2002Peters Eric C.Computer system and process for transferring multiple high bandwidth streams of data between multiple storage units and multiple applications in a scalable and reliable mannerUS20030037061Apr 30, 2002Feb 20, 2003Gautham SastriData storage system for a multi-client network and method of managing such systemUS20030046270Aug 30, 2002Mar 6, 2003Arkivio, Inc.Techniques for storing data based upon storage policiesUS20030046335Aug 30, 2001Mar 6, 2003International Business Machines CorporationEfficiently serving large objects in a distributed computing networkUS20030056112Aug 26, 2002Mar 20, 2003Jeffrey VinsonMethod and apparatus to allow remotely located computer programs and/or data to be accessed on a local computer in a secure, time-limited manner, with persistent cachingUS20030110263Oct 23, 2002Jun 12, 2003Avraham ShilloManaging storage resources attached to a data networkUS20030120948 *Dec 21, 2001Jun 26, 2003Schmidt Donald E.Authentication and authorization across autonomous network systemsUS20030126247Jan 2, 2002Jul 3, 2003Exanet Ltd.Apparatus and method for file backup using multiple backup devicesUS20030140051Aug 16, 2002Jul 24, 2003Hitachi, Ltd.System and method for virtualizing a distributed network storage as a single-view file systemUS20030154236Jan 22, 2002Aug 14, 2003Shaul DarDatabase Switch enabling a database area networkUS20030177178Dec 11, 2002Sep 18, 2003Valve LlcMethod and system for effectively communicating file properties and directory structures in a distributed file systemUS20030182313Mar 19, 2002Sep 25, 2003Federwisch Michael L.System and method for determining changes in two snapshots and for transmitting changes to destination snapshotUS20030195903Apr 23, 2003Oct 16, 2003Manley Stephen L.System and method for asynchronous mirroring of snapshots at a destination using a purgatory directory and inode mappingUS20030204613Jan 23, 2003Oct 30, 2003Hudson Michael D.System and methods of streaming media files from a dispersed peer network to maintain quality of serviceUS20030204670Apr 25, 2002Oct 30, 2003Holt Keith W.Method for loosely coupling metadata and data in a storage arrayUS20030220899Feb 14, 2003Nov 27, 2003Tadashi NumanoiStorage device management method, system and programUS20030220985Jan 3, 2003Nov 27, 2003Hitachi,Ltd.System and method for virtualizing network storages into a single file system viewUS20040010714Jul 11, 2002Jan 15, 2004Stewart Graham W.Authenticating legacy service via web technologyUS20040024963Aug 5, 2002Feb 5, 2004Nisha TalagalaMethod and system for striping data to accommodate integrity metadataUS20040054748Sep 16, 2002Mar 18, 2004Emmanuel AckaouyApparatus and method for processing data in a networkUS20040078465Feb 13, 2003Apr 22, 2004Coates Joshua L.Methods and apparatus for load balancing storage nodes in a distributed stroage area network systemUS20040088297Feb 13, 2003May 6, 2004Coates Joshua L.Distributed network attached storage systemUS20040103104Feb 21, 2003May 27, 2004Junichi HaraSnapshot creating method and apparatusUS20040117438Nov 2, 2001Jun 17, 2004John ConsidineSwitching systemUS20040133577Jan 2, 2003Jul 8, 2004Z-Force Communications, Inc.Rule based aggregation of files and transactions in a switched file systemUS20040133606 *Jan 2, 2003Jul 8, 2004Z-Force Communications, Inc.Directory aggregation for files distributed over a plurality of servers in a switched file systemUS20040133650Jan 2, 2003Jul 8, 2004Z-Force Communications, Inc.Transaction aggregation in a switched file systemUS20040133652Jan 2, 2003Jul 8, 2004Z-Force Communications, Inc.Aggregated opportunistic lock and aggregated implicit lock management for locking aggregated files in a switched file systemUS20040139167Dec 6, 2002Jul 15, 2004Andiamo Systems Inc., A Delaware CorporationApparatus and method for a scalable network attach storage systemUS20040153481Jan 21, 2004Aug 5, 2004Srikrishna TalluriMethod and system for effective utilization of data storage capacityUS20040186849Aug 28, 2003Sep 23, 2004Hitachi, Ltd.File storage service system, file management device, file management method, ID denotative NAS server and file reading methodUS20040267752Apr 23, 2004Dec 30, 2004Wong Thomas K.Transparent file replication using namespace replicationUS20040267831Apr 26, 2004Dec 30, 2004Wong Thomas K.Large file support for a network file serverUS20050033932Sep 8, 2004Feb 10, 2005Microsoft CorporationSystem and method for data migrationUS20050055402Jan 30, 2004Mar 10, 2005Eiichi SatoFile sharing device and inter-file sharing device data migration methodUS20050080981May 13, 2004Apr 14, 2005International Business Machines CorporationStructure and method for managing workshares in a parallel regionUS20050125503Sep 15, 2004Jun 9, 2005Anand IyengarEnabling proxy services using referral mechanismsUS20050188211May 10, 2004Aug 25, 2005Scott Steven J.IP for switch based ACL'sUS20050198062Mar 7, 2005Sep 8, 2005Shapiro Richard B.Method and apparatus for accelerating data access operations in a database systemUS20050262102Jul 1, 2005Nov 24, 2005Anderson Owen TMethod, apparatus, and program for separate representations of file system locations from referring file systemsUS20060080371Sep 30, 2005Apr 13, 2006Wong Chi MStorage policy monitoring for a storage networkUS20060129627Nov 21, 2005Jun 15, 2006Mangosoft Corp.Internet-based shared file service with native PC client access and semantics and distributed version controlUS20060161746Jan 3, 2006Jul 20, 2006Wong Chi MDirectory and file mirroring for migration, snapshot, and replicationUS20060253501May 9, 2005Nov 9, 2006Microsoft CorporationFast and reliable synchronization of file system directoriesUS20070024919Jun 29, 2006Feb 1, 2007Wong Chi MParallel filesystem traversal for transparent mirroring of directories and filesUS20070074207Sep 27, 2005Mar 29, 2007Sony Computer Entertainment Inc.SPU task manager for cell processorUS20070136308Oct 2, 2006Jun 14, 2007Panagiotis TsirigotisAccumulating access frequency and file attributes for supporting policy based storage managementUS20080114854Jan 24, 2008May 15, 2008Neopath Networks, Inc.Transparent file migration using namespace replicationEP0108338A2Oct 26, 1983May 16, 1984International Business Machines CorporationParallel queueing methodEP0926585A2Dec 16, 1998Jun 30, 1999Hitachi, Ltd.Subsystem replacement methodEP1209556A2Oct 17, 2001May 29, 2002Microsoft CorporationMethod and system for transparently extending non-volatile storageEP1311122A2Oct 23, 2002May 14, 2003Quantum CorporationUsing NAS appliance to build a non-conventional distributed video serverEP1396789A2Feb 26, 2003Mar 10, 2004Hitachi, Ltd.Information processing system having data migration device* Cited by examinerNon-Patent CitationsReference1"Leveraging the Benefits of the EMC CLARiiON IP4700 Network File Server With the Oracle8i Database," an Engineering White Paper, Mar. 5, 2002, EMC Corporation.2"Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration," for PCT/US04/12844, Mar. 14. 2005, 14 pages.3Allowed Claims, U.S. Appl. No. 10/831,376.4Allowed Claims, U.S. Appl. No. 10/831,701.5Allowed Claims, U.S. Appl. No. 10/832,927.6Anderson, D.C. et al., "Interposed Request Routing for Scalable Network Storage," ACM Transactions on Computer Systems, Feb. 2002, vol. 20, No. 1, pp. 1-24.7Bright, J.D. et al., "A Scalable Architecture for Clustered Network Attached Storage," Twentieth IEEE/Eleventh NASA Goddard Conference on Mass Storage Systems & Technologies, Apr. 7-10, 2003, 12 pages, Paradise Point Resort, San Diego, CA, USA.8Cams et al. (Oct. 1, 2000) "PVFS: A Parallel File System for Linux Clusters", Proceedings of the 4th Annual Linux Showcase and Conference, vol. 4, pp. 317-327, XP002532238, USENIX ASSOC, Atlanta, Georgia.9Chinese Office Action dated Nov. 20, 2009 for CN Patent Application No. 200680032142.X.10European Examination Report dated Nov. 9, 2010 issued in 04 750 678.7 -1245.11European Extended Search Report, supplementary European Search Report, and European Search Opinion dated Jul. 26, 2011 issued in EP 05 802 942.2.12European Extended Search Report, Supplementary Search Report and Search Opinion dated Feb. 25, 2011 issued in EP 06 785 872.0.13European Extended Search Report, Supplementary Search Report and Search Opinion dated Jun. 4, 2010 issued in EP 06 81 5981.14European Office Action dated Apr. 9, 2009 for EP Patent Application No. 04750678.7.15European Office Action dated Feb. 22, 2010 for EP Patent Application No. 04750678.7.16European Search Report dated Dec. 14, 2008 for EP Patent Application No. 04750678.7.17European Summons to attend oral proceedings dated Oct. 6, 2011 issued in EP Patent Application No. 04 750 678.7-1245.18Examiner Interview , U.S. Appl. No. 11/241,554, mailed Sep. 30, 2009.19Final Office Action dated Jul. 21, 2009 for U.S. Appl. No. 10/942,762.20Final Office Action mailed Aug. 10, 2007, for U.S. Appl. No. 10/831,376.21Final Office Action mailed Aug. 31, 2007 for U.S. Appl. No. 10/832,785.22Final Office Action mailed Jan. 5, 2009 for U.S. Appl. No. 10/832,785.23Final Office Action mailed Sep. 12, 2007, for U.S. Appl. No. 10/831,701.24Final Office Action, U.S. Appl. No. 10/831,701, mailed Jan. 5, 2009.25Final Office Action, U.S. Appl. No. 11/241,554, mailed Aug. 19, 2009.26Final Office Action, U.S. Appl. No. 11/241,554, mailed Jul. 25, 2008.27Final Office Action, U.S. Appl. No. 11/324,845, mailed Sep. 5, 2008.28Goldick, J., "Retry of Extending Networking Design Notes," PSC, Carnegie-Mellon University, Feb. 1995, 42 pages.29International Preliminary Report on Patentability dated Apr. 10, 2008 for PCT Application No. PCT/US2006/038361.30International Preliminary Report on Patentability dated Mar. 5, 2009, PCT Application No. PCT/US2005/035624.31International Search Report mailed May 8, 2007 for PCT Application No. US/2006/25430.32International Search Report sent Sep. 30, 2008 for PCT Application No. PCT/US05/35624.33Japanese Office Action (Notice of Grounds for Rejection) dated May 10, 2011 issued in JP 2007-534880.34Japanese Office Action dated Dec. 22, 2009 for JP Patent Application No. 2006-513342.35Katsurashima et al. (2003) "Design and Evaluation of CIFS Server Virtualization Method", Technical Research Report (IEICE), The Institute of Electronics Information and Communication Engineers, 103(248): 73-78.36Non-Final Office Action dated Jan. 15, 2010 for U.S. Appl. No. 10/942,762.37Non-Final Office Action dated Jan. 8, 2009 for U.S. Appl. No. 10/942,762.38Notice of Allowance mailed Dec. 2, 2009, for U.S. Appl. No. 11/324,845.39Notice of Allowance mailed Feb. 9, 2006 for U.S. Appl. No. 10/832,927.40Notice of Allowance mailed Mar. 16, 2010, for U.S. Appl. No. 11/324,845.41Notice of Allowance mailed Oct. 22, 2007, for U.S. Appl. No. 10/831,376.42Notice of Allowance mailed Sep. 21, 2009, for U.S. Appl. No. 11/324,845.43Notice of Allowance with Examiner Interview and Amendment dated Apr. 21, 2010 for U.S. Appl. No. 10/832,785.44Notice of Allowance with Examiner Interview and Amendment dated Dec. 29, 2009 for U.S. Appl. No. 10/832,785.45Notice of Allowance, U.S. Appl. No. 10/831,701, mailed May 14, 2009.46Notification of Transmittal of the International Search Report and the Written Opinion, PCT/US04/12841, Oct. 13, 2004, 9 pages.47Notification of Transmittal of the International Search Report and the Written Opinion, PCT/US04/30180, Mar. 27, 2006, 8 pages.48Notification of Transmittal of the International Search Report and Written Opinion, PCT/US04/12846, Sep. 28, 2004, 8 pages.49Notification of Transmittal of the International Search Report and Written Opinion, PCT/US04/12847, Nov. 3, 2004, 7 pages.50Office Action mailed Dec. 18, 2006 for U.S. Appl. No. 10/831,701.51Office Action mailed Feb. 3, 2005 for U.S. Appl. No. 10/832,927.52Office Action mailed Feb. 9, 2009, for U.S. Appl. No. 11/324,845.53Office Action mailed Jan. 11, 2008, for U.S. Appl. No. 11/324,845.54Office Action mailed Jan. 3, 2007 for U.S. Appl. No. 10/832,785.55Office Action mailed Jun. 22, 2005 for U.S. Appl. No. 10/832,927.56Office Action mailed Mar. 23, 2007, for U.S. Appl. No. 10/831,376.57Office Action U.S. Appl. No. 11/537,997, dated Apr. 15, 2010.58Office Action, U.S. Appl. No. 10/831,701, mailed Jun. 25, 2008.59Office Action, U.S. Appl. No. 10/832,785, mailed Jun. 8, 2009.60Office Action, U.S. Appl. No. 10/832,785, mailed May 28, 2008.61Office Action, U.S. Appl. No. 11/241,554, mailed Aug. 8, 2007.62Office Action, U.S. Appl. No. 11/241,554, mailed Feb. 5, 2010.63Office Action, U.S. Appl. No. 11/241,554, mailed Jan. 8, 2009.64Office Action, U.S. Appl. No. 11/537,997, mailed Sep. 25, 2009.65PCT International Preliminary Report on Patentability and Written Opinion dated Aug. 29, 2007 issued in PCT/US2006/038361.66PCT International Preliminary Report on Patentability and Written Opinion dated Jan. 9, 2008 issued in PCT/US2006/25430.67PCT International Search Report dated Aug. 29, 2007 issued in PCT/US2006/038361.68Sheth et al., "Data structure distribution and multi-threading of Linux file system for multiprocessors", 5th International Conference on High Performance Computing, 1998 (HIPC '98); Madras, India Dec. 17-20, 1998, IEEE Comput. Soc, US, Dec. 17, 1998, pp. 97-104, XP010317644, DOI: DOI:10.1109/HIPC.1998.737976.69U.S. Appl. No. 60/465,578, filed Apr. 24, 2003.70U.S. Appl. No. 60/465,579, filed Apr. 24, 2003.71U.S. Appl. No. 60/465,580, filed Apr. 24, 2003.72U.S. Appl. No. 60/478,154, filed Apr. 24, 2003.73U.S. Appl. No. 60/503,190, filed Sep. 15, 2003.74U.S. Appl. No. 60/615,002, filed Sep. 30, 2004.75U.S. Appl. No. 60/641,217, filed Dec. 31, 2004.76U.S. Appl. No. 60/667,567, filed Mar. 31, 2005, Wong et al.77U.S. Appl. No. 60/722,465, filed Sep. 30, 2005, Tsirigotis et al.78US Advisory Action dated Nov. 21, 2007 issued in U.S. Appl. No. 10/832,785.79US Advisory Action dated Nov. 21, 2008 issued in U.S. Appl. No. 11/324,845.80US Advisory Action dated Nov. 27, 2007 issued in U.S. Appl. No. 10/831,701.81US Examiner Interview Summary dated Jul. 19, 2010 issued in U.S. Appl. No. 11/537,997.82US Examiner Interview Summary dated Mar. 31, 2009 issued in U.S. Appl. No. 11/241,554.83US Examiner Interview Summary dated Oct. 12, 2010 issued in U.S. Appl. No. 10/942,762.84US Examiner Interview Summary dated Sep. 14, 2010 issued in U.S. Appl. No. 11/241,554.85US Final Office Action dated Feb. 25, 2011 issued in U.S. Appl. No. 12/019,582.86US Notice of Allowance and Examiner-Initiated Interview Summary dated Aug. 9, 2010 issued in U.S. Appl. No. 10/832,785.87US Notice of Allowance dated Aug. 5, 2011 issued in U.S. Appl. No. 11/537,997.88US Notice of Allowance dated Jan. 13, 2012 issued in U.S. Appl. No. 12/019,582.89US Notice of Allowance dated Jul. 6, 2011 issued in U.S. Appl. No. 11/241,554.90US Notice of Allowance dated Jun. 15, 2011 issued in U.S. Appl. No. 12/019,582.91US Notice of Allowance dated Nov. 28, 2011 issued in U.S. Appl. No. 11/537,997.92US Notice of Allowance dated Oct. 28, 2011 issued in U.S. Appl. No. 11/241,554.93US Notice of Allowance dated Sep. 30, 2011 issued in U.S. Appl. No. 12/019,582.94US Office Action dated Jan. 20, 2011 issued in U.S. Appl. No. 11/478,998.95US Office Action dated Jul. 8, 2011 issued in U.S. Appl. No. 11/478,998.96US Office Action dated Mar. 31, 2011 issued in U.S. Appl. No. 11/537,997.97US Office Action dated Sep. 22, 2010 issued in U.S. Appl. No. 12/019,582.98US Office Action Final dated Aug. 3, 2010 issued in U.S. Appl. No. 10/942,762.99US Office Action Final dated Dec. 22, 2011 issued in U.S. Appl. No. 11/478,998.100US Office Action Final dated Jul. 21, 2010 issued in U.S. Appl. No. 11/241,554.101Written Opinion mailed May 8, 2007 for PCT Application No. US/2006/25430.102Written Opinion sent Sep. 30, 2008 for PCT Application No. PCT/US05/35624.103Yamakawa et al., "NAS Switch: Virtualized Integration Techniques of NFS Server", Engineering Research Report of Institute of Electronics, Information and Communication Engineers published by Institute of Electronics, Information and Communication Engineers, Japan, Aug. 12, 2002, vol. 102, No. 275, pp. 13-18. Japan.Referenced byCiting PatentFiling datePublication dateApplicantTitleUS8321915 *Nov 27, 2012Amazon Technologies, Inc.Control of access to mass storage systemUS8539081Sep 15, 2004Sep 17, 2013Neopath Networks, Inc.Enabling proxy services using referral mechanismsUS8832697Jun 29, 2006Sep 9, 2014Cisco Technology, Inc.Parallel filesystem traversal for transparent mirroring of directories and filesUS20050125503 *Sep 15, 2004Jun 9, 2005Anand IyengarEnabling proxy services using referral mechanismsUS20070024919 *Jun 29, 2006Feb 1, 2007Wong Chi MParallel filesystem traversal for transparent mirroring of directories and files* Cited by examinerClassifications U.S. Classification709/226International ClassificationG06F15/173Cooperative ClassificationG06F17/30079, G06F17/30212European ClassificationG06F17/30F8D3, G06F17/30F1MLegal EventsDateCodeEventDescriptionJul 27, 2006ASAssignmentOwner name: NEOPATH NETWORKS, INC., CALIFORNIAFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:WONG, THOMAS K.;IYENGAR, ANAND;TSIRIGOTIS, PANAGIOTIS;AND OTHERS;REEL/FRAME:018019/0160;SIGNING DATES FROM 20060626 TO 20060627Owner name: NEOPATH NETWORKS, INC., CALIFORNIAFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:WONG, THOMAS K.;IYENGAR, ANAND;TSIRIGOTIS, PANAGIOTIS;AND OTHERS;SIGNING DATES FROM 20060626 TO 20060627;REEL/FRAME:018019/0160Jul 17, 2015ASAssignmentOwner name: CISCO TECHNOLOGY, INC., CALIFORNIAFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:CISCO SYSTEMS, INC.;REEL/FRAME:036120/0214Effective date: 20150716Owner name: CISCO SYSTEMS, INC., CALIFORNIAFree format text: MERGER;ASSIGNOR:NEOPATH NETWORKS, INC.;REEL/FRAME:036120/0201Effective date: 20100203Nov 30, 2015FPAYFee paymentYear of fee payment: 4RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services