From: grarpamp <grarpamp@gmail•com>
To: bitcoin-development@lists•sourceforge.net
Subject: [Bitcoin-development] Wallet related bug?
Date: Fri, 22 Jun 2012 07:01:19 -0400 [thread overview]
Message-ID: <CAD2Ti2_JL0HoNwkJJhzJ2CehPA0Ai0X7+CgF_n9-+H=vCU1F9A@mail.gmail.com> (raw)
I think there may be an ideal order of ops bug around rescan,
wallet upgrades/import and last block markers.
I dropped an old wallet in a current blockchain.
First ran - in rescan mode.
It said old walletver.
Then rescanned whole chain.
AddToWallet some blockhash, blocks out of range, invalid/nonwallet txid's,
which were already in there as legit ones in the old logs.
Second run in plain mode.
New wallet ver logged.
Rescanned the last 20k blocks or so,
which might have been the marker last time the old wallet was used.
Third and later runs... duplicates the second.
Never did say 'upgrading wallet' as it sometimes does.
Running detach=1 always.
Why scan the last 20k every time? Shouldn't have to if
whole chain was scanned. And certainly no more than
once if not.
Also...
Dumping the run params (bitcoin.conf, cmdline) to the log would be good.
And not automatically truncate the log when big but just append or roll it.
next reply other threads:[~2012-06-22 11:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-22 11:01 grarpamp [this message]
2012-06-23 0:10 grarpamp
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='CAD2Ti2_JL0HoNwkJJhzJ2CehPA0Ai0X7+CgF_n9-+H=vCU1F9A@mail.gmail.com' \
--to=grarpamp@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