From: Guillaume Quintard <guillaume.quintard@gmail.com>
To: Olly Betts <olly@survex.com>
Cc: sup-talk@rubyforge.org
Subject: Re: [sup-talk] Crash, bad index, and ensuing misery
Date: Tue, 6 Oct 2009 15:10:44 +0200 [thread overview]
Message-ID: <1e5fdab70910060610n7486dc1bi27b07c4f5f51faa6@mail.gmail.com> (raw)
In-Reply-To: <loom.20091006T143016-56@post.gmane.org>
On Tue, Oct 6, 2009 at 2:40 PM, Olly Betts <olly@survex.com> wrote:
> NEVER EVER remove the flintlock file.
Ooops, didn't know, won't do it again.
> My guess is that removing the flintlock file is the cause of the corruption
> you're seeing. Can you reproduce it on a database where you haven't removed
> this file?
Unfortunately, no
> which you have is whether there's a file called "iamflint" or "iamchert" in
Flint then
--
Guillaume
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2009-10-06 13:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-03 20:04 Guillaume Quintard
2009-10-03 20:17 ` Rich Lane
2009-10-03 21:06 ` Guillaume Quintard
2009-10-03 21:39 ` Rich Lane
2009-10-03 21:54 ` Guillaume Quintard
2009-10-06 12:40 ` Olly Betts
2009-10-06 13:10 ` Guillaume Quintard [this message]
2009-10-03 22:25 ` Rich Lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1e5fdab70910060610n7486dc1bi27b07c4f5f51faa6@mail.gmail.com \
--to=guillaume.quintard@gmail.com \
--cc=olly@survex.com \
--cc=sup-talk@rubyforge.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox