SHA1KnitCorrupt

Bug #674270 reported by Luca Pireddu
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bazaar
Triaged
Medium
Unassigned

Bug Description

I tried upgrading a shared repository in rich-root-pack format
$ bzr info
Shared repository with trees (format: rich-root-pack)
Location:
  shared repository: .

The upgrade fails.

 SHA1KnitCorrupt: Knit <bzrlib.knit._VFContentMapGenerator object at 0xb613f8c> corrupt: sha-1 of reconstructed text does not match expected sha-1. key ('<email address hidden>',) expected sha 57d965dfb10bbf76f8f955f430ba6eb251c1621a actual sha 87e3fcef65c712c69ab77c9b2ab9144ec9956e65

I've attached a complete crash log. I suppose there's a corrupt tree in the shared repository, but the error doesn't say anything, nor does it suggest how I may restore the repository (I figured out that moving the backup to .bzr should fix it).

I can retrieve all the history from the (restored) trees, so I don't think they're corrupt. If it helps, some of them are checkouts of svn repository. Some of the trees report "Repository tree (format: unnamed)", if "unnamed" means anything to you.

I'll be happy to provide more information if necessary.

Crash log attached.

Revision history for this message
Luca Pireddu (pireddu) wrote :
Revision history for this message
Vincent Ladeuil (vila) wrote :

Can you try to run 'bzr check -v' and then 'bzr reconcile' and report the results ?

Changed in bzr:
importance: Undecided → High
status: New → Incomplete
Revision history for this message
Luca Pireddu (pireddu) wrote :

On bzr check -v (crash file attached)

==========================================================================================
bzr: ERROR: bzrlib.errors.SHA1KnitCorrupt: Knit <bzrlib.knit._VFContentMapGenerator object at 0xbdbd5cc> corrupt: sha-1 of reconstrud text does not match expected sha-1. key ('<email address hidden>',) expected sha 57d965dfb10bbf76f8f955f4a6eb251c1621a actual sha 87e3fcef65c712c69ab77c9b2ab9144ec9956e65

*** Bazaar has encountered an internal error. This probably indicates a
    bug in Bazaar. You can help us fix it by filing a bug report at
        https://bugs.launchpad.net/bzr/+filebug
    attaching the crash file
        /home/pireddu/.cache/crash/bzr-20101119135545-10367.crash
    and including a description of the problem.

    The crash file is plain text and you can inspect or edit it to remove
    private information.
==========================================================================================
$ bzr reconcile
Reconciling repository file:///home/pireddu/Projects/old_migrepo_to_trash/
Reconciliation complete.
$ bzr check -v

Again, as before. By the way, the crash happens after

   Checking repository at 'file:///home/pireddu/Projects/old_migrepo_to_trash/'.

i.e. while it's checking the shared root, after it has checked all the individual branches.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Bazaar because there has been no activity for 60 days.]

Changed in bzr:
status: Incomplete → Expired
Jelmer Vernooij (jelmer)
Changed in bzr:
status: Expired → Triaged
Jelmer Vernooij (jelmer)
Changed in bzr:
importance: High → Medium
tags: added: knits
Jelmer Vernooij (jelmer)
tags: added: check-for-breezy
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.