diff options
Diffstat (limited to 'doc/bugs/git_annex_migrate_leaves_old_backend_versions_around.mdwn')
| -rw-r--r-- | doc/bugs/git_annex_migrate_leaves_old_backend_versions_around.mdwn | 18 |
1 files changed, 17 insertions, 1 deletions
diff --git a/doc/bugs/git_annex_migrate_leaves_old_backend_versions_around.mdwn b/doc/bugs/git_annex_migrate_leaves_old_backend_versions_around.mdwn index 2fed00be7..c32b763a2 100644 --- a/doc/bugs/git_annex_migrate_leaves_old_backend_versions_around.mdwn +++ b/doc/bugs/git_annex_migrate_leaves_old_backend_versions_around.mdwn @@ -1 +1,17 @@ -`git annex migrate` leaves old, unlinked backend versions lying around. It would be great if these were purged automatically somehow. +`git annex migrate` leaves old, unlinked backend versions lying around. It +would be great if these were purged automatically somehow. + +> Yes, this is an issue mentioned in the [[walkthrough#index14h2]]. +> +> Since multiple files can point to the same content, it could be that +> only one file has been migrated, and the content is still used. So +> the content either has to be retained, or an operation as expensive +> as `git annex unused` used to find it something else still uses it. +> +> Rather than adding such an +> expensive operation to each call to migrate, I focused on hard-linking +> the values for the old and new keys, so that the old keys don't actually +> use any additional resources (beyond an extra inode). +> +> This way a lot of migrations can be done, and only when you're done you +> can do the more expensive cleanup pass if you want to. --[[Joey]] |