bbba6c19bd
Backends are now only used to generate keys (and check them); they are not arbitrary key-value stores for data, because it turned out such a store is better modeled as a special remote. Updated docs to not imply backends do more than they do now. Sometimes I'm tempted to rename "backend" to "keytype" or something, which would really be more clear. But it would be an annoying transition for users, with annex.backends etc.
30 lines
1.2 KiB
Markdown
30 lines
1.2 KiB
Markdown
It's possible for data to accumulate in the annex that no files point to
|
|
anymore. One way it can happen is if you `git rm` a file without
|
|
first calling `git annex drop`. And, when you modify an annexed file, the old
|
|
content of the file remains in the annex. Another way is when migrating
|
|
between key-value [[backends|backend]].
|
|
|
|
This might be historical data you want to preserve, so git-annex defaults to
|
|
preserving it. So from time to time, you may want to check for such data and
|
|
eliminate it to save space.
|
|
|
|
# git annex unused
|
|
unused . (checking for unused data...)
|
|
Some annexed data is no longer used by any files in the repository.
|
|
NUMBER KEY
|
|
1 WORM-s3-m1289672605--file
|
|
2 WORM-s14-m1289672605--file
|
|
(To see where data was previously used, try: git log --stat -S'KEY')
|
|
(To remove unwanted data: git-annex dropunused NUMBER)
|
|
ok
|
|
|
|
After running `git annex unused`, you can follow the instructions to examine
|
|
the history of files that used the data, and if you decide you don't need that
|
|
data anymore, you can easily remove it:
|
|
|
|
# git annex dropunused 1
|
|
dropunused 1 ok
|
|
|
|
Hint: To drop a lot of unused data, use a command like this:
|
|
|
|
# git annex dropunused `seq 1 1000`
|