missing trie node, on archival sync

[Ajes1337]

When I follow the instructions to run a archival alethia node, and the sync finished, I get "missing trie node" errors:

When I call:
curl -s localhost:8547 -X POST -H "Content-Type: application/json" --data '{"jsonrpc":"2.0","method":"eth_getBalance","params":["0x1670000000000000000000000000000000000001","0xe827d"],"id":1003}'

I get this answer:
{"jsonrpc":"2.0","id":1003,"error":{"code":-32000,"message":"missing trie node 42590e599015cdbfa3199d90b40c8e8db8f15b89d8a4ce3e884a67154617bca9 (path ) state 0x42590e599015cdbfa3199d90b40c8e8db8f15b89d8a4ce3e884a67154617bca9 is not available, not found"}}

how much gb/tb should a archival-node be at?

I have sat in docker compose:
--gcmode archive

and also tried this in .env and re-synced:
GETH_ADDITIONAL_ARGS=--gcmode=archive

what am I missing? 🤷‍♂️

[maxysoft]

No issues there on mainnet with default config. The question is, why did you add --gcmode archive when it's already included?

simple-taiko-node/docker-compose.yml

Line 26 in d6a4248

--gcmode archive

{"jsonrpc":"2.0","id":1003,"result":"0x33b2d18ee297209daf53c3d"}

[Ajes1337]

you are correct, I did not add it to docker-compose.yml, it was already present when I cloned the repo.

how many gigabyte or terrabyte does archival mainnet take of diskspace?

I just made a clean sync, and I still cannot get the example curl call to work..

my "archival" node takes ~160gb of diskspace 🤷‍♂️

[maxysoft]

It depends. The initial sync will take less space that will grow much faster with time passing. In my case this is the usage after 110 days of uptime

Filesystem      Size  Used Avail Use% Mounted on
taikodata       3.6T  849G  2.7T  24% /mnt/taiko-chain-data

[Ajes1337]

hmm, for me, that does not make sense.. I need to run a real archival node, where all data is available from the first intital sync?