NFS doesn't keep track of whether a file is reflinked or not, so it doesn't prevent this behavior. It shouldn't be a problem for NFS anyway, so just skip this test there. Signed-off-by: Jeff Layton <jlayton@xxxxxxxxxx> --- tests/generic/357 | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/tests/generic/357 b/tests/generic/357 index ce748f854327..a0299b32bc90 100755 --- a/tests/generic/357 +++ b/tests/generic/357 @@ -24,6 +24,11 @@ _cleanup() . ./common/reflink # real QA test starts here + +# For NFS, a reflink is just a CLONE operation, and after that +# point it's dealt with by the server. +_supported_fs ^nfs generic + _require_scratch_swapfile _require_scratch_reflink _require_cp_reflink -- 2.41.0
