1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <laanwj@gmail.com>) id 1XHfAt-0000o6-JQ
for bitcoin-development@lists.sourceforge.net;
Wed, 13 Aug 2014 20:29:35 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.213.173 as permitted sender)
client-ip=209.85.213.173; envelope-from=laanwj@gmail.com;
helo=mail-ig0-f173.google.com;
Received: from mail-ig0-f173.google.com ([209.85.213.173])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1XHfAr-0002oo-Ed
for bitcoin-development@lists.sourceforge.net;
Wed, 13 Aug 2014 20:29:35 +0000
Received: by mail-ig0-f173.google.com with SMTP id h18so11464911igc.0
for <bitcoin-development@lists.sourceforge.net>;
Wed, 13 Aug 2014 13:29:28 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.50.134.136 with SMTP id pk8mr52845453igb.20.1407961768130;
Wed, 13 Aug 2014 13:29:28 -0700 (PDT)
Received: by 10.64.27.228 with HTTP; Wed, 13 Aug 2014 13:29:28 -0700 (PDT)
In-Reply-To: <tencent_6F055A157BDF0BD41143F75A@qq.com>
References: <tencent_6F055A157BDF0BD41143F75A@qq.com>
Date: Wed, 13 Aug 2014 22:29:28 +0200
Message-ID: <CA+s+GJCho_X3DT06evc_caHe+bpNv8sg3gUP4-dDqh7STQb-hQ@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: =?UTF-8?B?5r2Y5bqG5bqG?= <qingqing.pan@okcoin.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
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
(laanwj[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: 1XHfAr-0002oo-Ed
Cc: bitcoin-development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] What is the danger if bitcoind startted
with -flushwallet=false ?
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Wed, 13 Aug 2014 20:29:35 -0000
On Wed, Aug 13, 2014 at 6:22 PM, =E6=BD=98=E5=BA=86=E5=BA=86 <qingqing.pan@=
okcoin.com> wrote:
> Hi everybody,
>
> I tried to reduce the IO of bitcoind, and I found '-flushwallet=3Dfal=
se'. After trying it, my IO reduced greatly.
> But why 'flushwallet' is true by default? Is there any danger if clos=
ing the flush wallet thread?
> I lost all my coins in testnet after one crash with '-flushwallet=3Df=
alse', 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
|
