From: bugzilla-daemon@kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 221007] Online ext4 defragmentation fails on 'inline' files (feature inline_data_
Date: Sun, 25 Jan 2026 16:48:18 +0000 [thread overview]
Message-ID: <bug-221007-13602-cGrypAZfVd@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-221007-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=221007
Christian Kujau (kernel@nerdbynature.de) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kernel@nerdbynature.de
--- Comment #1 from Christian Kujau (kernel@nerdbynature.de) ---
While not necessarily a kernel issue, it's reproducible here once the
inline_data flag is set:
-----------------------------------
$ uname -rm
6.19.0-rc6-snafu aarch64
$ pv -Ss 512m /dev/zero > test.img
$ losetup -f test.img
$ mkfs.ext4 -O inline_data -F /dev/loop0
$ mount -t ext4 /dev/loop0 /mnt/disk/
$ date > /mnt/disk/file.txt
$ ulimit -c unlimited
$ e4defrag /mnt/disk/
e4defrag 1.47.2 (1-Jan-2025)
ext4 defragmentation for directory(/mnt/disk/)
Segmentation fault (core dumped)
-----------------------------------
Some debugging output:
-----------------------------------
$ gdb -c core /usr/sbin/e4defrag
(gdb) bt
#0 0x0000aaaaca774390 in file_defrag (file=0xaaaadca9b7e0
"/mnt/disk/file.txt", buf=0xffffea194a90, flag=<optimized out>,
ftwbuf=<optimized out>) at ../../../misc/e4defrag.c:1559
#1 0x0000ffff8d041760 [PAC] in process_entry (data=data@entry=0xffffea194c08,
dir=dir@entry=0xffffea194b80, name=name@entry=0xaaaadca9c883 "file.txt",
namlen=<optimized out>, d_type=<optimized out>)
at ../sysdeps/wordsize-64/../../io/ftw.c:472
#2 0x0000ffff8d041bc0 [PAC] in ftw_dir (data=data@entry=0xffffea194c08,
st=st@entry=0xffffea194c60, old_dir=old_dir@entry=0x0) at
../sysdeps/wordsize-64/../../io/ftw.c:551
#3 0x0000ffff8d042350 [PAC] in ftw_startup (dir=dir@entry=0xffffea194f40
"/mnt/disk", is_nftw=is_nftw@entry=1, func=func@entry=0xaaaaca7736e0
<file_defrag>, descriptors=descriptors@entry=2000,
flags=flags@entry=3) at ../sysdeps/wordsize-64/../../io/ftw.c:771
#4 0x0000ffff8d042460 [PAC] in __new_nftw (path=path@entry=0xffffea194f40
"/mnt/disk", func=func@entry=0xaaaaca7736e0 <file_defrag>,
descriptors=descriptors@entry=2000, flags=flags@entry=3)
at ../sysdeps/wordsize-64/../../io/ftw.c:844
#5 0x0000aaaaca7722c4 in main (argc=<optimized out>, argv=0xffffea198148) at
../../../misc/e4defrag.c:1913
-----------------------------------
Recompiling the userspace tools with -g should help (and I did that on another
machine), but I can't make sense of the details shown :-\
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2026-01-25 16:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-23 12:13 [Bug 221007] New: Online ext4 defragmentation fails on 'inline' files (feature inline_data_ bugzilla-daemon
2026-01-25 16:48 ` bugzilla-daemon [this message]
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-221007-13602-cGrypAZfVd@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