Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1VIxDZ-0007ko-Dz for bitcoin-development@lists.sourceforge.net; Mon, 09 Sep 2013 08:53:09 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.215.51 as permitted sender) client-ip=209.85.215.51; envelope-from=gmaxwell@gmail.com; helo=mail-la0-f51.google.com; Received: from mail-la0-f51.google.com ([209.85.215.51]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1VIxDY-0005mZ-Hq for bitcoin-development@lists.sourceforge.net; Mon, 09 Sep 2013 08:53:09 +0000 Received: by mail-la0-f51.google.com with SMTP id es20so4571078lab.24 for ; Mon, 09 Sep 2013 01:53:01 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.112.57.49 with SMTP id f17mr1644918lbq.26.1378716781455; Mon, 09 Sep 2013 01:53:01 -0700 (PDT) Received: by 10.112.89.72 with HTTP; Mon, 9 Sep 2013 01:53:01 -0700 (PDT) Date: Mon, 9 Sep 2013 01:53:01 -0700 Message-ID: From: Gregory Maxwell To: Bitcoin Development Content-Type: text/plain; charset=UTF-8 X-Spam-Score: -1.6 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (gmaxwell[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1VIxDY-0005mZ-Hq Subject: [Bitcoin-development] Some current turbulence on the Bitcoin network: DB corruption errors on start from Bitcoin-qt / Bitcoind X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Sep 2013 08:53:09 -0000 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.