I have completed most of my regression testing, and things are still looking
good. The performance of the block discard is there, and I haven't seen any
data corruption.
In particular, I have been testing against the testcase for the regression that
occurred with the previous revision of the patches, back in December. The
testcase is covered in bug 1907262 [1].
For each of the 5.11, 5.8, 5.4 and 4.15 kernels, the problem does not reproduce,
as the values of /sys/block/md0/md/mismatch_cnt are always 0, and mounting each
disk in singular and performing a full deep fsck shows no data corruption.
I have completed most of my regression testing, and things are still looking
good. The performance of the block discard is there, and I haven't seen any
data corruption.
In particular, I have been testing against the testcase for the regression that
occurred with the previous revision of the patches, back in December. The
testcase is covered in bug 1907262 [1].
[1] https:/ /bugs.launchpad .net/ubuntu/ +source/ linux/+ bug/1907262
For each of the 5.11, 5.8, 5.4 and 4.15 kernels, the problem does not reproduce, md0/md/ mismatch_ cnt are always 0, and mounting each
as the values of /sys/block/
disk in singular and performing a full deep fsck shows no data corruption.
Test results for each kernel are below:
5.11.0-16-generic #17+TEST1896578 v20210503b1- Ubuntu /paste. ubuntu. com/p/Dp3sR9mNd Y/
https:/
5.8.0-50-generic #56+TEST1896578 v20210504b1- Ubuntu /paste. ubuntu. com/p/tXmtmd5Jy s/
https:/
5.4.0-72-generic #80+TEST1896578 v20210504b1- Ubuntu /paste. ubuntu. com/p/VzX2mXcKb F/
https:/
4.15.0-142-generic #146+TEST189657 8v20210504b1- Ubuntu /paste. ubuntu. com/p/HpMcX3N9f D/
https:/
I think I will look into some longer running tests as well, more info on that
later.