monotone-devel
[Top][All Lists]
Advanced

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

Re: [Monotone-devel] SQL logic error, SQLite restore problems, etc.


From: Derek Scherger
Subject: Re: [Monotone-devel] SQL logic error, SQLite restore problems, etc.
Date: Tue, 04 Sep 2007 22:27:03 -0600
User-agent: Thunderbird 2.0.0.6 (X11/20070805)

Ralf S. Engelschall wrote:
> We are currently investigating on using Monotone for use in the OpenPKG
> environment. For this I imported the 26000 commits from the CVS
> repository of the packaging sources (56MB raw *,v files) of the OpenPKG
> CURRENT distribution via Tailor into a Monotone repository (130MB SQLite
> database). The 26000 commit transactions needed about 1.5 days to
> migrate via Tailor, but the result looks perfect. So far, very good.

Cool

> 1. copying repository via raw SQLite dump/restore fails

[snip - previous response sounds reasonable]

> 2. copying repository via Monotone "pull" fails

> Anyway, the SQLite issue I'll address at SQLite.org. But the Monotone
> "SQL logic error" issue and non-deterministical break on the "pull"
> operation is really nasty and should be figured out (perhaps it is a
> Monotone bug, a SQLite bug or even again a GCC bug).

IIRC we've had a few reports of this error lately but not much detail
(that I can recall). Some of them seem to be "disk full" or "no write
permission on file" conditions I think. Google brings up many pages for
"SQL logic error or missing database" from lots of different projects
for whatever that's worth.

For fun I tried pulling the net.venge.monotone branch from my full
monotone database (which contains 211 branches) and this worked ok.
However the resulting pulled database is *larger* than the database it
was pulled from which seems a bit odd.  There are about 3 times as many
bytes in full files in the pulled database than in the source database
according to db info. This is with mtn 0.35 which I now vaguely recall
having a problem along these lines.

Cheers,
Derek





reply via email to

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