@@ -52,8 +52,8 @@ done
swapon $testfile 2>&1 | _filter_scratch
# Can we write to it?
-$XFS_IO_PROG -c 'pwrite -S 0x59 64k 64k' $testfile
-$XFS_IO_PROG -d -c 'pwrite -S 0x60 64k 64k' $testfile
+$XFS_IO_PROG -c 'pwrite -S 0x59 64k 64k' $testfile 2>&1 | _filter_xfs_io_error
+$XFS_IO_PROG -d -c 'pwrite -S 0x60 64k 64k' $testfile 2>&1 | _filter_xfs_io_error
$XFS_IO_PROG -c 'mmap -rw 64k 64k' -c 'mwrite -S 0x61 64k 64k' $testfile
# Can we change the file size?
@@ -47,8 +47,8 @@ done
swapon $SCRATCH_DEV 2>&1 | _filter_scratch
# Can we write to it?
-$XFS_IO_PROG -c 'pwrite -S 0x59 64k 64k' $SCRATCH_DEV
-$XFS_IO_PROG -d -c 'pwrite -S 0x60 64k 64k' $SCRATCH_DEV
+$XFS_IO_PROG -c 'pwrite -S 0x59 64k 64k' $SCRATCH_DEV 2>&1 | _filter_xfs_io_error
+$XFS_IO_PROG -d -c 'pwrite -S 0x60 64k 64k' $SCRATCH_DEV 2>&1 | _filter_xfs_io_error
$XFS_IO_PROG -c 'mmap -rw 64k 64k' -c 'mwrite -S 0x61 64k 64k' $SCRATCH_DEV
# success, all done
When I backport fix commits into old kernel, pwrite action will report "pwrite64: Text file busy". Since xfsprogs without commit 2f9a125c3a39 ("xfsprogs: replace pread64/pwrite64 by equivalent pread/pwrite"), it will report pwrite64. I think these kernel patchs are simple, old kernel with lower version xfsprogs may backport these commits. So filter it. Signed-off-by: Yang Xu <xuyang2018.jy@cn.fujitsu.com> --- tests/generic/569 | 4 ++-- tests/generic/570 | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-)