Error when deploying a node using snapshot，dbx_env_open: MDBX_CORRUPTED，Looks like there's enough space #10814
Comments
|
continue with error message recommendations:
|
,I found that I cannot start the system with snapshots, but I can start it normally without snapshots. Is there something wrong with the snapshots? |
|
|
|
|
what means |
|
Even though the memory and disk are sufficient, the startup error is: meta_checktxnid:11415 catch invalid root_page_txnid 11557706 for maindb.mod_txnid 24300513 (workaround for incoherent flaw of unified page/buffer cache) |
|
maybe hardware failure. please use tools like https://www.memtest86.com/ to test RAM and tools like https://www.smartmontools.org/ to test Disk |
./memtester 100G 10 pagesize is 4096 |
|
4kb pagesize can maximum address 8tb db. so, |
So I should change the memory pagesize to 8kb, instead of simply setting db.pagesize=8kb, right? @AskAlexSharov |
/data2/erigon/build/bin/integration mdbx_to_mdbx --datadir /data1/erigon_temp --chaindata /data2/poly-archive/erigon_data --chaindata.to /data1/poly/chaindata/ goroutine 1 [running]: There is a problem with the copy data, please help me |
|
if need more then 8Tb database - then can't use 4kb pagesize. use 8kb or more (re-create target db) |
|
also can format logs and shell output by using triple backticks: https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#quoting-code |
I have understood this problem. I have changed db.pagesize=8KB, but the following error occurred when executing snapshot data copy. Integration mdbx_to_mdbx has an error Running version: 2.60.0 data2/erigon/build/bin/integration mdbx_to_mdbx --datadir /data1/erigon_temp --chaindata /data2/poly-archive/erigon_data --chaindata.to /data1/poly/chaindata/ goroutine 1 [running]: There is a problem with the copy data, please help me |
|
this seems to be for copying data from new and old nodes, not for snapshot import. The snapshot only has one file mdbx.dat. Is this the reason for the execution failure? @AskAlexSharov
if erigon doesn't stop after 1 min. just stop it.
|
|
try take a look if both db's are fine. for example by: |
|
@AskAlexSharov [root@c01_docker_solfullnode_pap_hk bin]# ./mdbx_stat -ef /data2/poly-archive/erigon_data |
plz use triple backticks for output formatting: https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#quoting-code |
1、 du -h /data2/poly-archive/erigon_data 2、./build/bin/mdbx_stat -ef /data2/poly-archive/erigon_data 3、./build/bin/mdbx_chk -0 -d /data2/poly-archive/erigon_data 4、./build/bin/mdbx_chk -1 -d /data2/poly-archive/erigon_data 5、./build/bin/mdbx_chk -2 -d /data2/poly-archive/erigon_data |
if it will return same error, can try: if this command doesn't return anything new - then something wrong with your database. maybe you did backup it wrong way (without shutting down erigon). maybe your hardware is broken: can use tools like https://www.memtest86.com/ to test RAM and tools like https://www.smartmontools.org/ to test Disk don't forget to |
yes,[root@c01_docker_solfullnode_pap_hk erigon]# git branch
|
|
|
Hey, when you mean |
Yes, after the snapshot is unzipped, there is only one mdbx.dat file |
|
Hey, @mh0lt can you ping the Polygon guys on this specific issue? it is not an Erigon problem. leaving this issue open until we receive a response from the mantainers of those snapshots but this is not an Erigon issue |
log:
meta_checktxnid:11415 catch invalid root_page_txnid 11557706 for maindb.mod_txnid 24300513 (workaround for incoherent flaw of unified page/buffer cache)
meta_waittxnid:11454 bailout waiting for valid snapshot (workaround for incoherent flaw of unified page/buffer cache)
mdbx_setup_dxb:16208 error -30796, while updating meta.geo: from l3-n749199549-u939524096/s2048-g1024 (txn#24300516), to l3-n749199549-u1006632960/s2048-g1024 (txn#24300517)
[EROR] [06-19|03:40:14.411] Erigon startup err="mdbx_env_open: MDBX_CORRUPTED: Maybe free space is over on disk. Otherwise it's hardware failure. Before creating issue please use tools like https://www.memtest86.com/ to test RAM and tools like https://www.smartmontools.org/ to test Disk. To handle hardware risks: use ECC RAM, use RAID of disks, run multiple application instances (or do backups). If hardware checks passed - check FS settings - 'fsync' and 'flock' must be enabled. Otherwise - please create issue in Application repo. On default DURABLE mode, power outage can't cause this error. On other modes - power outage may break last transaction and mdbx_chk can recover db in this case, see '-t' and '-0|1|2' options., label: chaindata, trace: [kv_mdbx.go:357 node.go:367 node.go:370 backend.go:245 node.go:124 main.go:66 make_app.go:54 command.go:276 app.go:333 app.go:307 main.go:34 proc.go:267 asm_amd64.s:1650]"
mdbx_env_open: MDBX_CORRUPTED: Maybe free space is over on disk. Otherwise it's hardware failure. Before creating issue please use tools like https://www.memtest86.com/ to test RAM and tools like https://www.smartmontools.org/ to test Disk. To handle hardware risks: use ECC RAM, use RAID of disks, run multiple application instances (or do backups). If hardware checks passed - check FS settings - 'fsync' and 'flock' must be enabled. Otherwise - please create issue in Application repo. On default DURABLE mode, power outage can't cause this error. On other modes - power outage may break last transaction and mdbx_chk can recover db in this case, see '-t' and '-0|1|2' options., label: chaindata, trace: [kv_mdbx.go:357 node.go:367 node.go:370 backend.go:245 node.go:124 main.go:66 make_app.go:54 command.go:276 app.go:333 app.go:307 main.go:34 proc.go:267 asm_amd64.s:1650]
commond:
docker run -d --name ok-erigon -u root -p 7011:30303 -p 7012:8545 -p 7013:9090 -v /data4/poly:/root/erigon/data/ ok-erigon --chain=bor-mainnet --bor.heimdall=https://heimdall-api.polygon.technology/ --http.addr=0.0.0.0 --http.vhosts=* --http.corsdomain=* --http.api=eth,erigon,engine,debug,trace --db.size.limit=15TB --datadir=/root/erigon/data/ --torrent.download.rate=512mb
I am using this snapshot, unzip and replace the mdbx.dat in chaindata
The text was updated successfully, but these errors were encountered: