| Salvaging | ||
|---|---|---|
 | Appendix C. The Demand-Attach File Server |  |
| Salvaging | ||
|---|---|---|
| | Appendix C. The Demand-Attach File Server | |
With a traditional fileserver, salvages usually occur in two situations:
The fileserver shuts down uncleanly, and when brought back up, all partitions are salvaged before the fileserver is available.
A volume experiences some corruption after it has been brought online, and an administrator manually schedules a salvage for an individual volume with bos salvage. Usually the way you notice this is that the fileserver noticed a volume has become corrupt and has taken it offline.
With DAFS, neither of these occur in normal operation. With DAFS, a volume will be salvaged automatically when a problem is detected in a volume. This occurs whether the fileserver detects the volume was not detached cleanly, or if the fileserver detects corrupt volume data.
In normal DAFS operation, you should not need to ever run bos salvage. However, if you suspect a bug, or that there is corruption in a volume that the fileserver has not detected, you can run bos salvage to manually issue a salvage.
All salvages scheduled from the salvageserver will be logged in /usr/afs/logs/SalsrvLog, in the same format as salvages for traditional fileservers are logged. If you issue a whole-partition or whole-server salvage, the logs for that will still be located in /usr/afs/logs/SalvageLog.
| |  | |
| DAFS Binaries |  | Converting a Fileserver to DAFS |