Hey,
is it on purpose that the storage node is logging every GET/PUT activity? I just changed the level for my node to WARN and there’s much less disk activity on my NAS. (I appended the docker run command with --log.level warn)
The only exception:
Although log level is set to warning, some INFO messages are still incoming every 10 minutes from the updater 
2026-02-02T10:38:42Z INFO Version is up to date {“Process”: “storagenode-updater”, “Service”: “storagenode-updater”}
The logging level being set to info by default is a discussion in and of itself. I personally think it’s a good thing, because when users face issues, the issues (and what is not an issue!) is visible in the logs.
I manually change all my nodes to warn as well, but have been contemplating dedicating a ~1TB NVMe drive as my log location for all nodes.
Regarding the storagenode-updater, it’s two different processes and it has it’s own logging.
Running the StorJ binary (which is done either from the commandline directly, or neatly packaged into the docker image) runs two images; the storage node itself, and the storagenode-updater, which as the name suggets, looks for updates and does update process when it’s time.
You can control how often you want the updater to check, if you want to lessen the burden on your log devices, but I would personally not bother. Changing from info to warn is already worlds of difference. Try changing to debug, if you’re feeling adventurous
Because the flag
is passed only to the storagenode binary.
You may try to use an env variable STORJ_LOG_LEVEL=warn instead (with -e in a docker run command before the image name, or in the environment: section of your docker-compose.yaml file).