From: Eric Whitney <enwlinux@gmail.com>
To: linux-ext4@vger.kernel.org
Cc: tytso@mit.edu
Subject: [PATCH] xfstests-bld: delete exclude files containing ext4 defrag tests
Date: Mon, 15 Aug 2016 13:24:59 -0400 [thread overview]
Message-ID: <20160815172459.GA2185@localhost.localdomain> (raw)
The _require_defrag function in xfstests can now correctly determine
whether an ext4 test file system supports the online defrag feature.
The exclude files that were added to prevent test failure noise when
running online defrag tests on journaled data and bigalloc file systems
are no longer necessary. These tests include ext4/301-304 and
ext4/307-308.
ext4/304 remains in the master exclude file for an unrelated problem.
Signed-off-by: Eric Whitney <enwlinux@gmail.com>
---
.../test-appliance/files/root/fs/ext4/cfg/bigalloc.exclude | 7 -------
.../test-appliance/files/root/fs/ext4/cfg/bigalloc_1k.exclude | 7 -------
.../test-appliance/files/root/fs/ext4/cfg/data_journal.exclude | 7 -------
.../files/root/fs/ext4/cfg/data_journal_noleak.exclude | 7 -------
4 files changed, 28 deletions(-)
delete mode 100644 kvm-xfstests/test-appliance/files/root/fs/ext4/cfg/bigalloc.exclude
delete mode 100644 kvm-xfstests/test-appliance/files/root/fs/ext4/cfg/bigalloc_1k.exclude
delete mode 100644 kvm-xfstests/test-appliance/files/root/fs/ext4/cfg/data_journal.exclude
delete mode 100644 kvm-xfstests/test-appliance/files/root/fs/ext4/cfg/data_journal_noleak.exclude
diff --git a/kvm-xfstests/test-appliance/files/root/fs/ext4/cfg/bigalloc.exclude b/kvm-xfstests/test-appliance/files/root/fs/ext4/cfg/bigalloc.exclude
deleted file mode 100644
index bd779be..0000000
--- a/kvm-xfstests/test-appliance/files/root/fs/ext4/cfg/bigalloc.exclude
+++ /dev/null
@@ -1,7 +0,0 @@
-# bigalloc does not support on-line defrag
-ext4/301
-ext4/302
-ext4/303
-ext4/304
-ext4/307
-ext4/308
diff --git a/kvm-xfstests/test-appliance/files/root/fs/ext4/cfg/bigalloc_1k.exclude b/kvm-xfstests/test-appliance/files/root/fs/ext4/cfg/bigalloc_1k.exclude
deleted file mode 100644
index bd779be..0000000
--- a/kvm-xfstests/test-appliance/files/root/fs/ext4/cfg/bigalloc_1k.exclude
+++ /dev/null
@@ -1,7 +0,0 @@
-# bigalloc does not support on-line defrag
-ext4/301
-ext4/302
-ext4/303
-ext4/304
-ext4/307
-ext4/308
diff --git a/kvm-xfstests/test-appliance/files/root/fs/ext4/cfg/data_journal.exclude b/kvm-xfstests/test-appliance/files/root/fs/ext4/cfg/data_journal.exclude
deleted file mode 100644
index 7190c8c..0000000
--- a/kvm-xfstests/test-appliance/files/root/fs/ext4/cfg/data_journal.exclude
+++ /dev/null
@@ -1,7 +0,0 @@
-# data_journal does not support on-line defrag
-ext4/301
-ext4/302
-ext4/303
-ext4/304
-ext4/307
-ext4/308
diff --git a/kvm-xfstests/test-appliance/files/root/fs/ext4/cfg/data_journal_noleak.exclude b/kvm-xfstests/test-appliance/files/root/fs/ext4/cfg/data_journal_noleak.exclude
deleted file mode 100644
index 7190c8c..0000000
--- a/kvm-xfstests/test-appliance/files/root/fs/ext4/cfg/data_journal_noleak.exclude
+++ /dev/null
@@ -1,7 +0,0 @@
-# data_journal does not support on-line defrag
-ext4/301
-ext4/302
-ext4/303
-ext4/304
-ext4/307
-ext4/308
--
2.1.4
reply other threads:[~2016-08-15 17:21 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=20160815172459.GA2185@localhost.localdomain \
--to=enwlinux@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).