178debe435
When we map a file for generating the DAG, we do a simple truncate to e.g. 1Gb. This is fine, even if we have nowhere near 1Gb disk available, as the actual file doesn't take up the full 1Gb, merely a few bytes. When we start generating into it, however, it eventually crashes with a unexpected fault address . This change fixes it (on linux systems) by using the Fallocate syscall, which preallocates suffcient space on disk to avoid that situation. Co-authored-by: Felix Lange <fjl@twurst.com> |
||
---|---|---|
.. | ||
algorithm_test.go | ||
algorithm.go | ||
api.go | ||
consensus_test.go | ||
consensus.go | ||
difficulty.go | ||
ethash_test.go | ||
ethash.go | ||
mmap_help_linux.go | ||
mmap_help_other.go | ||
sealer_test.go | ||
sealer.go |