| 1 |
Supported forms for mount paths are: |
| 2 |
|
| 3 |
Normal single-host (these are unchanged) |
| 4 |
<path> host:/path/path |
| 5 |
|
| 6 |
Single host entries are not probed for a server response. |
| 7 |
|
| 8 |
Multiple replicated hosts, same path: |
| 9 |
<path> host1,host2,hostn:/path/path |
| 10 |
|
| 11 |
Multiple hosts, some with same path, some with another |
| 12 |
<path> host1,host2:/blah host3:/some/other/path |
| 13 |
|
| 14 |
Multiple replicated hosts, different (potentially) paths: |
| 15 |
<path> host1:/path/pathA host2:/path/pathB |
| 16 |
|
| •17 |
Multiple weighted, replicated hosts same path: |
| 18 |
<path> host1(5),host2(6),host3(1):/path/path |
| 19 |
|
| 20 |
Multiple weighted, replicated hosts different (potentially) |
| 21 |
paths: |
| 22 |
<path> host1(3):/path/pathA host2(5):/path/pathB |
| 23 |
|
| 24 |
For these formats a priority ordered list of hosts is created by using |
| 25 |
the following selection rules. |
| 26 |
|
| 27 |
1) Highest priority in selection is proximity. |
| 28 |
Proximity, in order of precedence is: |
| 29 |
- PROXIMITY_LOCAL, host corresponds to a local interface. |
| 30 |
- PROXIMITY_SUBNET, host is located in a subnet reachable |
| 31 |
through a local interface. |
| 32 |
- PROXIMITY_NETWORK, host is located in a network reachable |
| 33 |
through a local interface. |
| 34 |
- PROXIMITY_OTHER, host is on a network not directlty |
| 35 |
reachable through a local interface. |
| 36 |
|
| 37 |
2) NFS version and protocol is selected by calculating the largest |
| 38 |
number of hosts supporting an NFS version and protocol that |
| 39 |
have the closest proximity. These hosts are added to the list |
| 40 |
in response time order. Hosts may have a corresponding weight |
| 41 |
which essentially increases response time and so influences the |
| 42 |
host order. |
| 43 |
|
| 44 |
3) Hosts at further proximity that support the selected NFS version |
| 45 |
and protocol are also added to the list in response time order as |
| 46 |
in 2 above. |
| 47 |
|