A traditional file-server uses the `bnode` type `fs` and has a definition similar to
bnode fs fs 1
- parm /usr/afs/bin/fileserver -p 123 -pctspare 20 -L -busyat 200 -rxpck 2000 -rxbind
- parm /usr/afs/bin/volserver -p 127 -log -rxbind
+ parm /usr/afs/bin/fileserver -p 123 -L -busyat 200 -rxpck 2000 -cb 4000000
+ parm /usr/afs/bin/volserver -p 127 -log
parm /usr/afs/bin/salvager -parallel all32
end
Since an additional component was required for the demand-attach file-server, a new `bnode` type ( `dafs`) is required. The definition should be similar to
bnode dafs dafs 1
- parm /usr/afs/bin/fileserver -p 123 -pctspare 20 -L -busyat 50 -rxpck 2000 -rxbind -cb 4000000 -vattachpar 128 -vlruthresh 1440 -vlrumax 8 -vhashsize 11
- parm /usr/afs/bin/volserver -p 64 -log -rxbind
+ parm /usr/afs/bin/dafileserver -p 123 -L -busyat 200 -rxpck 2000 -cb 4000000 -vattachpar 128 -vlruthresh 1440 -vlrumax 8 -vhashsize 11
+ parm /usr/afs/bin/davolserver -p 64 -log
parm /usr/afs/bin/salvageserver
- parm /usr/afs/bin/salvager -parallel all32
+ parm /usr/afs/bin/dasalvager -parallel all32
end
-The instance for a demand-attach file-server is therefore `dafs` instead of `fs`.
+The instance for a demand-attach file-server is therefore `dafs`
+instead of `fs`. For a complete list of configuration options see the
+[dafileserver man page](http://docs.openafs.org/Reference/8/dafileserver.html).
### <a name="File-server Start-up / Shutdown"></a><a name="File-server Start-up / Shutdown "></a> File-server Start-up / Shutdown Sequence
The vnode finite-state automata is available in the source tree under `doc/arch/dafs-vnode-fsa.dot`
-`/usr/afs/bin/fssync-debug` provides low-level inspection and control of the file-server volume package. <span style="color:red"> *Indiscriminate use of <code>**fsync-debug**</code> can lead to extremely bad things occurring. Use with care. </span>
+`/usr/afs/bin/fssync-debug` provides low-level inspection and control of the file-server volume package. **Indiscriminate use of <code>fsync-debug</code>** can lead to extremely bad things occurring. Use with care.
<a name="SalvageServer"></a>
- file-server automatically requests volumes be salvaged as required, i.e. they are marked as requiring salvaging when attached.
- manual initiation of salvaging may be required when access is through the `volserver` (may be addressed at some later date).
-- `bos salvage` requires the `-forceDAFS` flag to initiate salvaging wit DAFS. However, <span style="color:red">**salvaging should not be initiated using this method**.</span>
+- `bos salvage` requires the `-forceDAFS` flag to initiate salvaging with DAFS. However, **salvaging should not be initiated using this method**.
- infinite salvage, attach, salvage, ... loops are possible. There is therefore a hard-limit on the number of times a volume will be salvaged which is reset when the volume is removed or the file-server is restarted.
- volumes are salvaged in parallel and is controlled by the `-Parallel` argument to the `salvageserver`. Defaults to 4.
- the `salvageserver` and the `inode` file-server are incompatible:
- because volumes are inter-mingled on a partition (rather than being separated), a lock for the entire partition on which the volume is located is held throughout. Both the `fileserver` and `volserver` will block if they require this lock, e.g. to restore / dump a volume located on the partition.
- inodes for a particular volume can be located anywhere on a partition. Salvaging therefore results in **every** inode on a partition having to be read to determine whether it belongs to the volume. This is extremely I/O intensive and leads to horrendous salvaging performance.
-- `/usr/afs/bin/salvsync-debug` provides low-level inspection and control over the `salvageserver`. <span style="color:red"> **Indiscriminate use of `salvsync-debug` can lead to extremely bad things occurring. Use with care.** </span>
+- `/usr/afs/bin/salvsync-debug` provides low-level inspection and control over the `salvageserver`. **Indiscriminate use of `salvsync-debug` can lead to extremely bad things occurring. Use with care.**
- See [[=salvsync-debug=|DemandAttach#salvsync_debug]] for information on debugging problems with the salvageserver.
<a name="FSStateDat"></a>
</tr>
</table>
-Arguments controlling the [[VLRU:|WebHome#VolumeLeastRecentlyUsed]]
+Arguments controlling the VLRU
<table border="1" cellpadding="0" cellspacing="0">
<tr>
### <a name="==fssync-debug=="></a> <code>**fssync-debug**</code>
-<span style="color:red"> **Indiscriminate use of `fssync-debug` can have extremely dire consequences. Use with care** </span>
+**Indiscriminate use of `fssync-debug` can have extremely dire consequences. Use with care.**
`fssync-debug` provides low-level inspection and control over the volume package of the file-server. It can be used to display the file-server information associated with a volume, e.g.
### <a name="==salvsync-debug=="></a> <code>**salvsync-debug**</code>
-<span style="color:red"> **Indiscriminate use of `salvsync-debug` can have extremely dire consequences. Use with care** </span>
+**Indiscriminate use of `salvsync-debug` can have extremely dire consequences. Use with care**
`salvsync-debug` provides low-level inspection and control of the salvageserver process, including the scheduling order of volumes.
This is the method that should be used on demand-attach file-servers to initiate the manual salvage of volumes. It should be used with care.
-Under normal circumstances, the priority ( `prio`) of a salvage request is the number of times the volume has been requested by clients. <span style="color:red"> Modifying the priority (and hence the order volumes are salvaged) under heavy demand-salvaging usually leads to extremely bad things happening. </span> To modify the priority of a request, use
+Under normal circumstances, the priority ( `prio`) of a salvage request is the number of times the volume has been requested by clients. Modifying the priority (and hence the order volumes are salvaged) under heavy demand-salvaging usually leads to extremely bad things happening. To modify the priority of a request, use
salvsync-debug priority -vol 537119916 -part /vicepb -priority 999999
git://git.openafs.org / openafs-wiki.git / blobdiff