> Jan Vlach <ja...@volny.cz> hat am 23.11.2023 23:35 CET geschrieben: > > > Hello Martin, > > I'm sorry for stupid question, but I don't quite follow what the OpenZFS > 2.2.0 with "the most important bugfixes from 2.2.1" means. > > there is issue 15526 (https://github.com/openzfs/zfs/issues/15526 > <https://github.com/openzfs/zfs/issues/15526>) in openzfs that enables block > cloning feature by default and that on linux "eats" data. > > OpenZFS 2.2.1 specifically switches the block cloning on by default to off by > default and nothing else. ( > https://github.com/openzfs/zfs/commit/479dca51c66a731e637bd2d4f9bba01a05f9ac9f > > <https://github.com/openzfs/zfs/commit/479dca51c66a731e637bd2d4f9bba01a05f9ac9f> > ) > > So is the code at 2.2.0 (toxic) eating data by default or at 2.2.1 where > block cloning is disabled by default and therefore safe? > > Thank you for clarification, > JV
we cherry-picked the relevant patches from 2.2.1, but it seems there is now new information that block cloning just made the bug easier to trigger but was not actually the cause. we'll include any follow-up fixes promptly after testing, as usual. https://git.proxmox.com/?p=zfsonlinux.git;a=commit;h=96c807af63f70dc930328e5801659a5bd40e6d47 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
