From: "Warren Togami Jr." <wtogami@gmail•com>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] Bounty: MacOS X Bitcoin Corruption Issue
Date: Mon, 18 Nov 2013 01:29:04 -1000 [thread overview]
Message-ID: <CAEz79PrGSO+LHb4PoU3VYF4SNajhEqXTXODqc1A_QV3ywdH7KQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1309 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 1589 bytes --]
reply other threads:[~2013-11-18 11:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAEz79PrGSO+LHb4PoU3VYF4SNajhEqXTXODqc1A_QV3ywdH7KQ@mail.gmail.com \
--to=wtogami@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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