diff options
| author | Jeff Layton <jlayton@kernel.org> | 2023-09-01 13:39:56 -0400 |
|---|---|---|
| committer | Zorro Lang <zlang@kernel.org> | 2023-09-02 13:54:38 +0800 |
| commit | cf1ef0daf48864827e2712638a76d2aebbaa1ba0 (patch) | |
| tree | e05d606cf2bf8ded806eded7c2f95ad30b8b5c21 | |
| parent | b6f51cac4dbe30d509e1c206720303c118b4d360 (diff) | |
| download | xfstests-dev-cf1ef0daf48864827e2712638a76d2aebbaa1ba0.tar.gz | |
generic/357: don't run this test on NFS
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@kernel.org>
Reviewed-by: Zorro Lang <zlang@redhat.com>
Signed-off-by: Zorro Lang <zlang@kernel.org>
| -rwxr-xr-x | tests/generic/357 | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/tests/generic/357 b/tests/generic/357 index ce748f8543..0f3e02d5b5 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 + _require_scratch_swapfile _require_scratch_reflink _require_cp_reflink |