Erigon v0.0.8 Release for Mainnet [Action Required]

A new version of Erigon (on Polygon Fork) is available - v0.0.8

If you are running erigon nodes on Mainnet, you need to upgrade to this version before the Indore hardfork kicks in on 11th July 2023 (Polygon Block Countdown).

Same block on erigon repo is included in v2.48.0 or above, If you are running nodes on erigon repo then upgrade to that before the above timeline.

Instructions to Upgrade

These are the instructions to upgrade Erigon on your nodes:

  1. Upgrade Erigon to the latest version:

    cd ~/erigon
    git pull --tags
    git checkout v0.0.8
    make erigon
  2. Ensure that you are on the latest version:

    ./build/bin/erigon --version
    # It should return
    erigon version 0.0.8-bor-047e789a
  3. Restart erigon

    sudo service erigon restart


Our chaindata size (db size) will soon grow more than 8 TB for Polygon mainnet archive (currently at 6.4T). We know that the db size limit is set to 8 TB and we can only increase that if we increase the db.pagesize config to >= 8KB (currently at 4KB). We wanted to ask the following:

  1. Will we have to sync from scratch if we want to change the pagesize config? (if yes when is the new snapshot for erigon mainnet archive going to be dropped at
  2. The Polygon fork for Erigon with version v0.0.8 is deployed on Alpine 3.14.0 where the default pagesize is 4KB. Does the OS used in this image support pagesize increase to 8KB or more?

@Krishna looking forward to get a detailed response on above. Thank you in advance.


1 Like
  1. There is an integration tool using which you can change the pagesize for existing data without syncing from scratch, More details about it you can find on erigon discord server.
    Regarding snapshot, I can’t comment as it’s not under my supervision, Maybe you can ask support team on our discord for more details on that.

  2. Yes

1 Like

so reading this… if I’m using 2.48.1 or 0.0.8 as an archive node, I’m covered for the indore fork?

1 Like

What does one need to modify in the configuration files or in the commands used to execute Erigon so that it works cohesively with Heimdall?

I didn’t understood your question, Erigon already works fine with Heimdall.

I’m having issues setting up my erigon node, have heimdall working successfully, downloading erigon snapshots (edited)

this is what my logfile says

[#47a3e3 25GiB/25GiB(100%) CN:0] [Checksum:#47a3e3 22GiB/25GiB(90%)]
[#47a3e3 25GiB/25GiB(100%) CN:0] [Checksum:#47a3e3 22GiB/25GiB(91%)]
[#47a3e3 25GiB/25GiB(100%) CN:0] [Checksum:#47a3e3 23GiB/25GiB(93%)]
[#47a3e3 25GiB/25GiB(100%) CN:0] [Checksum:#47a3e3 23GiB/25GiB(94%)]
[#47a3e3 25GiB/25GiB(100%) CN:0] [Checksum:#47a3e3 23GiB/25GiB(95%)]
[#47a3e3 25GiB/25GiB(100%) CN:0] [Checksum:#47a3e3 24GiB/25GiB(96%)]
[#47a3e3 25GiB/25GiB(100%) CN:0] [Checksum:#47a3e3 24GiB/25GiB(97%)]
[#47a3e3 25GiB/25GiB(100%) CN:0] [Checksum:#47a3e3 24GiB/25GiB(98%)]
[#47a3e3 25GiB/25GiB(100%) CN:0] [Checksum:#47a3e3 24GiB/25GiB(99%)]

10/07 09:31:46 [NOTICE] Verification finished successfully. file=/root/erigon-mainnet-snapshots/data/erigon-mainnet-snapshot-bulk-2023-09-08-part-aa

10/07 09:31:46 [NOTICE] Download complete: /root/erigon-mainnet-snapshots/data/erigon-mainnet-snapshot-bulk-2023-09-08-part-aa

Download Results:
gid   |stat|avg speed  |path/URI
47a3e3|OK  |    20MiB/s|/root/erigon-mainnet-snapshots/data/erigon-mainnet-snapshot-bulk-2023-09-08-part-aa

Status Legend:
(OK):download completed.

10/07 09:31:46 [NOTICE] Serialized session to 'erigon-mainnet-failures.txt' successfully.
Command succeeded.
Join parts for bulk-2023-09-08 then extract
cat: write error: No space left on device
/*stdin*\ : Read error (39) : premature end 
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now
root@ip-172-31-16-89:~/erigon-mainnet-snapshots# df -H
Filesystem      Size  Used Avail Use% Mounted on
/dev/root       4.0T  1.7T  2.3T  44% /
devtmpfs        8.4G     0  8.4G   0% /dev
tmpfs           8.4G     0  8.4G   0% /dev/shm
tmpfs           1.7G  914k  1.7G   1% /run
tmpfs           5.3M     0  5.3M   0% /run/lock
tmpfs           8.4G     0  8.4G   0% /sys/fs/cgroup
/dev/loop0       26M   26M     0 100% /snap/amazon-ssm-agent/6312
/dev/loop1       97M   97M     0 100% /snap/lxd/24061
/dev/loop4       56M   56M     0 100% /snap/snapd/19122
/dev/loop3       59M   59M     0 100% /snap/core18/2745
/dev/loop2       67M   67M     0 100% /snap/core20/1891
/dev/xvda15     110M  6.4M  104M   6% /boot/efi
/dev/loop5       43M   43M     0 100% /snap/snapd/20092
/dev/loop6       59M   59M     0 100% /snap/core18/2790
/dev/loop7       67M   67M     0 100% /snap/core20/2015
tmpfs           1.7G     0  1.7G   0% /run/user/1000
/dev/loop8       27M   27M     0 100% /snap/amazon-ssm-agent/7628

But there is plenty of space on my disk

What is going on? How do I get past the cat: write error: No space left on device error?

I think the erigon snapshot is more than 2.3TB, Can you try attaching a separate 4 TB disk for snapshot downloading and use that.