Bitcoin Forum
May 04, 2024, 08:39:53 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Crash and db corruption after a large number of small transfers  (Read 8397 times)
bdonlan (OP)
Full Member
***
Offline Offline

Activity: 221
Merit: 102


View Profile
July 14, 2010, 07:22:50 PM
 #1

After performing about 2400 transfers of BC0.01 each, my wallet.dat grew to 340MB, and bitcoind crashed, asking me to run DB recovery. After I used BDB tools to dump and reload the wallet, I was able to get it to restart (alebit using 500MB of RAM), but trying to transfer out the remaining balance failed with:

error: Error: The transaction was rejected.  This might happen if some of the coins in your wallet were already spent, such as if you used a copy of wallet.dat and coins were spent in the copy but not marked as spent here.

How do I recover my wallet now?
1714811993
Hero Member
*
Offline Offline

Posts: 1714811993

View Profile Personal Message (Offline)

Ignore
1714811993
Reply with quote  #2

1714811993
Report to moderator
1714811993
Hero Member
*
Offline Offline

Posts: 1714811993

View Profile Personal Message (Offline)

Ignore
1714811993
Reply with quote  #2

1714811993
Report to moderator
1714811993
Hero Member
*
Offline Offline

Posts: 1714811993

View Profile Personal Message (Offline)

Ignore
1714811993
Reply with quote  #2

1714811993
Report to moderator
Activity + Trust + Earned Merit == The Most Recognized Users on Bitcointalk
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1714811993
Hero Member
*
Offline Offline

Posts: 1714811993

View Profile Personal Message (Offline)

Ignore
1714811993
Reply with quote  #2

1714811993
Report to moderator
bdonlan (OP)
Full Member
***
Offline Offline

Activity: 221
Merit: 102


View Profile
July 14, 2010, 07:27:13 PM
 #2

My debug.log after repairing wallet.dat is here: http://fushizen.net/~bd/debug.log.gz
Unfortunately, this time I forgot to save debug.log for the crash itself, but I did encounter this same bug previously; here is the log for that time: http://fushizen.net/~bd/debug-crash.log.gz
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!