adamsurak

G Suite (Google Workspace) has a similar feature called Work Insights - https://support.google.com/workinsights

There is a simpler way by adding a different CA into the chain. You can add the version of USERTrust RSA CA that is signed by AAA Certificate Services (https://ssl-tools.net/subjects/cd30d24c343a82ab1f0570158ad7a...) and it will work.

They'll use legitimate interest as a reason.

Unless you run the latest kernel, I would disable TRIM.

We have multiple different pages. In our cluster we have 3 machines and if one of them is unavailable because of broken network, we do not page. In this case the page came as an application error that the application was not able to cope with. When we have issue that we have seen before and the server can handle it on its own, we do not page.

I completely agree and we are going this direction.

In this case it was un-queued TRIM (I forgot to mention it in the blogpost). We have reached to Samsung and although it looked good at the beginning now they are silent for more than a month without any progress.

The drives we have detected the issue had still un-queued TRIM. I have reached to one of the kernel I/O developers for help and he confirmed that it is not related.

With our architecture, HW requirements, the price of HW and the price of the cloud VMs, even working on this for a week or two saves us significant amount of money both short-term and long-term. The side effect is that we now have tools to recover servers way faster and allows us to do things we have not thought about before.

In this case the TRIM command was un-queued, which makes it worse.