Missing FILE_CHECKPOINT(*) at * recovery

Hello,

few of our nodes running 10.11.9 have managed to hit the dreaded:

2024-11-05  8:38:17 0 [ERROR] InnoDB: Missing FILE_CHECKPOINT(64995256970708) at 64996778124892

2024-11-05  8:38:17 0 [ERROR] InnoDB: Log scan aborted at LSN 64996778124892

For which the recovery is to use innodb_force_recovery=6, dump with partial data loss due to index corruption in some tables, reinit datadir and reimport.

mysqldump: Error 1034: Index for table 'wp_options' is corrupt; try to repair it when dumping table `wp_options` at row: 129

Upgrading to 10.11.10 (6acada713a95a605b3aa65bd519fbd4532ad23e5, also CI build) after this had happened does not usually help. Except in one case, it did, with the `0e8fb977b00983d98c4c35e39bc1f36463095938` CI build.

I can see work was done on MDEV-34689, but I assume it's for squashing the root cause and not for recovery? If it was meant to help recovery, we still have datadir with the issue available to help test if needed.
We're planning to upgrade to MariaDB 10.11.10 ASAP.

Thanks