Hi Thimo, Thanks for letting me know, and great to hear that things are working as expected. I'll check in with you in one week's time, to double check things are still going okay.
I spent some time today performing verification on all the kernels in -proposed, testing block discard performance [1], and also running through the regression testcase from LP #1907262 [2]. [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896578 [2] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907262 All kernels performed as expected, with block discard on 4x 1.9TB NVMe disks on an i3.8xlarge AWS instance taking 3-4 seconds, and the consistency checks performed returned clean disks, with no filesystem or data corruption. I have documented my tests in my verification messages: Hirsute: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896578/comments/26 Groovy: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896578/comments/27 Focal: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896578/comments/28 Bionic: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896578/comments/29 I have marked the launchpad bug as verified for all releases. I'm still running my own testing, with my /home directory being on a Raid10 array on a Google Cloud instance, and it has no issues. If things keep going well, we should see a release to -updates around the 21st of June, give or take a few days if any CVEs turn up. Thanks, Matthew -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907262 Title: raid10: discard leads to corrupted file system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907262/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
