public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Gregory Maxwell <gmaxwell@gmail.com>
To: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: [Bitcoin-development] Some current turbulence on the Bitcoin network: DB corruption errors on start from Bitcoin-qt / Bitcoind
Date: Mon, 9 Sep 2013 01:53:01 -0700	[thread overview]
Message-ID: <CAAS2fgRrgrfmjSKMkDWcqnRNfS_S2pZaCECb7OiaGr3B+kMqww@mail.gmail.com> (raw)

Please return your seats and fasten your seat-belts.

All Bitcoin-qt / Bitcoind nodes will currently fail to come back up
after a restart, reporting

": *** coin database inconsistencies found"
and
"Do you want to rebuild the block database now?"

Reindexing _will not_ correct the problem.  In Bitcoin-qt you should
say no to this reindex prompt as it will not help for this problem and
will only waste your time.

To workaround:

Please specify the command-line or configuration file argument
-checklevel=2  to Bitcoind or Bitcoin-qt.

The issue appears to have been introduced by 0.8.0 and is only a local
issue, beyond the annoyance restarting nodes it appears to be harmless
and carries no forking risk but will take a software update to fix
completely.

This problem will persist until no more than 288 blocks after 256818,
unless another trigger transaction is added to the blockchain (which
may well happen).

More information will be forthcoming once a patch is available.



             reply	other threads:[~2013-09-09  8:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-09  8:53 Gregory Maxwell [this message]
2013-09-09  9:25 ` [Bitcoin-development] Some current turbulence on the Bitcoin network: DB corruption errors on start from Bitcoin-qt / Bitcoind Gregory Maxwell
2013-09-09 23:25   ` Gregory Maxwell

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=CAAS2fgRrgrfmjSKMkDWcqnRNfS_S2pZaCECb7OiaGr3B+kMqww@mail.gmail.com \
    --to=gmaxwell@gmail.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    /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