OpenZFS Discovers Critical File Damage Error

Available Intermediate production of the project Openzfs 2.2.1 is now released. Openzfs 2.2.1 is a development that focuses on implementing the ZFS file system for Linux and FreeBSD. This release is notable for the addition of nucleus Linux 6.6 and the attempt to eliminate problems that have been causing data damage to blocks during copying.

The initial assumption was that the problem only affected the 2.2.x branch and was caused by an error in the blocking mechanism of Openzfs 2.2.0. The blocking mechanism allowed the creation of a file or part without duplicating data by using a link to existing data blocks in the second copy of the file. In OpenZFS 2.2.1, the block cloning mechanism for addressing the issue has been disabled by default. To restore support for this mode, tuning zfs_bclone_enabled has been added.

Later, developers confirmed the reproduction of the problem in configurations with OpenZFS 2.1.X. It was found that the problem was not limited to systems with old releases of the Coreutils package. The error was reproduced in FreeBSD and in Linux distributions with the latest release of Coreutils 9.4.

The file damage occurs under rare circumstances, such as when executing the command “Emerge -1 DEV -Lang/GO” which leads to the installation of tools with file damage in the /usr/Lib/GO/PKG/Tool/Linux_AMD64/Compile directory. It is believed that the error started to occur after the openzfs version that includes the parameter

/Reports, release notes, official announcements.