Open battlmonstr opened 10 months ago
@AskAlexSharov could you explain how https://github.com/ledgerwatch/erigon/pull/10074 is related to this, and why the code there is commented out?
@battlmonstr because i decided to stay on MMAP https://github.com/ledgerwatch/erigon/pull/10074#issuecomment-2080359603
If it helps it might be possible to prevent this from panicking by passing a flag to mmap causing the space to be preallocated, rather than paging it in on demand. This would cause the error to occur when the torrent opens the storage, which is when the info bytes are obtained and added. So you you should see an error when you call Client.AddTorrent or something instead.
Can be:
Oh yeah, CoW FS might still panic on this. I don't think it's viable to catch a signal writing to a mmap in Go.
System information
Erigon version:
./erigon --version
devel
OS & Version: Linux
Commit hash: ab04de6d9f9fc4291dbfd113dadc79e798fd8daf
Erigon Command (with flags/config):
Chain/Network: mainnet
Expected behaviour
Produce an error in the log. It could be a fatal error, but it's better to degrade the functionality.
Actual behaviour
Crash.
Steps to reproduce the behaviour
Run with datadir having 700 Gb limit or less.
Backtrace
see full log attachment:
erigon.log.zip