From: bugzilla-daemon@kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 220594] Online defragmentation has broken in 6.16
Date: Sat, 27 Sep 2025 13:19:52 +0000 [thread overview]
Message-ID: <bug-220594-13602-uaLNLSEc7a@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220594-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=220594
--- Comment #7 from Artem S. Tashkinov (aros@gmx.com) ---
Created attachment 308721
--> https://bugzilla.kernel.org/attachment.cgi?id=308721&action=edit
My 6.16 configuration
I remember from the log that you sent, there were quite a lot of failures, over
9000 of them.
Are you sure your scripts handles this?
e4defrag -v uBlock0\@raymondhill.net.xpi; echo $?
e4defrag 1.47.2 (1-Jan-2025)
ext4 defragmentation for uBlock0@raymondhill.net.xpi
[1/1]uBlock0@raymondhill.net.xpi: 0%
Failed to defrag with EXT4_IOC_MOVE_EXT ioctl:Success [ NG ]
Success: [0/1]
1
So, it's "successful" except it's not.
> is specific to Artem's kernel or hardware configuration.
I thought ext4 code is quite independent from the rest of the kernel and no
other kernel options can possibly affect it.
gzip -d < /proc/config.gz | grep -i ext4
CONFIG_EXT4_FS=y
CONFIG_EXT4_USE_FOR_EXT2=y
CONFIG_EXT4_FS_POSIX_ACL=y
CONFIG_EXT4_FS_SECURITY=y
# CONFIG_EXT4_DEBUG is not set
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2025-09-27 13:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-22 17:57 [Bug 220594] New: Online defragmentation has broken in 6.16 bugzilla-daemon
2025-09-22 18:04 ` [Bug 220594] " bugzilla-daemon
2025-09-25 12:14 ` bugzilla-daemon
2025-09-25 14:24 ` bugzilla-daemon
2025-09-25 18:44 ` bugzilla-daemon
2025-09-25 20:44 ` bugzilla-daemon
2025-09-26 21:29 ` bugzilla-daemon
2025-09-27 13:19 ` bugzilla-daemon [this message]
2025-09-28 2:17 ` bugzilla-daemon
2025-11-20 6:48 ` bugzilla-daemon
2025-11-24 5:15 ` Theodore Tso
2025-11-20 6:52 ` bugzilla-daemon
2025-11-24 5:15 ` bugzilla-daemon
2025-11-24 16:13 ` bugzilla-daemon
2025-11-24 16:33 ` Theodore Tso
2025-11-24 16:33 ` bugzilla-daemon
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=bug-220594-13602-uaLNLSEc7a@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-ext4@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