Catch LevelDB I/O errors #2201

issue sipa opened this issue on January 22, 2013
  1. sipa commented at 11:28 PM on January 22, 2013: member

    Right now, write errors in LevelDB (e.g. out of disk space) will cause block connection to fail, potentially resulting in that block being marked invalid, and never considered again for connecting.

    One possibility is throwing an (uncaught, until top-level) exception when there's a read or write error, causing an exit.

  2. gavinandresen commented at 8:30 PM on January 30, 2013: contributor

    Fixed by pull #2224

  3. gavinandresen closed this on Jan 30, 2013

  4. MarcoFalke locked this on Sep 8, 2021
Contributors

Milestone
0.8.0


github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2026-04-19 09:16 UTC

This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me