From: Theodore Ts'o Date: Thu, 9 Jun 2016 18:42:31 +0000 (-0400) Subject: shared/272: don't try to use O_DIRECT X-Git-Tag: v2022.05.01~2497 X-Git-Url: http://git.apps.os.sepia.ceph.com/?a=commitdiff_plain;h=795ea36a18c559412d8a2062e6ea49aeee764f70;p=xfstests-dev.git shared/272: don't try to use O_DIRECT A comment in shared/272 claims that ext4 supports O_DIRECT in data=journalling mode. Actually, it doesn't, it was just silently ignoring O_DIRECT, let's not try to test O_DIRECT for either ext3 or ext4 in this test. Signed-off-by: Theodore Ts'o Reviewed-by: Eryu Guan Signed-off-by: Eryu Guan --- diff --git a/tests/shared/272 b/tests/shared/272 index e5adf385..7023b657 100755 --- a/tests/shared/272 +++ b/tests/shared/272 @@ -31,10 +31,8 @@ tmp=/tmp/$$ status=1 # failure is the default! trap "rm -f $tmp.*; exit \$status" 0 1 2 3 15 -# ext3 doesn't support direct IO in journalling mode +# ext3 and ext4 don't support direct IO in journalling mode write_opt_list="iflag=noatime conv=notrunc conv=fsync" -# For filesystems that can handle it, add also direct IO test -[ $FSTYP = "ext4" ] && write_opt_list="$write_opt_list oflag=direct" # get standard environment, filters and checks . ./common/rc