Can database corruption be caused by a Windows Virtual Memory Resize?
Is it a known issue that allowing Windows to perform automatic resizing of the page file can cause Innodb corruption?
We had a stable production database crash to an unrecoverable state over the weekend, version: 5.7.22.
Here is the error in the log:
2021-08-21T00:16:41.834378Z 0 [ERROR] InnoDB: Database page corruption on disk or a failed file read of page [page id: space=13355, page number=6024]. You may have to recover from a backup.
At almost this same time, there is an "informational notice" in the Windows Event log:
2021-08-21T00:16:52.00000Z
Application popup: Windows - Virtual Memory Minimum Too Low : Your system is low on virtual memory. Windows is increasing the size of your virtual memory paging file. During this process, memory requests for some applications may be denied. For more information, see Help.
Subject
Views
Written By
Posted
Can database corruption be caused by a Windows Virtual Memory Resize?
722
August 23, 2021 07:13AM
314
August 23, 2021 11:39AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.