diff options
| author |  Joey Hess <joey@kitenet.net> | 2014-05-16 14:53:45 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2014-05-16 14:53:45 -0400 |
| commit | b657726efd26a64e8914503562ece5e3b0d51774 (patch) | |
| tree | c3b01962b5dd2bbaca3176100e59f534dd678b7e | |
| parent | bdb14491612e212e2d614867d891bbbc0975e3f0 (diff) | |
update
| -rw-r--r-- | doc/tips/what_to_do_when_a_repository_is_corrupted.mdwn | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/tips/what_to_do_when_a_repository_is_corrupted.mdwn b/doc/tips/what_to_do_when_a_repository_is_corrupted.mdwn index 80cb046d9..78f4977a2 100644 --- a/doc/tips/what_to_do_when_a_repository_is_corrupted.mdwn +++ b/doc/tips/what_to_do_when_a_repository_is_corrupted.mdwn @@ -19,4 +19,9 @@ on the drive. * Check for any problems with the annexed data: `cd $good; git annex fsck` * Now you can remove the corrupted repository, the new one is ready to use. +Alternatively, recent versions of git-annex have a `git annex repair` +command that uses <http://git-repair.branchable.com/> to repair a +repository in-place. The git-annex assistant will detect most corruptions +and offer to run the repair for you automatically. + --[[Joey]] |