I'm seeing generic/154 failing sometimes. It does a "cp --reflink" (which uses FI_CLONE, which results in a ->remap_file_range call that NFS maps to the CLONE operation), then overwriting parts of the fire, and checking free blocks (with "stat -f /path -c "%f") at various points, and failing when the number of free blocks is outside an expected range. I don't know if it might be some caching issue, or something about how NFS reports free blocks. Honestly it looks unlikely to be critical, so for now I'm ignoring it.... --b.