Comments - InnoDB recovery under Maria
Content reproduced on this site is the property of its respective owners,
and this content is not reviewed in advance by MariaDB. The views, information and opinions
expressed by this content do not necessarily represent those of MariaDB or any other party.
I would still say the correct fix here is to avoid the InnoDB corruption in the first place, not try to work around it.
This kind of thing should not have to happen no matter how systems crash. But you need to configure your setup (virtualisation software + host disk system) so that when InnoDB does fsync(), it really gets to the disk and does not lie to InnoDB about it. If you've done that and still get this, it would indicate a bug in InnoDB I think that should be fixed...
I think you are right here.
Virtual box does not do a real flush by default. I will do some testing on this next week.
Thanks.