Hello,
I have been fault-tracing something fishy that is going on when i run a node on my raspberry pi but I don't seem to get any further on my own.
The problem:After the blocks have been indexed/verified etc. the bitcoind process keeps downloading something constantly at around ~92Mbit+/s. I have verified this both using vnstat, bwm-ng locally and on the NAS itself on that side using similar tools so I am 100% that the node is requesting some data constantly from the datadir while the service is up and running.
My setup:Raspberry Pi 3 running 0.14.1 daemon mounts a NFS share from my NAS to store the data.
I've tested adapted launch options for the rpi such as -dbcache etc. but during the more detailed fault tracing I was just using:
$ bitcoind -datadir=/mnt/bitcoin -printtoconsole
I downloaded bitcoind to my desktop to try to recreate the problem but it works flawlessly there.
It had the exact same circumstances, same NFS share with the same data on it.
It verifies the blocks (a lot faster though since it's a relatively fast computer compared to the pi3) and then just sits there pulling almost no data from the NFS share at all (like it should). Verfied using vnstat, bwm-ng locally and on the NAS itself as before.
It doesn't seem to be an NFS issue, the mounts are mounted exactly the same on both machines during seperate testing.
Could the PI3 not be processing something fast enough that it needs to keep reading something from the datadir?
What could possibly be wrong here?
I really want to run this full node (without constantly draining my NASes bandwidth)
EDIT: The console/outputfile(s) mentions nothing suspicious from what I can tell