monotone-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Monotone-devel] db check after upgrade fails


From: Jeronimo Pellegrini
Subject: [Monotone-devel] db check after upgrade fails
Date: Fri, 21 Apr 2006 19:16:15 -0300
User-agent: Mutt/1.5.11+cvs20060403

Hi.

I just upgraded from monotone 0.25-2 to 0.26, following the instructions
in the UPGRADE file.
I used to have the .deb monotone 0.25-2 file on a sid box, and installed the
.deb for 0.26.

First I did:

$ mtn db rosterify --db main.db
mtn: calculating necessary migration steps
mtn: migrating data
mtn: committing changes to database
$ mtn db rosterify -k my_new_key --db main.db
mtn: converting existing revision graph to new roster-style revisions
mtn: certs in | certs out | nodes | revs out
mtn:    2,744 |         0 |   737 |        0
mtn: scanning for bogus merge edges
mtn: rebuilding 737 nodes
mtn: certs in | certs out | nodes | revs out
mtn:    2,744 |     2,744 |   737 |      737

(The database got smaller, as mentioned in the release notes -- great
work!)

-rw-r--r-- 1 jeronimo jeronimo 39649280 2006-04-21 19:01 main.db
-rw-r--r-- 1 jeronimo jeronimo 53411840 2006-04-21 18:48 
main.db-BACKUP-BEFORE-UPGRADE

OK, so I did:

$ mtn db check --db main.db

And I got a long list of errors:

mtn: file 025956f13beceec4cca7393659b05de8e71e5bd0 unreferenced
mtn: file 094b2ed953a07ff3a82efbf82b502b8035340df4 unreferenced
...
mtn: revision 00f8c20566a8c25b340d03738b6b392da43fa1b8 missing branch cert
mtn: revision 01192e87a971615ce36c7812d0cc4b5de2a8d8b0 missing branch cert
...
mtn: revision 38a42fef05f9faab97f384c48b65ced421c9d6ef mismatched certs (1 
authors 2 dates 1 changelogs)
mtn: revision f24059f68e450fd6151551a3520e63e3b9072c89 missing branch cert
...
mtn: warning: 38 unreferenced files
mtn: warning: 209 missing certs
mtn: warning: 1 mismatched certs
mtn: check complete: 1,977 files; 737 rosters; 737 revisions; 3 keys;
2,744 certs
mtn: total problems detected: 248 (209 serious)
mtn: error: serious problems detected

However, I did a checkout of one branch, and it seemed to be OK.

Did something go wrong in the upgrade? Is there something else I can do
to diagnose the problem? Or is it just OK?

Thanks,
J.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]