Remix.run Logo
koverstreet a day ago

I'm hoping to have erasure coding done sometime in the first half of next year (knock on wood).

While reconcile was getting done we got a detailed outline of where EC resilvering is going to plug into that, so it's not looking like a huge amount of work anymore - and there's been people testing EC and reporting the occasional bug, it's been looking pretty solid.

We did some performance testing not too long ago, and it looked like we were in better shape than I thought. I'm still more interested in tracking down performance bug than shaving cycles and going for raw IOPS.

And the userbase isn't complaining about performance at all, aside from the odd thing like accounting read being slow (just fixed a couple issues there) or lack of defrag.

After debugging and stabilization, it's going to be more about usability, fleshing out missing features, more integration work (there's some systemd integration that needs to happen in the mount path), telemetry/introspection improvements (I want all the data I can get for stabilization, and json reporting would be good for lots of things).

So, if you're asking if you can help, that's a decent list to start from :)

BlackLotus89 a day ago | parent | next [-]

Oh I'm already active on irc and still have to send you a few things, but sure always eager to oblige.

LeFantome a day ago | parent | prev [-]

Hoping systemd will remain optional

koverstreet a day ago | parent [-]

yes, it will. But we do want to communicate properly with systemd and let the user know what's going on if mount has to take awhile because of some sort of recovery (instead of timing out), and various other things.

related, plymouth integration to let users know when their machine is booting up if a drive or the filesystem is unhealthy