On Tue, Nov 27, 2018 at 03:48:19PM +0100, Marek Habersack wrote: > On 27/11/2018 15:32, Guenter Roeck wrote: > Hi, > > You might try to see if you have CONFIG_SCSI_MQ_DEFAULT=yes in your kernel config. Starting with 4.19.1 it somehow Yes, it is enabled in my configuration. > interferes with ext4 and causes problems similar to the ones you list below. Ever since I disabled MQ (either recompile > your kernel or add `scsi_mod.use_blk_mq=0` to the kernel command line) none of those errors came back. > I'll try that. Thanks a lot for the hint! Guenter > hope it helps, > > marek > > [trying again, this time with correct kernel.org address] > > > > Hi, > > > > I have seen the following and similar problems several times, > > with both v4.19.3 and v4.19.4: > > > > Nov 23 04:32:25 mars kernel: [112668.673671] EXT4-fs error (device sdb1): ext4_iget:4831: inode #12602889: comm git: bad > > extra_isize 33661 (inode size 256) > > Nov 23 04:32:25 mars kernel: [112668.675217] Aborting journal on device sdb1-8. > > Nov 23 04:32:25 mars kernel: [112668.676681] EXT4-fs (sdb1): Remounting filesystem read-only > > Nov 23 04:32:25 mars kernel: [112668.808886] EXT4-fs error (device sdb1): ext4_iget:4831: inode #12602881: comm rm: bad > > extra_isize 33685 (inode size 256) > > ... > > > > Nov 25 00:12:43 saturn kernel: [59377.725984] EXT4-fs error (device sda1): ext4_lookup:1578: inode #238034131: comm > > updatedb.mlocat: deleted inode referenced: 238160407 > > Nov 25 00:12:43 saturn kernel: [59377.766638] Aborting journal on device sda1-8. > > Nov 25 00:12:43 saturn kernel: [59377.779372] EXT4-fs (sda1): Remounting filesystem read-only > > ... > > > > Nov 24 01:52:31 saturn kernel: [189085.240016] EXT4-fs error (device sda1): ext4_lookup:1578: inode #52038457: comm > > nfsd: deleted inode referenced: 52043796 > > Nov 24 01:52:31 saturn kernel: [189085.263427] Aborting journal on device sda1-8. > > Nov 24 01:52:31 saturn kernel: [189085.275313] EXT4-fs (sda1): Remounting filesystem read-only > > > > > > The same systems running v4.18.6 never experienced a problem. > > > > Has anyone else seen similar problems ? Is there anything I can do > > to help tracking down the problem ? > > > > Thanks, > > Guenter > > >
