from what copilot told me, it turns out that my node has egress of around 2.5-3x per tb stored compared to the overall average. and i have only 100mbps net link for the node and on a not-very-fast nas-oriented mechanical hdd not ssd! i was a bit of impressed so i tried to remind myself what i did …

[image] vv75: could someone point how much free space should be kept on the filesystem for these compaction operations 1GB x STORJ_HASHSTORE_COMPACTION_REWRITE_MULTIPLE. Default is 10.

[image] vv75: where can i look for that for my node? I am using debug endpoint.

[image] alpharabbit: I am using debug endpoint. where can i rtfm about it?

[image] What going on? is the forum bug or @vv75 change answer solution multiple times?

[image] kocoten1992: What going on? is the forum bug or @vv75 change answer solution multiple times? i marked several as solution but it deselected them and i selected again. happens when the solution button isnt directly below the answer but under “…” menu. i marked as solution, then looke…

and after a bit of thought… if the data logs would be treated as sparse files, then before the compaction operation, the unused data could be discarded WITHIN the file so even more free space can be gained on the filesystem. devs, waddya think?

[image] vv75: confusing bug of the forum engine! It’s not a bug. Only one comment can be a solution.

[image] arrogantrabbit: It’s not a bug. Only one comment can be a solution. heeeee. thanks for telling! and in the current state of things, SEVERAL people solved the question, each one in some aspect… scratched my head and gave you guys hearts instead. :slight_smile:

It was discussed here on the forum and internally. This idea have more cons than pros, I wouldn’t like to repeat this discussion again, but TL;DR: too many nuances between OSes’ implementation of “sparse” files and punch holes, too fragile we messing with append-only approach and punch holes and f…

[image] Alexey: we messing with append-only approach and punch holes and filling them i meant not to fill them, just to punch before copying filled data to the new datalog chunk. in hope just to spare a bit more hdd space for the operation. or maybe even punch them as soon as data is no mor…

The concern #1 still remain, also the occupied space will not change. And it requires special quirks for each FS+OS combination to use the actual size without a punched hole.

And a bit of my observations report as a sno and not as a user

Node Operators

Alexey June 10, 2026, 5:49am 73

I asked AI for a better explanation, it’s pretty accurate: Google Search