use new name for new format fsck db
The old db is cleaned up when a new incremental fsck is started. The incremental fsck won't pick up where the old one left off, but I consider this a minor enough thing that it can just be documented and won't be a problem.
This commit is contained in:
parent
dc9295017f
commit
1b5f4b67b5
4 changed files with 19 additions and 3 deletions
|
@ -23,6 +23,10 @@ upgrade automatic = do
|
|||
showAction "v7 to v8"
|
||||
|
||||
populateKeysDb
|
||||
-- The fsck databases are not transitioned here; any running
|
||||
-- incremental fsck can continue to write to the old database.
|
||||
-- The next time an incremental fsck is started, it will delete the
|
||||
-- old database, and just re-fsck the files.
|
||||
|
||||
removeOldDb gitAnnexKeysDbOld
|
||||
liftIO . nukeFile =<< fromRepo gitAnnexKeysDbIndexCacheOld
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue