https://bugzilla.kernel.org/show_bug.cgi?id=201685 --- Comment #33 from Jimmy.Jazz@xxxxxxx --- (In reply to Jens Axboe from comment #28) > If it's not this, another hint might be a discard change. Is everyone > affected using discard? All 'cat /sys/block/dm-*/dm/use_blk_mq' are zero. Could MQ still be a suspect ? I reproduced the issue with 4.19.3 as well but without your patch. The difference is, it happens less often but still under heavy load (hours of work, mostly compilations and monitoring). The strange is, the affected disks are not obliged to be under load and on the next reboot fsck -f show some of them as clean despite they were declared with ext4_iget corruptions (tested during reboot from 4.19.2 to 4.19.3 kernel)! It's like some shared fs cache failure to me with unpleasant consequences. Disabling user_xattr seems to be more helpful with 4.20.0-rc3 anyway, no error since. Actually not under heavy load. Failures appear also on an plain old HDD device. For me, SSD discard is more a consequence as a reason but it's worse investigating it. I will try your patch ASAP. Thx -- You are receiving this mail because: You are watching the assignee of the bug.
