The OpenZFS development team have put out not one but two new releases of the open-source cross-platform filesystem for Linux and FreeBSD.
This was necessary because while, as we reported a week ago, it was OpenZFS 2.2.0 that brought the issue to light and made it visible, it didn’t actually cause the problem.
It merely exposed an underlying bug which had been around for years: OpenZFS 2.2.0’s new, faster copy function simply made the existing issue much more likely to happen.
For instance, the bug was also confirmed in Illumos, the open-source fork of OpenSolaris which has continued development since Oracle killed off the open source project in 2010.
Unfortunately, it looks like Red Hat backported this functionality from Coreutils 9.x to 8.x, and it’s been identified in CentOS Stream 9 as well as in the OpenELA source code.
There’s a newer overview of the issue on Github, but the investigation as to when the bug first appeared is still underway, as the comments there show (along with a link to our earlier story).
The original article contains 603 words, the summary contains 174 words. Saved 71%. I’m a bot and I’m open source!
This is the best summary I could come up with:
The OpenZFS development team have put out not one but two new releases of the open-source cross-platform filesystem for Linux and FreeBSD.
This was necessary because while, as we reported a week ago, it was OpenZFS 2.2.0 that brought the issue to light and made it visible, it didn’t actually cause the problem.
It merely exposed an underlying bug which had been around for years: OpenZFS 2.2.0’s new, faster copy function simply made the existing issue much more likely to happen.
For instance, the bug was also confirmed in Illumos, the open-source fork of OpenSolaris which has continued development since Oracle killed off the open source project in 2010.
Unfortunately, it looks like Red Hat backported this functionality from Coreutils 9.x to 8.x, and it’s been identified in CentOS Stream 9 as well as in the OpenELA source code.
There’s a newer overview of the issue on Github, but the investigation as to when the bug first appeared is still underway, as the comments there show (along with a link to our earlier story).
The original article contains 603 words, the summary contains 174 words. Saved 71%. I’m a bot and I’m open source!