From: Eric Whitney <enwlinux@gmail.com>
To: fstests@vger.kernel.org
Cc: linux-ext4@vger.kernel.org, tytso@mit.edu
Subject: [PATCH] common/defrag: rework _require_defrag for ext4
Date: Thu, 4 Aug 2016 16:02:46 -0400 [thread overview]
Message-ID: <20160804200246.GA2208@localhost.localdomain> (raw)
The existing _require_defrag function rejects ext4 file systems
mounted with the dax option or constructed without extents. However,
there are also a number of other ext4 file system configuration cases
that do not currently support online defrag, including encryption, data
journaling, and bigalloc. In the future, online defrag functionality
may be implemented for some of these, and new configuration cases
could be added that don't support it.
Rather than add a laundry list of mount and file system configuration
options to the existing _require_defrag function that will need ongoing
maintenance, use the available src/e4compact program to directly
determine whether the kernel supports ext4's move extent ioctl on the
test file system.
Signed-off-by: Eric Whitney <enwlinux@gmail.com>
---
common/defrag | 17 +++++++++++------
1 file changed, 11 insertions(+), 6 deletions(-)
diff --git a/common/defrag b/common/defrag
index 7db0cb4..986b4bf 100644
--- a/common/defrag
+++ b/common/defrag
@@ -27,14 +27,19 @@ _require_defrag()
DEFRAG_PROG="$XFS_FSR_PROG"
;;
ext4|ext4dev)
- echo $MOUNT_OPTIONS | grep -q dax
+ testfile="$TEST_DIR/$$-test.defrag"
+ donorfile="$TEST_DIR/$$-donor.defrag"
+ bsize=`get_block_size $TEST_DIR`
+ $XFS_IO_PROG -f -c "pwrite -b $bsize 0 $bsize" $testfile > /dev/null
+ cp $testfile $donorfile
+ echo $testfile | $here/src/e4compact -v -f $donorfile | \
+ grep -q "err:95"
if [ $? -eq 0 ]; then
- _notrun "$FSTYP defragmentation not supported with DAX"
- else
- DEFRAG_PROG="$E4DEFRAG_PROG"
+ rm -f $testfile $donorfile 2>&1 > /dev/null
+ _notrun "$FSTYP test filesystem doesn't support online defrag"
fi
- dumpe2fs -h $TEST_DEV 2> /dev/null | grep -wq extent || \
- _notrun "file system does not have extents, needed for defrag"
+ rm -f $testfile $donorfile 2>&1 > /dev/null
+ DEFRAG_PROG="$E4DEFRAG_PROG"
;;
btrfs)
DEFRAG_PROG="$BTRFS_UTIL_PROG filesystem defragment"
--
2.1.4
next reply other threads:[~2016-08-04 19:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-04 20:02 Eric Whitney [this message]
2016-08-11 17:48 ` [PATCH] common/defrag: rework _require_defrag for ext4 Christoph Hellwig
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=20160804200246.GA2208@localhost.localdomain \
--to=enwlinux@gmail.com \
--cc=fstests@vger.kernel.org \
--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