I have been running a node for about 6 months now and my chain data recently maxed out my ssd completely and I started seeing disk I/O errors in the node's log output.
I made a mistake snapshotting, etc...and am rebuilding the node from scratch — it's currently bootstrapping.
With the new code and new node, after the bootstrapping with the chain data take under 16GB, or will it still take 150GB-ish, I'll I need to snapshot and upgrade it again?
Update
I should add I'm using Docker and the mainnet.sh
script. I created a fresh node docker container (I deleted the VPS, recreated it) with the latest image and let it bootstrap. After bootstrapping I saw, I double-checked which mode I was running in:
$ ./mainnet.sh client rpc get /chains/main/checkpoint
{ "block":
{ "level": 442369, "proto": 3,
"predecessor": "BLVxE1WGhVhtyFfYLDdKhe42N25nTGYWjKvfA2AokHDM6vJMjSQ",
"timestamp": "2019-05-18T06:39:35Z", "validation_pass": 4,
"operations_hash":
"LLoazsHZS8KSdCNFe9B6u5y78nYCynni8tqGEACKPywmrkisE1FEz",
"fitness": [ "00", "0000000000d35c7d" ],
"context": "CoVCLRtu1TeX8s5BBrQ3db56epGZCx7DH6vHS6Tw7QBFzbkV3HEM",
"protocol_data":
"00000000000373f6f25a004b67f5443ea32df421c4dbb31b3d14bbb2b297587261e2214c69adc43157040d9578272326ea60d97eb5f01706866923f7c2b88ffe2b4dbe7e7e5901ae450300" },
"save_point": 442369, "caboose": 0, "history_mode": "full" }
I checked the disk space after bootstrapping completed:
5.0G store
113.9G context
Then per the docs here, I upgraded with:
./mainnet.sh upgrade
Now checking the disk space a day or two later or I see:
5.8G store
140.7G context
What is wrong here?
Is it also strange that rpc get /chains/main/checkpoint
outputs a proto
of 3 instead of 4?