From: bugzilla-daemon@kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 216317] New: "ext4: lblock 0 mapped to illegal pblock" after upgrading to 5.19.0
Date: Tue, 02 Aug 2022 05:49:49 +0000 [thread overview]
Message-ID: <bug-216317-13602@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=216317
Bug ID: 216317
Summary: "ext4: lblock 0 mapped to illegal pblock" after
upgrading to 5.19.0
Product: File System
Version: 2.5
Kernel Version: 5.19.0
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: ext4
Assignee: fs_ext4@kernel-bugs.osdl.org
Reporter: gerbilsoft@gerbilsoft.com
Regression: No
On upgrading to kernel 5.19.0, I hit a bunch of warnings and inaccessible
files. Attempting to access e.g. /etc/alsa/conf.d/51-pulseaudio-probe.conf
(symlink to ../../../usr/share/alsa/alsa.conf.d/51-pulseaudio-probe.conf)
resulted in a "Structure needs cleaning" error. Checking dmesg shows the
following:
Aug 02 01:10:43 [kernel] [ 12.037708] EXT4-fs error (device dm-2):
ext4_map_blocks:599: inode #14680223: block 774843950: comm alsactl: lblock 0
mapped to illegal pblock 774843950 (length 1)
Aug 02 01:10:43 [kernel] [ 12.039070] EXT4-fs error (device dm-2):
ext4_map_blocks:599: inode #14680223: block 774843950: comm alsactl: lblock 0
mapped to illegal pblock 774843950 (length 1)
Aug 02 01:10:43 [kernel] [ 12.041453] EXT4-fs error (device dm-2):
ext4_map_blocks:599: inode #14680223: block 774843950: comm alsactl: lblock 0
mapped to illegal pblock 774843950 (length 1)
Aug 02 01:10:43 [kernel] [ 12.043086] EXT4-fs error (device dm-2):
ext4_map_blocks:599: inode #14680223: block 774843950: comm alsactl: lblock 0
mapped to illegal pblock 774843950 (length 1)
Aug 02 01:10:43 [kernel] [ 12.045207] EXT4-fs error (device dm-2):
ext4_map_blocks:599: inode #14680223: block 774843950: comm alsactl: lblock 0
mapped to illegal pblock 774843950 (length 1)
Lots of other files were also showing the same issue. Reverting to 5.18.10 (and
running fsck) fixed it with no noticeable corruption.
Rootfs is ext4, using LVM-on-LUKS. (/dev/sda2 is a LUKS volume that contains an
LVM physical volume.) I have inline data turned on; the symlink is 60 bytes, so
it could be an inline data issue, but other symlinks in /etc/alsa/conf.d/
weren't showing the problem.
--
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 reply other threads:[~2022-08-02 5:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-02 5:49 bugzilla-daemon [this message]
2022-08-02 5:50 ` [Bug 216317] "ext4: lblock 0 mapped to illegal pblock" after upgrading to 5.19.0 bugzilla-daemon
2022-08-02 5:58 ` bugzilla-daemon
2022-08-02 6:14 ` bugzilla-daemon
2022-08-17 14:59 ` 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-216317-13602@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).