From: bugzilla-daemon@kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 220594] Online defragmentation has broken in 6.16
Date: Thu, 20 Nov 2025 06:48:47 +0000 [thread overview]
Message-ID: <bug-220594-13602-T0C29jzqNj@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 #9 from Artem S. Tashkinov (aros@gmx.com) ---
Sadly it's still broken in 6.17:
ext4 defragmentation for ./birdie/.config/google-chrome/Default/Sync
Data/LevelDB/000435.log
Failed to defrag with EXT4_IOC_MOVE_EXT ioctl:Success [ NG ]
ls -la /home/birdie/.config/google/Default/Sync Data/LevelDB/000435.log
-rw-------. 1 birdie birdie 139150 Nov 19 10:22
'/home/birdie/.config/google-chrome/Default/Sync Data/LevelDB/000435.log'
A small file that is not getting defragmented and I have literally five dozens
of them.
And I have plenty of free space.
Filesystem volume name:
Last mounted on: /
Filesystem UUID:
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: ext_attr resize_inode dir_index filetype extent
flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize
Filesystem flags: signed_directory_hash
Default mount options: user_xattr acl
Filesystem state: not clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 1572864
Block count: 6287360
Reserved block count: 314367
Overhead clusters: 109963
Free blocks: 4126491
Free inodes: 1428171
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 1022
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 8192
Inode blocks per group: 512
Flex block group size: 16
Filesystem created:
Last mount time:
Last write time:
Mount count:
Maximum mount count: -1
Last checked:
Check interval: 0 (<none>)
Lifetime writes:
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 28
Desired extra isize: 28
Default directory hash: half_md4
Directory Hash Seed:
Journal backup: inode blocks
--
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-11-20 6:48 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
2025-09-28 2:17 ` bugzilla-daemon
2025-11-20 6:48 ` bugzilla-daemon [this message]
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-T0C29jzqNj@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;
as well as URLs for NNTP newsgroup(s).