We had similar behavior on GCE by running Elasticsearch through the following suite of unit tests: https://github.com/elastic/rally-eventdata-track
The test suite takes about 5 days to run fully and any corruption can be found by running: zgrep CorruptIndexException /var/log/elasticsearch/elasticsearch.log I was able to reproduce the corruption on all 4.15 kernels, but not on any 5.0 kernels. I was provided a test kernel with the commits mentioned above for 4.15.0-1051-gcp and I ran it through 3 different test iterations without a single report of corruption. As a control, I used the 4.15.0-1051-gcp kernel that is currently available from the proposed pocket (without the commits referenced in this LP) and the testing logged corruption on the 3rd day of tests. Thanks, Chris -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848739 Title: [linux-azure] Patch to prevent possible data corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1848739/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
