[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Monotone-devel] db check after upgrade fails
From: |
Jeronimo Pellegrini |
Subject: |
Re: [Monotone-devel] db check after upgrade fails |
Date: |
Sat, 22 Apr 2006 10:46:11 -0300 |
User-agent: |
Mutt/1.5.11+cvs20060403 |
On Sat, Apr 22, 2006 at 01:00:24AM -0700, Nathaniel Smith wrote:
> On Fri, Apr 21, 2006 at 07:16:15PM -0300, Jeronimo Pellegrini wrote:
> > 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
>
> Probably there's no problem here. The unreferenced files are a normal
> side-effect of rosterify -- the db still contains entries for the old
> .mt-attrs files, but 'rosterify' moves all the data in them into
> real-first class attrs and then leaves the actual old files out of the
> new manifests it generates.
I see. But this may confuse (and scare) users a bit, don't you think so?
> It might be interesting to run 'db check' on the old database with
> 0.25, for comparison.
Ooops... You're right! The original database has revisions with missing
branch certs. So the only problem was the unreferenced files.
> In any case, these "problems" are not really problems, just somewhat
> unusual things. It's entirely possible that everything listed is
> exactly how you want it to be, and nothing in your output means any
> data is corrupted, or that monotone will get confused when trying to
> use your database.
OK, thanks a lot!
J.