> Did some of you have this same problem? Is there any workaround (i don´t care if it is dirty, i just want to move forward)?
You can try disabling script verification: --noverifyscripts
Based on what other people have reported it looks like there is a hard database size limit LevelDB runs into - so you could look into LevelDB config flags that let you bypass this issue.
> And the last question: how can I collect info enough to report this issue with more useful details?
Usually, you'd want to use the debug logging flags (--bchdbg, --netdbg, etc.), but in this case I think it's a LevelDB issue. We will probably have to optimize the database format to make it usable again.
We're currently storing all data in LevelDB. Quite possibly, this particular issue could be avoided by using LevelDB only for indexes and storing the actual blocks in plain files - which is what I should have done to begin with - don't judge. ^^
On Thursday, May 23, 2013 5:12:25 PM UTC+2, Lucas Ontivero wrote:
Hi all,
Did some of you have this same problem? Is there any workaround (i don´t care if it is dirty, i just want to move forward)?
And the last question: how can I collect info enough to report this issue with more useful details?
Thank you.