Yep. Kind of…
Why not just use EXT4 and forget about this?
meh only thing i would use EXT4 is as a boot / OS drive, because ZFS drivers can be weird.
also is it really possible to avoid fragmentation… seems like a tricky thing.
never really liked defrag anyways, always seemed like it would only very temporarily fix the issue, then for it only to come back worse… so never really done that even on old school windows
Ext4 is not immune, see this thread: On Ext4, fragmentation and the filewalker
Anyone else’s estimated earnings for this month drop like a rock? This month’s estimated payout is 20% less than the past several months.
same here, very low earnings this month…
ingress is up these last few days, so that is something.
also it’s possible storj is slowly phasing out the test data they don’t need…
so we are starting to see more and more seasonal deviations, based upon when large corps do backups and such, i would think…
I don’t think that’s it. Income from saltlake has dropped by 2/3rds. I think they stopped egress from that test satellite. I only see a few MB per day now on that satellite. Unfortunately this will mostly hit long time node operators. New nodes likely barely see a difference. But yeah, it’s hitting me hard. As well as other long time node operators.
To be fair to Storj Labs… this kind of had to happen at some point. Nobody is paying them for that egress, so it was a pretty huge cost to them. And customer satellites are taking over, providing quite a bit more egress.
If there is likely to be less egress on Saltlake, do you think they are planning to move someones Disk utilisation from that satellite, so it can grow with true data… ?
if that makes sense ?
I can only speculate. But I think they may want to keep the data reserved on nodes for moments where there is increasing customer demand. But they’d have to consider the risk of node operators with full nodes exiting this satellite.
@john could you maybe address this change in saltlake egress and future plans with test data, like you did a while ago? This is quite a big change for long time node operators.
Previous posts by John about test data here (pretty outdated now):
This is the last 90 days of egress for the Saltlake sat. Clearly somethings happening with test data.
Yes, it shows on the earnings. I wasn’t aware about the extent of the testing data upload.
Saltlake egress seems to be back for now. Lets see if it sticks around.
They should consider droping old test data progressively to allow old storage node to get “real” data
John’s posts I linked earlier mention some reasons for that test data to still be there. SNO incentives is one. But it is also there to reserve space for possible rapid expansion in case of large customer onboarding. As long as the egress matches customer behavior roughly, it doesn’t matter whether we host test data or customer data, as we get paid the same for it. And until earlier this month it has matched customer egress for years. Since the egress is already back, I’m going to assume this was just temporary.
0 GB ingress since the 10th Aug on all my nodes running 1.58.2, the one that gets auto updated is on 1.61.1 and has had ingress for that whole time.
Is there no ingress for slightly outdated nodes?
EDIT: Updated all notes to 1.61.1 and now got ingress again
Correct. The node version must be within 2 updates of the latest to continue receiving ingress. Egress will still work.
Does that match up with what the nodes say?
Should also say there what the minimum version is to have ingress.
Or a message saying why there is no ingress
The second point isn’t yet implemented as far as I know. So although it could be phrased differently your node could still egress data when running version 1.24.x
Stopped again since Friday…