monotone-devel
[Top][All Lists]
Advanced

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

[Monotone-devel] Mysterious bug that turns out not so mysterious after a


From: Nuno Lucas
Subject: [Monotone-devel] Mysterious bug that turns out not so mysterious after all
Date: Wed, 8 Aug 2007 15:38:11 +0100

Hello,

I use a 1GB USB pen drive to do the synchronization of some files
between work and home.
Sometimes I had some mysterious errors that would not allow me to sync
and I thought it had to do with the reliability of the flash memory.

This is the last one:

======================================================

$ mtn sync file:/media/disk/work/repo.mtn "etpos.*" "oracle*"
mtn: connecting to file:/media/disk/work/repo.mtn
mtn: finding items to synchronize:
mtn: certificates | keys | revisions
mtn:          309 |    3 |       103
mtn:  bytes in | bytes out | revs in | revs out
mtn:     3.1 k |     7.8 M |     0/0 |      2/2terminate called after
throwing an instance of 'informative_failure'
  what():  error: sqlite error: SQL logic error or missing database
mtn: fatal signal: Aborted
this is almost certainly a bug in monotone.
please send this error message, the output of 'mtn --full-version',
and a description of what you were doing to address@hidden
do not send a core dump, but if you have one,
please preserve it in case we ask you for information from it.
mtn:     3.1 k |     7.8 M |     0/0 |      2/2
mtn: error: I/O failure while talking to peer
file:/media/disk/work/repo.mtn, disconnecting

$ mtn --full-version
monotone 0.35 (base revision: f92dd754bf5c1e6eddc9c462b8d68691cfeb7f8b)
Running on          : Linux 2.6.20-16-generic #2 SMP Thu Jun 7
20:19:32 UTC 2007 i686
C++ compiler        : GNU C++ version 4.1.1 20070105 (Red Hat 4.1.1-51)
C++ standard library: GNU libstdc++ version 20070105
Boost version       : 1_33_1
Changes since base revision:
format_version "1"

new_manifest [f95da638a0aa17f7c5979d17a059faf6a46e9670]

old_revision [f92dd754bf5c1e6eddc9c462b8d68691cfeb7f8b]

  Generated from data cached in the distribution;
  further changes may have been made.

======================================================

Well, I finally lost 5 minutes to try to understand why this would
happen and found out it was simply complaining the disk was full (it
had 6 MB free this time).

As usually I don't fill up the pen, as soon I moved the big files to
the destination PC it would start working again.

Seems like a basic thing to review in the UI?


Best regards, keep up the good work,
~Nuno Lucas




reply via email to

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