FedFsNfsServer0.9
From Linux NFS
Chucklever (Talk | contribs) (Created page with "== Prepare mountd to resolve junctions == * rpc.mountd updated with junction support (nfs-utils 1.2.6 or later, built with the nfs-plugin.h header present) * libnfsjunct.so inst...") |
Chucklever (Talk | contribs) |
||
| Line 1: | Line 1: | ||
| + | == Project: fedfs-utils == | ||
| + | [ | ||
| + | [[FedFsUtilsProject|Project Home]] | | ||
| + | [[FedFsUtilsNews|News]] | | ||
| + | [[FedFsUtilsDownloads|Downloads]] | | ||
| + | [[FedFsUtilsDocs|Docs]] | | ||
| + | [[FedFsUtilsMailingLists|Mailing Lists]] | | ||
| + | [[FedFsUtilsSourceControl|Source Control]] | | ||
| + | [[FedFsUtilsIssues|Issues]] | ||
| + | ] | ||
| + | ---- | ||
| + | |||
| + | == Introduction == | ||
| + | |||
| + | A ''junction'' is a link between two shared file systems. The two shared file systems may not reside on the same server. There may be more than one replica of the linked-to shared file system, stored on several different file servers. Each replica of the linked-to file system is called a ''location''. | ||
| + | |||
| + | Junctions store a list of locations. Each location in the list is represented as an export path paired with a server name or IP address. When a file-access client encounters a junction, the file server (via a ''referral'') provides the stored list of locations to the client, who chooses a location and mounts it. | ||
| + | |||
| + | A file server must convert the information stored in a junction into a list of locations that's in a format which is correct for the protocol clients are using to access the server (say, NFSv4). The server-side process of recognizing a junction and converting its contents is known as ''junction resolution''. | ||
| + | |||
| + | This article describes how to configure a Linux NFS server to resolve junctions. | ||
| + | |||
== Prepare mountd to resolve junctions == | == Prepare mountd to resolve junctions == | ||
Revision as of 16:30, 17 October 2012
Contents |
Project: fedfs-utils
[ Project Home | News | Downloads | Docs | Mailing Lists | Source Control | Issues ]
Introduction
A junction is a link between two shared file systems. The two shared file systems may not reside on the same server. There may be more than one replica of the linked-to shared file system, stored on several different file servers. Each replica of the linked-to file system is called a location.
Junctions store a list of locations. Each location in the list is represented as an export path paired with a server name or IP address. When a file-access client encounters a junction, the file server (via a referral) provides the stored list of locations to the client, who chooses a location and mounts it.
A file server must convert the information stored in a junction into a list of locations that's in a format which is correct for the protocol clients are using to access the server (say, NFSv4). The server-side process of recognizing a junction and converting its contents is known as junction resolution.
This article describes how to configure a Linux NFS server to resolve junctions.
Prepare mountd to resolve junctions
- rpc.mountd updated with junction support (nfs-utils 1.2.6 or later, built with the nfs-plugin.h header present)
- libnfsjunct.so installed (fedfs-utils package install, or built from source)
Install the nfsref command
- nfsref program installed (fedfs-utils package install, or built from source)
