From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1ViN0y-0005xZ-T7 for bitcoin-development@lists.sourceforge.net; Mon, 18 Nov 2013 11:29:12 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.160.52 as permitted sender) client-ip=209.85.160.52; envelope-from=wtogami@gmail.com; helo=mail-pb0-f52.google.com; Received: from mail-pb0-f52.google.com ([209.85.160.52]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1ViN0w-0000Lj-3p for bitcoin-development@lists.sourceforge.net; Mon, 18 Nov 2013 11:29:12 +0000 Received: by mail-pb0-f52.google.com with SMTP id uo5so147753pbc.39 for ; Mon, 18 Nov 2013 03:29:04 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.66.216.129 with SMTP id oq1mr21055665pac.75.1384774144158; Mon, 18 Nov 2013 03:29:04 -0800 (PST) Received: by 10.66.158.129 with HTTP; Mon, 18 Nov 2013 03:29:04 -0800 (PST) Date: Mon, 18 Nov 2013 01:29:04 -1000 Message-ID: From: "Warren Togami Jr." To: Bitcoin Dev Content-Type: multipart/alternative; boundary=047d7b5d9549f501db04eb71da16 X-Spam-Score: -0.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 (wtogami[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: bitcointalk.org] 1.0 HTML_MESSAGE BODY: HTML included in message -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: 1ViN0w-0000Lj-3p Subject: [Bitcoin-development] Bounty: MacOS X Bitcoin Corruption Issue 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, 18 Nov 2013 11:29:13 -0000 --047d7b5d9549f501db04eb71da16 Content-Type: text/plain; charset=UTF-8 https://bitcointalk.org/index.php?topic=337294 Since 0.8.x many MacOS X users have been experiencing periodic leveldb data corruption issues. While not fatal, it is very time consuming to recover from this corruption and upsetting that it happens often for some users. There have been three commits in Bitcoin that attempted to fix this, one fsync fix in leveldb, one in util.h, and a leveldb version upgrade to 1.13. My guess is that one of these commits fixed other corruption, but there remains at least one mysterious corruption issue on Mac where leveldb is corrupted after a clean shutdown of Bitcoin-Qt. After 5+ months we still do not know why some users never see corruption while it happens often for others. Gavin has pledged 5 BTC, and Litecoin Dev pledges 200 LTC to start this bounty. This thread has public addresses for Mac users to donate to increase the incentive to fix this issue sooner. To help please contribute detailed bug reports or links to more relevant background information pertaining to this corruption issue. https://bitcointalk.org/index.php?topic=320695.0 For testing purposes, please use either Bitcoin git master or Bitcoin 0.8.5 OMG3, both of which contain all of the relevant leveldb fixes. Testing without those fixes will not be helpful at this point. Warren --047d7b5d9549f501db04eb71da16 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
https://bitcointalk.org/index.php?topic=3D337294
Since 0.8.x man= y MacOS X users have been experiencing periodic leveldb data corruption iss= ues. =C2=A0While not fatal, it is very time consuming to recover from this = corruption and upsetting that it happens often for some users. =C2=A0There = have been three commits in Bitcoin that attempted to fix this, one fsync fi= x in leveldb, one in util.h, and a leveldb version upgrade to 1.13. =C2=A0M= y guess is that one of these commits fixed other corruption, but there rema= ins at least one mysterious corruption issue on Mac where leveldb is corrup= ted after a clean shutdown of Bitcoin-Qt. =C2=A0After 5+ months we still do= not know why some users never see corruption while it happens often for ot= hers.

Gavin has pledged 5 BTC, and Litecoin Dev pledges 200 L= TC to start this bounty. =C2=A0This thread has public addresses for Mac use= rs to donate to increase the incentive to fix this issue sooner.
=
To help please contribute detailed bug reports or links to more = relevant background information pertaining to this corruption issue.
<= div>
For testing purposes, please use either Bitcoin git master or Bi= tcoin 0.8.5 OMG3, both of which contain all of the relevant leveldb fixes. = =C2=A0Testing without those fixes will not be helpful at this point.
<= div>
Warren
--047d7b5d9549f501db04eb71da16--