https://bugzilla.kernel.org/show_bug.cgi?id=201685 --- Comment #38 from Rainer Fiebig (jrf@xxxxxxxxxxx) --- (In reply to Jimmy.Jazz from comment #37) > @Jen Axboe > > please read worth not worse in comment 33 > > I tried your patch for 4.19.3 and still get quite harmful ext4 errors like > this one, > > EXT4-fs error (device dm-4): ext4_xattr_ibody_get:592: inode #4881425: comm > rsync: corrupted in-inode xattr > > The filesystems were clean at boot time and the system was idle. > > tune2fs ends with > FS Error count: 64 > First error time: Fri Nov 23 00:19:25 2018 > First error function: ext4_xattr_ibody_get > First error line #: 592 > First error inode #: 4881425 > First error block #: 0 > Last error time: Fri Nov 23 00:19:25 2018 > Last error function: ext4_xattr_ibody_get > Last error line #: 592 > Last error inode #: 4881430 > Last error block #: 0 > MMP block number: 9255 > MMP update interval: 5 > > If you are interested in its dumpe2fs result let me know. > > I don't use binary modules. Jimmy, what *I* would do if I were in your shoes is - run a kernel < 4.19, make sure the fs is OK and *backup important data* - compile 4.19.3 with CONFIG_SCSI_MQ_DEFAULT *not* set and see what happens. If you still get corruption, CONFIG_SCSI_MQ_DEFAULT probably is not the culprit. If not, it has at least something to do with it. It seems that CONFIG_SCSI_MQ_DEFAULT *not* set was the default <= 4.18.19. Others here obviously don't have problems with CONFIG_SCSI_MQ_DEFAULT=y and kernels >= 4.19, but you never know. -- You are receiving this mail because: You are watching the assignee of the bug.
