2011-02-27 16:45:48 +00:00
|
|
|
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 backends.
|
|
|
|
|
|
|
|
|
|
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
|
2011-05-29 02:20:22 +00:00
|
|
|
unused . (checking for unused data...)
|
2011-04-03 00:59:41 +00:00
|
|
|
Some annexed data is no longer used by any files in the repository.
|
2011-02-27 16:45:48 +00:00
|
|
|
NUMBER KEY
|
2011-03-16 02:19:44 +00:00
|
|
|
1 WORM-s3-m1289672605--file
|
|
|
|
|
2 WORM-s14-m1289672605--file
|
2011-02-27 16:45:48 +00:00
|
|
|
(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`
|
