Alexey
June 15, 2024, 4:50am
22
Hello @majklsee ,
Seems you didn’t remove their data
Following the announcement to decommission Europe-north-1 and US2 satellites, manually deleting the remaining data of these satellites from the node can be a tedious task as it requires finding the blobs folder name for each satellite, so we wanted to improve the storagenode CLI to semi-automate cleaning up a satellite data after it is marked as untrusted.
The storagenode CLI (versions from 1.88.0) provides a forget-satellite subcommand to remove satellites from the trust cache and clean up the…
majklsee:
error: context canceled
This is mean that your disk is too slow to keep-up and the lazy filewalker is failed.
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…
Oh, separately, make sure you have last access time disabled on the volume that holds storage node data – this will remove quite a lot of IO:
And if you haven’t done so yet – move databases to your system drive.
We should have started with this (but I assumed you have already done that, but I"m not sure, so double check
1 Like