Traceback when attempting to delete a corrupted .checkpoint archive

[TheVillux]

After upgrading to 1.0.9, I noticed the daily backup on one of the machines failed. I'm not sure 1.0.9 is the culprit here however, it may have just let me know about the corrupted archive since it looks like it rebuilt the indexes.

When attempting the delete the corrupted archive, I receive the following traceback, even when using --force. Any ideas?

Error: Did not get expected metadata dict - archive corrupted!
Local Exception.
Traceback (most recent call last):
  File "borg/archiver.py", line 2052, in main
  File "borg/archiver.py", line 1997, in run
  File "borg/archiver.py", line 90, in wrapper
  File "borg/archiver.py", line 498, in do_delete
  File "borg/cache.py", line 97, in __init__
  File "borg/cache.py", line 391, in sync
  File "borg/cache.py", line 358, in create_master_idx
  File "borg/cache.py", line 315, in fetch_and_build_idx
  File "msgpack/_unpacker.pyx", line 469, in msgpack._unpacker.Unpacker.__next__ (msgpack/_unpacker.cpp:5459)
  File "msgpack/_unpacker.pyx", line 400, in msgpack._unpacker.Unpacker._unpack (msgpack/_unpacker.cpp:4483)
TypeError: unhashable type: 'dict'

Platform: Linux machinename 2.6.32-642.11.1.el6.i686 #1 SMP Fri Nov 18 18:48:28 UTC 2016 i686 i686
Linux: CentOS 6.8 Final
Borg: 1.0.9  Python: CPython 3.5.2
PID: 15290  CWD: /usr/local/bin
sys.argv: ['/usr/local/bin/borg', 'delete', 'user@machine:/location::machine_2016-07-18-23:45:02.checkpoint']
SSH_ORIGINAL_COMMAND: None

---

💰 there is a bounty for this

[enkore]

Yes, looks like an outdated cache together with a corrupted archive can make --force useless, because the cache sync tries to access the archives, among them the corrupted one, before --force does it's magic.

[TheVillux]

Any idea how to manually clean this up, besides wiping the repo and starting over?

[enkore]

This script should do the trick.

[TheVillux]

Nice, thanks. I'm using the binary client, so I'll guess I'll need to pip install Borg on the impacted machine for this will work, but this is much appreciated.

[ThomasWaldmann]

Keep in 1.0, due to "being able to fix a corrupted repo".