From: "Darrick J. Wong" <djwong@kernel.org>
To: Disha Goel <disgoel@linux.ibm.com>
Cc: fstests@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-fsdevel@vger.kernel.org, ritesh.list@gmail.com,
ojaswin@linux.ibm.com, xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH] common/defrag: Skip defrag tests on DAX-enabled filesystems
Date: Tue, 2 Jun 2026 13:09:30 -0700 [thread overview]
Message-ID: <20260602200930.GB6054@frogsfrogsfrogs> (raw)
In-Reply-To: <20260602101418.55131-1-disgoel@linux.ibm.com>
On Tue, Jun 02, 2026 at 03:44:18PM +0530, Disha Goel wrote:
> Online defragmentation is not supported on DAX-enabled filesystems
> because DAX bypasses the page cache required for defrag operations.
>
> Add check in _require_defrag() to skip tests when DAX is enabled,
> avoiding false failures on ext4/301-304, ext4/308 and generic/018.
>
> Signed-off-by: Disha Goel <disgoel@linux.ibm.com>
> ---
> common/defrag | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/common/defrag b/common/defrag
> index 055d0d0e..28db2f7a 100644
> --- a/common/defrag
> +++ b/common/defrag
> @@ -6,6 +6,10 @@
>
> _require_defrag()
> {
> + # Defragmentation is not supported on DAX-enabled filesystems
> + if echo "$MOUNT_OPTIONS" | grep -qw "dax"; then
> + _notrun "Defragmentation not supported on DAX-enabled filesystem"
> + fi
Defrag doesn't work on XFS on DAX as well? It seems to work fine on my
VMs...
<confused>
--D
> case "$FSTYP" in
> xfs)
> # xfs_fsr does preallocates, require "falloc"
> --
> 2.45.1
>
>
next prev parent reply other threads:[~2026-06-02 20:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 10:14 [PATCH] common/defrag: Skip defrag tests on DAX-enabled filesystems Disha Goel
2026-06-02 10:38 ` Ojaswin Mujoo
2026-06-03 14:22 ` Disha Goel
2026-06-02 20:09 ` Darrick J. Wong [this message]
2026-06-03 14:20 ` Disha Goel
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=20260602200930.GB6054@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=disgoel@linux.ibm.com \
--cc=fstests@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=ojaswin@linux.ibm.com \
--cc=ritesh.list@gmail.com \
/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