Skip to content

Conversation

@laanwj
Copy link
Member

@laanwj laanwj commented Jan 26, 2015

A lot of times, disk corruption problems appear here.
To facilitate debugging and troubleshooting, add position information to the error messages.

I've tested all the error messages by injecting errors.

@laanwj laanwj added the Docs label Jan 26, 2015
@pstratem
Copy link
Contributor

I'm trying to trigger this code path on the system I have that produces this error during normal operation without fault injection.

@jonasschnelli
Copy link
Contributor

utACK

A lot of times, disk corruption problems appear here.
To facilitate debugging and troubleshooting, add position information
to the error messages.
@laanwj laanwj force-pushed the 2015_01_block_corrupt_debug branch from 69cda08 to f5791c6 Compare February 5, 2015 13:35
@fanquake
Copy link
Member

utACK

@harding
Copy link
Contributor

harding commented Feb 16, 2015

I ran this for several days without problem on a machine that once had bitcoind die on ReadBlockFromDisk. (Alas, I couldn't reproduce the previous error even with a full reindex.)

I did not inject errors to test the code paths.

@sipa sipa merged commit f5791c6 into bitcoin:master Feb 16, 2015
sipa added a commit that referenced this pull request Feb 16, 2015
f5791c6 Add more information to errors in ReadBlockFromDisk (Wladimir J. van der Laan)
@pstratem
Copy link
Contributor

Oops forgot to mention.

I tested this on a system which had repeatable ReadBlockFromDisk issues and this worked correctly.

@bitcoin bitcoin locked as resolved and limited conversation to collaborators Sep 8, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants