From: Wladimir <laanwj@gmail•com>
To: 潘庆庆 <qingqing.pan@okcoin•com>
Cc: bitcoin-development <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] What is the danger if bitcoind startted with -flushwallet=false ?
Date: Wed, 13 Aug 2014 22:29:28 +0200 [thread overview]
Message-ID: <CA+s+GJCho_X3DT06evc_caHe+bpNv8sg3gUP4-dDqh7STQb-hQ@mail.gmail.com> (raw)
In-Reply-To: <tencent_6F055A157BDF0BD41143F75A@qq.com>
On Wed, Aug 13, 2014 at 6:22 PM, 潘庆庆 <qingqing.pan@okcoin•com> wrote:
> Hi everybody,
>
> I tried to reduce the IO of bitcoind, and I found '-flushwallet=false'. After trying it, my IO reduced greatly.
> But why 'flushwallet' is true by default? Is there any danger if closing the flush wallet thread?
> I lost all my coins in testnet after one crash with '-flushwallet=false', was this because of no flush wallet thread?
When flushwallet is disabled, the wallet is not flushed (written to
disk in a self-contained state) periodically. This means that there's
a larger chance that the wallet database is in inconsistent state when
the process stops unexpectedly. This can happen either due to a crash,
or an external cause such as the power turning off unexpectedly.
With the wallet in non-self-contained state, the next time that you
start bitcoind BerkeleyDB will have to process log files. There is a
non-zero chance that this will fail and manual recovery is needed.
As the wallet is usually critical, it is unwise to disable that option.
Wladimir
next parent reply other threads:[~2014-08-13 20:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tencent_6F055A157BDF0BD41143F75A@qq.com>
2014-08-13 20:29 ` Wladimir [this message]
2014-08-13 16:27 KingK.Pan
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=CA+s+GJCho_X3DT06evc_caHe+bpNv8sg3gUP4-dDqh7STQb-hQ@mail.gmail.com \
--to=laanwj@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=qingqing.pan@okcoin$(echo .)com \
/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