HI Node running for about 7 weeks now. Previously I posted about the amount of uncollected garbage I have had for weeks now - it was 40% of my storage for ages - while it has improved slightly, when we had a long awaited bloom filter I think from SLC, but for the last 10 days its not really come d…

The issue I originally raised, and discussed at length here since end of May, has now been solved and discussed in this thread - in my case 5.62TB of uncollected garbage moved to trash, freeing 68% of my storage for paid data opnce more. [image] When will "Uncollected Garbage" be d…

[image] Julio: but shouldn’t it spew the current defaults - if they’re not too lazy to update? If you specified some value in the config.yaml, why the node should reset it? This would mean that you cannot provide anything in your config file ever? It has no idea, what’s options were default. …

[image] Alexey: It has no idea, what’s options were default. With a different yaml structure in the config.yaml, this should be possible I believe.

Only if the parameter got renamed.

[image] Alexey: unlimited, but you may check yours What size do you mean? Max Segment size is still 64 MB, max piece size should depend on RS settings which were changed several times recently.

Yes. But. It’s not hard coded. Right now the maximum possible segment size is 64MiB, with the setting 80/29 it’s probable the 64MiB/80 or 64MiB/29. But I wouldn’t confirm that’s the maximum possible size for the piece… Especially, if we want to change RS settings almost dynamically [im…

[image] Alexey: Yes. But. It’s not hard coded. Right now the maximum possible segment size is 64MiB, with the setting 80/29 it’s probable the 64MiB/80 or 64MiB/29. But I wouldn’t confirm that’s the maximum possible size for the piece… I do recall pieces of ~8 MB being uploaded briefly as part…

[image] Alexey: If you specified some value in the config.yaml, why the node should reset it? That’s correct, yes of course the binaries defaults should not superceed the configuration file’s user variables. What I meant was when querying the binary with a ‘–help’ command, normally all defaul…

ok … so, in essence ‘Now testing RS number 16/20/30/60 with bestofn n=1.9’ == 64MiB segment / 16 pieces = 4 MiB blobs, ergo max mem needed. And in the case of 8 meg blobs, if those were max 64MiB segments, that’d be only 8 pieces. Obviously 16 is a better divisor to match cluster sizes, wonder why t…

One thing is that a piece file will also have a 512-byte header on top of actual data, which will already break your nice round numbers. Second is that a significant majority of segments are not exactly 64 MiB big. Third is that the parity algorithm used by Storj will also have some small overhead. …

[image] Toyoo: One thing is that a piece file will also have a 512-byte header on top of actual data I wasn’t aware of that. What information is stored in this header?

Storj Community Forum (official)

Two weeks working for free in the waste storage business :-(

Node Operators troubleshooting