{"id":111714,"date":"2023-11-23T15:10:22","date_gmt":"2023-11-23T13:10:22","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/v-openzfs-vyyavlena-oshibka-kotoraya-mozhet-privesti-k-povrezhdeniyu-fajlov"},"modified":"2023-11-23T15:10:22","modified_gmt":"2023-11-23T13:10:22","slug":"v-openzfs-vyyavlena-oshibka-kotoraya-mozhet-privesti-k-povrezhdeniyu-fajlov","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/v-openzfs-vyyavlena-oshibka-kotoraya-mozhet-privesti-k-povrezhdeniyu-fajlov","title":{"rendered":"An error has been discovered in OpenZFS that could lead to file corruption.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
An intermediate release of the OpenZFS project 2.2.1 is available, which develops the implementation of the ZFS file system for Linux and FreeBSD. This release is notable for adding support for Linux kernel 6.6 and attempting to fix a problem that leads to data corruption (zeroing out parts of blocks) in files after they have been copied. <\/p>\n
Initially, it was thought that the problem only occurred in version 2.2.x and was caused by an error in the block cloning mechanism included in OpenZFS 2.2.0, which allows creating a copy of a file or its part without duplicating data, using references to already existing data blocks from the original file without actually copying them. In OpenZFS 2.2.1, to block the issue, the block cloning mechanism has been disabled by default, and a setting to enable zfs_bclone_enabled has been added for those wishing to revert to this mode. <\/p>\n
Later, developers reported that the issue could also be reproduced in configurations with the OpenZFS 2.1.x branch. The assumptions that the problem manifests on systems with older releases of the coreutils package were disproven \u2014 the error was able to be reproduced in FreeBSD and in Linux distributions with the latest coreutils 9.4 release. <\/p>\n
File corruption occurs under quite rare circumstances; for example, running the command \"emerge -1 dev-lang\/go\" in Gentoo results in the installation of the Go language toolkit with file corruption in the directory \/usr\/lib\/go\/pkg\/tool\/linux_amd64\/compile. It is assumed that the error began to manifest after the \"zfs_dmu_offset_next_sync=1\" parameter was set to default in OpenZFS version 2.1.4. The source of the error has not yet been identified. As a recommended workaround to block the error, it is suggested to set the parameter \"\/sys\/module\/zfs\/parameters\/zfs_dmu_offset_next_sync\" to 0. \n Source: opennet.ru<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"