Hacker News Reader

Actual issue here: https://github.com/openzfs/zfs/issues/6531

It seems the whole thing took place in 2017 and was fixed then (first by not calling the reclaim if used ARC memory was zero, then the root cause also fixed by using a PRNG instead of the default CSPRNG in 0.7).

View on HN

Where do you see the actual issue was fixed in that ticket?

You’re right, the hack/workaround to not reclaim ARC if it’s below a size was written but not merged [0]. But the PRNG thing (actual CPU usage bug) is real and in 0.7+ so far as I can tell. Ideally both would have been committed.

[0]: https://github.com/openzfs/zfs/pull/6544

Might be a good idea to go to the PR and mention that. The stale bot has done its awful work… again.

Ahhh, sweet sweet reuse [1]. If code is poetry, most code is noetry, software reuse should be renamed to software refuse. Refuse it straight to the /bin

No code.

https://ocw.mit.edu/courses/aeronautics-and-astronautics/16-...

> stale bot closed this on 23 Nov 2020

as is tradition

Reply on news.ycombinator.com