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 Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1848739 Title: [linux-azure] Patch to prevent possible data corruption Status in linux-azure package in Ubuntu: Confirmed Status in linux-azure source package in Xenial: Fix Committed Bug description: There are three patches that prevent possible data corruption. The three commits are: aef1897cd36d ("blk-mq: insert rq with DONTPREP to hctx dispatch list when requeue") c616cbee97ae ("blk-mq: punt failed direct issue to dispatch list") 923218f6166a ("blk-mq: don't allocate driver tag upfront for flush rq") 18.04 has all three of these patches. 16.04 has two out of the three, but it is missing commit c616cbee97ae. We would like to request commit c616cbee97ae be included in the 16.04 kernel: c616cbee97ae ("blk-mq: punt failed direct issue to dispatch list") To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1848739/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
