System for operating NFSv2 and NFSv3 clients with federated namespace

• US 8,516,149 B1
• Filed: 12/17/2010
• Issued: 08/20/2013
• Est. Priority Date: 12/17/2010
• Status: Active Grant

• Current Assignee: Emc IP Holding Company LLC (Dell Technologies Inc.)
• Original Assignee: EMC Corporation (Dell Technologies Inc.)
• Inventors: Edmett Stacey, Christopher Howard
• Primary Examiner(s): Daftuar, Saket K
• Application Number:
  US12/971,792
• Time in Patent Office: 977 Days
• Field of Search: 709/201, 709/203, 709/213, 709/214, 709/215, 709/216, 709/217, 709/218, 709/219, 709/226, 709/227, 709/228, 709/229, 709/230, 709/231, 709/232, 709/238, 709/245, 709/246, 707/200, 707/822, 707/E17.01, 707/E17.032, 707/827, 707/E17.005, 707/E17.006, 707/737, 707/E17.044, 707/204, 707/1, 707/10, 707/705, 707781-788, 707/769, 707/809, 707609-686, 714/3, 714/4, 714/5, 714/6, 714/E11.084, 714/8, 714/42, 714/54, 714/4.1, 714/4.11, 714/4.12, 711/111, 711/112, 711/113, 711/114, 711117-140, 711147-173, 711/213
• US Class Current: 709/238
• CPC Class Codes: G06F 16/183 Provision of network file services by network file servers, e.g. by using NFS, CIFS network file access protocols H04L67/1097
• CPC Class Codes: H04L 45/00 Routing or path finding of packets in data switching networks routing or path finding in wireless networks H04W40/00
• CPC Class Codes: Y10S 707/99931 Database or file accessing
• CPC Class Codes: Y10S 707/9994 Distributed or remote access
• CPC Class Codes: Y10S 707/99955 Archiving or backup

Abstract

An information retrieval system having: a client adapted for accessing a plurality of file sets stored on one of a plurality of file servers; a plurality of file servers configured to operate with a federated file system namespace; and a memory for storing re-direction information accessible by the client for identifying a request issued by the client for a file set at a first location in the namespace where the file set is located at a second, different location on one of the file servers and wherein the client in examining the re-direction information in the memory, re-directs the request to the second location in accordance with the re-direction information.

Claims

1. An information retrieval system, comprising:

a NFS version 2 or 3 client, wherein the NFS version 2 or 3 client operating without junctions support;

a file server system accessible by the client and operating with a NFS version 4 federated namespace, wherein file sets therein are linked together using junctions;

a memory storing re-direction information accessible by the NFS version 2 or 3 client for identifying a request issued by the NFS version 2 or 3 client for the file set at a first location in the NFS version 4 federated namespace of the file server where the file set is located at a second, different location and wherein the client examining the re-direction information in the memory, re-directs the request to the second location in accordance with the re-direction information.

2. The information retrieval system recited in claim 1 wherein the file server system includes a plurality of file servers operating with the NFS version 4 federated namespace.

3. The information retrieval system recited in claim 2 wherein the memory stores an automount map accessible to the client.

4. The information retrieval system recited in claim 3 wherein the automount map stores the first location in the namespace from which the client must be re-directed to the second location also stored in the automount map.

5. The information retrieval system recited in claim 2 wherein the memory stores a symbolic link relating the first location to the second location.

7. The information retrieval system recited in claim 5 wherein the symbolic link in the namespace is the first location and a target of the symbolic link is the second location.

8. The information retrieval system recited in claim 1 wherein the file server system includes a single server operating with the federated namespace.

9. The information retrieval system recited in claim 8 wherein the memory stores a symbolic link relating the first location to the second location.

6. The information retrieval system recited 5 wherein the memory is in the server.

10. The information retrieval system recited 9 wherein the memory is in the server.

11. The information retrieval system recited in claim 10 wherein the symbolic link in the namespace is the first location and a target of the symbolic link is the second location.

12. An information retrieval system, comprising:

a file server system operating with federated namespace wherein file sets therein are linked together using junctions;

a client, including an NFS version 2 or 3, having access to the file server system, wherein the client operating without support for the junctions provided by the file server;

a memory storing re-direction information accessible by the client being operating without support for the junctions provided by the file server for identifying a request issued by the client operating without support for the junctions provided by the file server for a file set at a first location in the federated namespace where the file set is located at a second, different location and wherein the client examining the re-direction information in the memory, re-directs the request to the second location in accordance with the re-direction information.

13. The information retrieval system recited in claim 12 wherein the file server system includes a plurality of file servers operating with the federated namespace.

14. The information retrieval system recited in claim 13 wherein the memory stores an automount map accessible to the client.

15. The information retrieval system recited in claim 14 wherein the automount map stores the first location in the namespace from which the client must be re-directed to the second location also stored in the automount map.

16. The information retrieval system recited in claim 13 wherein the memory stores a symbolic link relating the first location to the second location.

18. The information retrieval system recited in claim 16 wherein the symbolic link in the namespace is the first location and a target of the symbolic link is the second location.

19. The information retrieval system recited in claim 12 wherein the file server system includes a single server operating with the federated namespace.

20. The information retrieval system recited in claim 19 wherein the memory stores a symbolic link relating the first location to the second location.

17. The information retrieval system recited 16 wherein the memory is in the server.

21. The information retrieval system recited 20 wherein the memory is in the server.

22. The information retrieval system recited in claim 21 wherein the symbolic link in the namespace is the first location and a target of the symbolic link is the second location.

23. An information retrieval system, comprising:

a file server system operating with federated namespace wherein file sets therein are linked together using junctions;

a NFS version 2 or 3 client having access to the file server system, wherein the NFS version 2 or 3 client operating without junctions support;

a memory storing re-direction information accessible by the NFS version 2 or 3 client for identifying a request issued by the NFS version 2 or 3 client for a file set at a first location in the federated namespace where the file set is located at a second, different location and wherein the NFS version 2 or 3 client examining the re-direction information in the memory, re-directs the request to the second location in accordance with the re-direction information.

24. The information retrieval system recited in claim 23 wherein the file server system includes a plurality of file servers operating with the federated namespace.

25. The information retrieval system recited in claim 24 wherein the memory stores an automount map accessible to the client.

26. The information retrieval system recited in claim 25 wherein the automount map stores the first location in the namespace from which the client must be re-directed to the second location also stored in the automount map.

27. The information retrieval system recited in claim 24 wherein the memory stores a symbolic link relating the first location to the second location.

29. The information retrieval system recited in claim 27 wherein the symbolic link in the namespace is the first location and a target of the symbolic link is the second location.

30. The information retrieval system recited in claim 23 wherein the file server system includes a single server operating with the federated namespace.

31. The information retrieval system recited in claim 30 wherein the memory stores a symbolic link relating the first location to the second location.

28. The information retrieval system recited 27 wherein the memory is in the server.

32. The information retrieval system recited 31 wherein the memory is in the server.

33. The information retrieval system recited in claim 32 wherein the symbolic link in the namespace is the first location and a target of the symbolic link is the second location.