diff options
author | Joey Hess <joeyh@joeyh.name> | 2017-01-30 12:54:32 -0400 |
---|---|---|
committer | Joey Hess <joeyh@joeyh.name> | 2017-01-30 13:18:50 -0400 |
commit | 0b1a6e9ba0180f77d12895d7576dfc06238f5c51 (patch) | |
tree | f854d6f277e068afca9a90ae73db0a30075cde3c /doc/git-annex-reinit.mdwn | |
parent | f81280a6e378b4350252ee68a897d4399dd9d2ac (diff) |
reusing repository uuid cannot result in data loss AFAIK
Avoiding such problems is one reason why git-annex does active
verification of other copies of a file when dropping.
You could argue that reusing the uuid of a trusted repository leads to
data loss, but that data loss doesn't really involve reusing the uuid,
but instead is caused by deleting a trusted repository. Using trusted
repositories without a great deal of care is a good way to blow off your
foot, of which deleting them is only the most obvious;
added some sections about that.
If reusing a repository uuid could result in data loss then I'd be on
board with making reinit run a fast fsck to update the location log, but
since it can't, I feel that is not worth forcing. Not a bad idea to run
fsck afterwards. Updated language about that.
This commit was sponsored by Jake Vosloo on Patreon.
Diffstat (limited to 'doc/git-annex-reinit.mdwn')
-rw-r--r-- | doc/git-annex-reinit.mdwn | 9 |
1 files changed, 5 insertions, 4 deletions
diff --git a/doc/git-annex-reinit.mdwn b/doc/git-annex-reinit.mdwn index 52bca57dc..790546f42 100644 --- a/doc/git-annex-reinit.mdwn +++ b/doc/git-annex-reinit.mdwn @@ -14,10 +14,11 @@ UUID -- for example, if a repository got deleted, and you're setting it back up. Use this with caution; it can be confusing to have two existing -repositories with the same UUID. It can lead to data loss and other -weird phenomenons. Make sure you run `git annex fsck` after changing -the UUID of a repository to make sure location tracking information is -recorded correctly. +repositories with the same UUID. + +Make sure you run `git annex fsck` after changing the UUID of a +repository to make sure location tracking information is recorded +correctly. Like `git annex init`, this attempts to enable any special remotes that are configured with autoenable=true. |