Aikin OpenZFS 2.2.1, wanda ke haɓaka tsarin aiwatar da tsarin fayil na ZFS don Linux da FreeBSD, yanzu yana samuwa. Wannan sakin sananne ne don ƙara tallafi ga Linux 6.6 kernel da ƙoƙarin magance batun da zai iya haifar da ɓarnawar bayanai (batar da wasu tubalan) a cikin fayiloli bayan kwafa su.
Da farko, an yi imanin batun ya keɓanta da reshe na 2.2.x kuma ya haifar da bug a cikin tsarin toshe cloning wanda aka haɗa a cikin OpenZFS 2.2.0. Wannan tsarin yana ba da damar ƙirƙirar kwafin fayil ko ɓangarensa ba tare da kwafin bayanai ba, ta amfani da nassoshi na toshe bayanan da ke cikin ainihin fayil ɗin a cikin kwafi na biyu ba tare da kwafin su ba. A cikin OpenZFS 2.2.1, toshe cloning an kashe ta tsohuwa don rage matsalar, kuma an ƙara saitin zfs_bclone_enabled don maido da goyan bayan wannan yanayin.
Daga baya masu haɓakawa sun ba da rahoton sake fitar da batun a cikin daidaitawa tare da reshen OpenZFS 2.1.x. Zato cewa batun yana faruwa akan tsarin tare da tsofaffin abubuwan da aka fitar na kunshin coreutils suma an karyata-kuskuren an sami nasarar sake buga shi akan rarrabawar FreeBSD da Linux tare da sabon sakin coreutils 9.4.
Lalacewar fayil yana faruwa a ƙarƙashin ingantattun yanayi. Misali, gudanar da umarnin "fito-1 dev-lang/go" akan sakamakon Gentoo a cikin shigar da kayan aikin Go, wanda ke lalata fayiloli a cikin /usr/lib/go/pkg/tool/linux_amd64/compile directory. An yi imanin cewa kuskuren ya fara bayyana kansa bayan saita siginar "zfs_dmu_offset_next_sync=1" ta tsohuwa a cikin openzfs 2.1.4. Har yanzu ba a gano tushen kuskuren ba. Saita ma'aunin "/sys/module/zfs/parameters/zfs_dmu_offset_next_sync" zuwa 0 shine shawarar da aka ba da shawarar.
source: budenet.ru
