diff options
| author |  Joey Hess <joey@kitenet.net> | 2013-10-29 14:22:56 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2013-10-29 14:25:20 -0400 |
| commit | 16d6ab71124876f7cffb79778cf8de1b23b5c1ba (patch) | |
| tree | 088d256697b521d069c14f3e05c70540586de7ad /doc/design | |
| parent | e802db0b6b69198e4699d63d76b5d0fc78864714 (diff) | |
add post-repair actions
Diffstat (limited to 'doc/design')
| -rw-r--r-- | doc/design/assistant/disaster_recovery.mdwn | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/doc/design/assistant/disaster_recovery.mdwn b/doc/design/assistant/disaster_recovery.mdwn index 4f72d96c3..40e48650e 100644 --- a/doc/design/assistant/disaster_recovery.mdwn +++ b/doc/design/assistant/disaster_recovery.mdwn @@ -62,7 +62,10 @@ Add git fsck to scheduled self fsck **done** TODO: git fsck on ssh remotes? Probably not worth the complexity.. TODO: If committing to the repository fails, after resolving any dangling -lock files (see above), it should git fsck. +lock files (see above), it should git fsck. This is difficult, because +git commit will also fail if the commit turns out to be empty, or due to +other transient problems.. So commit failures are currently ignored by the +assistant. If git fsck finds problems, launch git repository repair. **done** |