https://bugzilla.kernel.org/show_bug.cgi?id=201685 --- Comment #156 from Guenter Roeck (linux@xxxxxxxxxxxx) --- Status update: I have not been able to reproduce the problem with v4.19.6 minus the reverts from #99. I did see some failures, specifically exactly one per affected file system, but I attribute those to false positives (I did not run fsck as recommended prior to starting the test). stats: System 1: uptime: 18h 45m iostats: Device tps MB_read/s MB_wrtn/s MB_read MB_wrtn loop0 0.00 0.00 0.00 0 0 nvme0n1 195.54 3.27 3.96 220723 267555 sda 128.88 0.36 18.91 24659 1277907 sdb 131.40 18.85 5.07 1273780 342404 nvme0n1 and sda were previously affected. sdb is a new drive. System 2: uptime: 14h 56m iostats: Device tps kB_read/s kB_wrtn/s kB_read kB_wrtn loop0 0.00 0.00 0.00 5 0 sda 26.45 538.25 87.87 28965283 4728576 sdb 108.87 2875.25 4351.42 154728917 234167724 Both sda and sdb were previously affected. My next step will be to try v4.19.6 with the following reverts: Revert "ext4: handle layout changes to pinned DAX mappings" Revert "dax: remove VM_MIXEDMAP for fsdax and device dax" Revert "ext4: close race between direct IO and ext4_break_layouts()" -- You are receiving this mail because: You are watching the assignee of the bug.
