Add docs for recovering an OpenAFS fileserver
This should be a smooth recovery process. Change-Id: I3c68b077e38a88160286d94e71676c0c4dbb6a51
This commit is contained in:
parent
2ffd934819
commit
87fccc8e9b
@ -311,6 +311,25 @@ Then remove the server with ::
|
|||||||
Finally run the ``bos create`` command above with any modified
|
Finally run the ``bos create`` command above with any modified
|
||||||
parameters to restart the server.
|
parameters to restart the server.
|
||||||
|
|
||||||
|
Recovering a Failed Fileserver
|
||||||
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||||
|
|
||||||
|
If a fileserver crashes, take the following steps to ensure it's
|
||||||
|
usable after recovery:
|
||||||
|
|
||||||
|
* Pause mirror updates and volume release cron jobs
|
||||||
|
|
||||||
|
* Reboot the server; fix any filesystem errors and check the salvager
|
||||||
|
logs
|
||||||
|
|
||||||
|
* Check for any stuck volume transactions; remedy as appropriate
|
||||||
|
|
||||||
|
* Perform a manual release of every volume from a terminal on a server
|
||||||
|
using "-localauth" in case OpenAFS decides it can't do an
|
||||||
|
incremental update.
|
||||||
|
|
||||||
|
* Re-enable cron jobs
|
||||||
|
|
||||||
Mirrors
|
Mirrors
|
||||||
~~~~~~~
|
~~~~~~~
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user