Challenges with fstests and blktests [LWN.net]

Challenges with fstests and blktests

Posted Jun 1, 2022 17:14 UTC (Wed) by developer122 (guest, #152928)
Parent article: Challenges with fstests and blktests

I know the OpenZFS folks slam their filesystem for every changeset, but how much testing does BTRFS do? It seems like more comprehensive testing would enable a lot more of it's spurious bugs to be caught and fixed.

to post comments

Challenges with fstests and blktests

Posted Jun 3, 2022 12:48 UTC (Fri) by mcgrof (subscriber, #25917) [Link]

Each developer *aught* to run fstests or blktests, depending on what they are developing.

Each maintainer runs these tests as well.

To address low deterministic bugs however one must run the tests multiple times. That will vary by developer, maintainer and Linux distribution.

Do the math for what you can afford to test and in what timeline.

I doubt OpenZFS gets more test coverage than the aggregate testing of any real Linux filesystems for all Linux distributions ;) We all stand to gain each filesystem is tested heavily. If your filesystem is upstream you benefit from generic tests, there are tons. If you're filesystem is out of tree the onus is on you. OpenZFS stands out as a wonderful example of loosing out of everything valuable from the standard Linux filesystems test experience.