On Tue, Jul 22, 2025 at 11:27:35AM +0100, Filipe Manana wrote: > > Can you please rework the patch to see that setting the nocow flag > > works first and only try with that or something like that? > > Reworking it is late as it's already in for-next, but we can add a > patch to skip it on zoned xfs: It though I explained it before, but let me try again. This is not about zoned xfs, zoned xfs is just the canary in the coal mine. The test fundamentally assumes file systems can overwrite without space allocations. And then noticed that this isn't true with a weird btrfs hack. It needs to be reworked to only run when that is known to be true. > > 1) The quickest way would be to add to the test: > _require_non_zoned_device $SCRATCH_DEV That test is not relevant here. While zoned device require out of place updates, they are also common for many other cases. > 2) Or add a "_require_nocow_data_writes" helper to check we can write > in place and skip the test if not, as you suggest, as it's more > generic in case there are other filesystems or configurations where > data writes are always COWed. That's the only thing that works. Only run on file systems that are known to do in-place updates, or in the odd btrfs case can be forced to even if they don't normally do it. To be honest the hardcoded btrfs hack should have been a big red flag, those almost always means the test is fishy.
