Disk usage discrepancy?

[Alexey]

@digitalfrank

raid 0

1 disk failure and data is gone. But I think you know this.
As expected it’s not a Hyper-V VM, where they have a relatively good integration.
You may try this method to improve speed of the disk subsystem:

NTFS Disable 8dot3name

Fresh off an ReFS volume that went RAW, I’ve decided to be equally reckless and disable the 8 dot 3 short names for my replacement NTFS volume. I was shocked to not find a single mention of it in this forum, so I’ll report back once this bad decision ends up in another catastrophic fail, but the numbers looks promising for the Storj trillion tiny file configurations. [8484.image_thumb_0763777C] Disable across system: fsutil behavior set disable8dot3 Strip existing: fsutil 8dot3name strip /f…

The final goal - is to have all filewalkers successfully finish their work:

Storagenode.exe stopping for too long, for 10h+

Windows/PowerShell Logs should be at least info level Used space filewalker Regulated by the parameter in the config.yaml file or as a command line argument (add -- before the parameter, remove :, place it after the image name in your docker run command): # if set to true, all pieces disk usage is recalculated on startup (default true) storage2.piece-scan-on-startup: true to watch for a progress: cat "C:\Program Files\Storj\Storage Node\*.log" -Wait | sls "used-space-filewalker" | sls "sta…