If you have such a big problem running bitcoin-qt, you should just use other wallets.
Just upload your wallet.dat on https://blockchain.info/wallet/import-wallet
You can continue to use blockchain.info, or you can send your bitcoin to a newly created Electrum or Multibit wallet.
Topic: Just my gripe with the bitcoin qt (Read 923 times)
As mentioned by Foxpup, that's utterly bizarre and not normal behavior. Write caching seems pretty far-fetched unless you have some type of alien hard drive from the future given we're talking 10GB+ of data for 12 weeks behind current.
I've actually seen a Windows machine use two-thirds of all available RAM for the disk cache, and it wasn't even working with huge files. I don't really understand why such a large cache is necessary for anything faster than a tape drive, but no doubt Microsoft knows what they're doing. 
You thought it would be a good idea to put the blockchain on a RAMdisk.
That was my first thought too, but my second thought was that nobody using a RAMdisk is surprised that the data vanishes when the computer crashes. Though I've been wrong before. 
Your hard drive is failing. I had this problem when I started with bitcoin too and my knee jerk reaction was to blame the software. Later I found out that my hard drive was probably the cause of it.
It takes that long because it has to scan the blockchain for previous transactions to that address.
If you guys want speed switch to a lite client like Electrum.
Heh, on a semi-related note, I used importprivkey yesterday. Took over ten minutes. I was stunned.
It takes that long because it has to scan the blockchain for previous transactions to that address.
If you guys want speed switch to a lite client like Electrum.
Heh, on a semi-related note, I used importprivkey yesterday. Took over ten minutes. I was stunned.
As mentioned by Foxpup, that's utterly bizarre and not normal behavior. Write caching seems pretty far-fetched unless you have some type of alien hard drive from the future given we're talking 10GB+ of data for 12 weeks behind current.
I'd guess the following equally-far-fetched ideas:
*You thought it would be a good idea to put the blockchain on a RAMdisk.
*There is some kind of backup software on your PC which automatically and fully restores your computer (including deleting new files) to a previous date whenever it crashes.
*You've managed to connect to people who giving you nothing but corrupt blocks. Maybe some type of other similar attack.
*You've downloaded a fake QT client. Its sole purpose is to annoy users.
*You have nano-gremlins physically erasing data on your hard drive disks. Are you friends with any Gypsies?
As mentioned by Foxpup, that's utterly bizarre and not normal behavior. Write caching seems pretty far-fetched unless you have some type of alien hard drive from the future given we're talking 10GB+ of data for 12 weeks behind current.
I'd guess the following equally-far-fetched ideas:
*You thought it would be a good idea to put the blockchain on a RAMdisk.
*There is some kind of backup software on your PC which automatically and fully restores your computer (including deleting new files) to a previous date whenever it crashes.
*You've managed to connect to people who giving you nothing but corrupt blocks. Maybe some type of other similar attack.
*You've downloaded a fake QT client. Its sole purpose is to annoy users.
*You have nano-gremlins physically erasing data on your hard drive disks. Are you friends with any Gypsies?
As far as I know, the problem you're describing is impossible if the database is actually being saved to your hard disk (even in a corrupt state). Does your hard disk use write caching? If so, it's possible that most or all database operations are only happening in the cache, and were never actually written to the disk before your computer crashed (the database files are constantly changing as long as Bitcoin is running, and the disk cache may be waiting for it to finish before committing those changes to disk, which never happens unless the program is shut down cleanly). That won't work at all. Disabling your disk cache will force all data to be constantly saved to disk, which is slower but will greatly reduce the risk of data loss if your computer crashes. (Why your computer keeps crashing is another question you should be asking.)
EDIT: Typo.
EDIT: Typo.
Try MultiBit.
Every time my system hangs, restarts, whatever, bitcoin qt fucks up the blocks database, has to re-index it. By starting over and re-downloading it.
From the fucking start. All the fucking blocks.
I don't have that issue. Also, if the database does get corrupt, you can run bitcoin-qt with -reindex to do a check of the database and only redownload the corrupt blocks. From the fucking start. All the fucking blocks.
As mentioned, this irks me.
Installed Bitcoin QT, trying to run the full client to help the network/community.
Been running it for 1 month and still not been able to download all blocks.
Every time my system hangs, restarts, whatever, bitcoin qt fucks up the blocks database, has to re-index it. By starting over and re-downloading it.
From the fucking start. All the fucking blocks.
Why the hell does it need to re-download ALL the blocks. I mean, if something went wrong, and bitcoin exited unexpectedly with an I/O error, why is it that all the blockchain database is fucked and not only the last block.
People, we are in 2014, transactional databases were invented eons ago! DBase would lick this kind of database.
Every time it gets close, 12 weeks behind, it seems that the time needed to finish the fucking last weeks get exponentially longer.
I got some penny payments from my pool, at my wallet address in Bitcoin QT, still not being able to view them after one month.
This is getting nowhere fast!
Sorry for the tone. I'm pissed. You could see that, right? You have a very keen perception.
Installed Bitcoin QT, trying to run the full client to help the network/community.
Been running it for 1 month and still not been able to download all blocks.
Every time my system hangs, restarts, whatever, bitcoin qt fucks up the blocks database, has to re-index it. By starting over and re-downloading it.
From the fucking start. All the fucking blocks.
Why the hell does it need to re-download ALL the blocks. I mean, if something went wrong, and bitcoin exited unexpectedly with an I/O error, why is it that all the blockchain database is fucked and not only the last block.
People, we are in 2014, transactional databases were invented eons ago! DBase would lick this kind of database.
Every time it gets close, 12 weeks behind, it seems that the time needed to finish the fucking last weeks get exponentially longer.
I got some penny payments from my pool, at my wallet address in Bitcoin QT, still not being able to view them after one month.
This is getting nowhere fast!
Sorry for the tone. I'm pissed. You could see that, right? You have a very keen perception.
Jump to: