I think there have been fixes with handling of debug.log writes recently.
IMO the debug log should even be disabled by default.
Topic: excessive harddrive read acces on mac osx (Read 1317 times)
Yeah it stoped now when I passed 20k blocks.
But it looks so suspicious for someone new to Bitcoin, thinking it's indexing the whole harddrive or something.
Perhaps for future versions someone should try to minimize this effect, maxing the harddrive for an hour isn't fun
But it looks so suspicious for someone new to Bitcoin, thinking it's indexing the whole harddrive or something.
Perhaps for future versions someone should try to minimize this effect, maxing the harddrive for an hour isn't fun
You're probably downloading the chain.
Also downloading the newest client will probably fix your problem.
If it still doesn't, symlink the debug.log to /dev/null
Also downloading the newest client will probably fix your problem.
If it still doesn't, symlink the debug.log to /dev/null
Why is the harddrive working at 6MB/s as soon as I start up bitcoin 0.3.13 on my mac?
It starts when the first connection has been made.
This makes other things stutter, and I'm not even trying to generate coins
It starts when the first connection has been made.
This makes other things stutter, and I'm not even trying to generate coins
Jump to: