public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Zorro Lang <zlang@redhat.com>
To: fstests@vger.kernel.org
Subject: [PATCH v3] xfs: skip growfs test on large device
Date: Mon, 14 May 2018 22:41:53 +0800	[thread overview]
Message-ID: <20180514144153.14638-1-zlang@redhat.com> (raw)

When test on large SCRATCH_DEV, grow a small XFS to huge size is a
horrible thing (e.g grow 128M to 500T). So skip this kind of tests
if LARGE_SCRATCH_DEV is yes.

Signed-off-by: Zorro Lang <zlang@redhat.com>
---

V3 drops all _scratch_xfs_growfs related code. Turn to use
_require_no_large_scratch_dev.


 tests/xfs/002 | 1 +
 tests/xfs/127 | 1 +
 tests/xfs/233 | 1 +
 3 files changed, 3 insertions(+)

diff --git a/tests/xfs/002 b/tests/xfs/002
index 741117be..a6114748 100755
--- a/tests/xfs/002
+++ b/tests/xfs/002
@@ -51,6 +51,7 @@ _cleanup()
 _supported_fs xfs
 _supported_os Linux
 _require_scratch_nocheck
+_require_no_large_scratch_dev
 
 # So we can explicitly turn it _off_:
 _require_xfs_mkfs_crc
diff --git a/tests/xfs/127 b/tests/xfs/127
index 9df99904..60597fbf 100755
--- a/tests/xfs/127
+++ b/tests/xfs/127
@@ -45,6 +45,7 @@ _cleanup()
 _supported_os Linux
 _supported_fs xfs
 _require_scratch_reflink
+_require_no_large_scratch_dev
 _require_cp_reflink
 
 echo "Format and mount"
diff --git a/tests/xfs/233 b/tests/xfs/233
index e61c444d..b20dd4f1 100755
--- a/tests/xfs/233
+++ b/tests/xfs/233
@@ -44,6 +44,7 @@ _cleanup()
 _supported_os Linux
 _supported_fs xfs
 _require_xfs_scratch_rmapbt
+_require_no_large_scratch_dev
 
 echo "Format and mount"
 _scratch_mkfs_sized $((2 * 4096 * 4096)) > $seqres.full 2>&1
-- 
2.14.3


                 reply	other threads:[~2018-05-14 14:42 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180514144153.14638-1-zlang@redhat.com \
    --to=zlang@redhat.com \
    --cc=fstests@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox