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@xxxxxxxxxxxxxxxxxxxx Reporter: gerbilsoft@xxxxxxxxxxxxxx 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.
