📅 Original date posted:2014-08-13
📝 Original message:On Wed, Aug 13, 2014 at 6:22 PM, 潘庆庆 <qingqing.pan at 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
Wladimir [ARCHIVE] /
npub1xq…ymc2p
2023-06-07 15:25:10
in reply to nevent1q…cg7y
Author Public Key
npub1xqshkqv2g7uea4xzqwvmgjcz7u8vfavw6aazs999v0azsv3w7u3qpymc2pPublished at
2023-06-07 15:25:10Event JSON
{
"id": "fe2417f6dd1395b09199aed48ad46d73f9d7672be986abece5f2d7f02e4c2558",
"pubkey": "30217b018a47b99ed4c20399b44b02f70ec4f58ed77a2814a563fa28322ef722",
"created_at": 1686151510,
"kind": 1,
"tags": [
[
"e",
"7159589b226360c2d4fa49f027cc1a4cde36992f32cbe7967f416364a5efdfde",
"",
"root"
],
[
"e",
"a4741a59093d0854f3dcfaf4e9756c69178113add831eac65e41de5148cd3872",
"",
"reply"
],
[
"p",
"f44efbe05456e6ae546d2167bd9bc6c11ffed52d86aaaf15806ff5caaf11f6db"
]
],
"content": "📅 Original date posted:2014-08-13\n📝 Original message:On Wed, Aug 13, 2014 at 6:22 PM, 潘庆庆 \u003cqingqing.pan at okcoin.com\u003e wrote:\n\u003e Hi everybody,\n\u003e\n\u003e I tried to reduce the IO of bitcoind, and I found '-flushwallet=false'. After trying it, my IO reduced greatly.\n\u003e But why 'flushwallet' is true by default? Is there any danger if closing the flush wallet thread?\n\u003e I lost all my coins in testnet after one crash with '-flushwallet=false', was this because of no flush wallet thread?\n\nWhen flushwallet is disabled, the wallet is not flushed (written to\ndisk in a self-contained state) periodically. This means that there's\na larger chance that the wallet database is in inconsistent state when\nthe process stops unexpectedly. This can happen either due to a crash,\nor an external cause such as the power turning off unexpectedly.\n\nWith the wallet in non-self-contained state, the next time that you\nstart bitcoind BerkeleyDB will have to process log files. There is a\nnon-zero chance that this will fail and manual recovery is needed.\n\nAs the wallet is usually critical, it is unwise to disable that option.\n\nWladimir",
"sig": "64f4ce4d73b25c471eda20f2da0dc5b94387f477883d1d7dd43e070f951ace2559487db21949f08fc39b5f4a02b8be2e5331f85d554373a9581d2bd742dd4a7f"
}