https://bugzilla.kernel.org/show_bug.cgi?id=201685 Laurent Bonnaud (L.Bonnaud@xxxxxxxxxxx) changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |L.Bonnaud@xxxxxxxxxxx --- Comment #67 from Laurent Bonnaud (L.Bonnaud@xxxxxxxxxxx) --- I am also experiencing ext4 corruptions with 4.19.x kernels. One way to trigger this bug that works almost every time on my system is to backup the whole FS with BorgBackup using this command: nice -19 ionice -c3 borg create -v --stats --list --filter=AME --one-file-system --exclude-caches --compression zstd --progress my-server:/borg-backup::'{hostname}-{now:%Y-%m-%d_%H:%M}' / Here are kernel messages: [ 916.082499] EXT4-fs error (device sda1): ext4_iget:4831: inode #6318098: comm borg: bad extra_isize 35466 (inode size 256) [ 916.093908] Aborting journal on device sda1-8. [ 916.096417] EXT4-fs (sda1): Remounting filesystem read-only [ 916.096799] EXT4-fs error (device sda1): ext4_iget:4831: inode #6318101: comm borg: bad extra_isize 35466 (inode size 256) [ 916.101544] EXT4-fs error (device sda1): ext4_iget:4831: inode #6318103: comm borg: bad extra_isize 35466 (inode size 256) [ 916.106531] EXT4-fs error (device sda1): ext4_iget:4831: inode #6318107: comm borg: bad extra_isize 35466 (inode size 256) [ 916.111039] EXT4-fs error (device sda1): ext4_iget:4831: inode #6318110: comm borg: bad extra_isize 35466 (inode size 256) [ 916.115763] EXT4-fs error (device sda1): ext4_iget:4831: inode #6318112: comm borg: bad extra_isize 35466 (inode size 256) If there is some interest, I can provide more details, but in another bug report since this one is already loaded with attached files. -- You are receiving this mail because: You are watching the assignee of the bug.
