News for hackers. Stuff that matters.
Re:In OpenZFS and Btrfs, everyone was just guessing by jiripospisil on Thursday November 30, 2023 @05:32PM (#38480136)
A more "correct" fix has been posted https://github.com/openzfs/zfs/pull/15615
Re:In OpenZFS and Btrfs, everyone was just guessing by jeffbee on Friday December 01, 2023 @10:09AM (#38487586)
Neither of these fixes are great because neither of them include tests. This is a dataloss bug in a filesystem, no existing test covered it, and no new tests were added to demonstrate the efficacy of the supposed fix or prevent regressions.
Re:In OpenZFS and Btrfs, everyone was just guessing by jiripospisil on Friday December 01, 2023 @10:55AM (#38488168)
There's an ongoing work on a stress test for this. https://github.com/openzfs/zfs/pull/15608
Re:In OpenZFS and Btrfs, everyone was just guessing by rincebrain on Friday December 01, 2023 @01:27PM (#38490337)
There was, actually, a test, but it turns out to be rather hard to make a deterministic test to reproduce a rare race condition without sticking your fingers in at runtime and forcing the "wrong" ordering.
Re:In OpenZFS and Btrfs, everyone was just guessing by mnd999 on Saturday December 02, 2023 @06:46AM (#38497919)
The same was true of the fix for the completely deterministic cp from unencrypted to encrypted with block cloning. There doesn’t seem to me much incentive to write tests.