Unknown flag: --storage2.piece-scan-on-startup

[agente]

Something changed on this flag?

[nerdatwork]

Enabling the Lazyfilewalker

There were several discussions and open concerns related to filewalker processes (such as garbage collection and the used-space calculation services) competing for disk IOPS with same priority as more important services such customer downloads/uploads, audits and repairs. The community introduced workarounds to disable the initial used-space calculation on startup by adding the --storage2.piece-scan-on-startup flag. The lazyfilewalker runs the used-space calculation and garbage collection filew…

[Alexey]

Depends on how you trying to pass it.
The correct options are:

• after the image name (docker)
• in the storagenode run command (service)
• as an environment variable STORJ_STORAGE2_PIECE_SCAN_ON_STARTUP
• as an option storage2.piece-scan-on-startup: in the config.yaml file

So please provide your docker run command (you may mask the private info).

[agente]

Sorry. I will clarify my question. I’m using --storage2.piece-scan-on-startup=false in my docker run settings and I have an unknown flag error.

[Alexey]

Passing via RUN_PARAMS will lead to a various errors, because it’s now passed differently, see

storj/storagenode-docker/blob/21b0028b8e02a7fea2370c06360a0250c7ec603f/docker/entrypoint#LL51C1-L51C11

and storagenode-updater did not recognize most of storagenode options, include this one.

[agente]

Thanks. I was using it before image name (docker)