mariadb/storage/innobase/log
Thirunarayanan Balathandayuthapani c5fe1b8fc1 MDEV-16866 InnoDB fails to start upon crash recovery with "[ERROR] InnoDB: Redo log crypto: failed to decrypt log block"
- If InnoDB encounters garbage or incomplete written log block during
recovery then don't throw the error. Treat it as end of the log.
- This kind of incomplete or empty block can be result of killing
InnoDB when writing the redo log.
2019-06-12 12:17:13 +05:30
..
log0crypt.cc Merge branch '5.5' into 10.1 2019-05-11 22:19:05 +03:00
log0log.cc Merge branch '5.5' into 10.1 2019-05-11 19:15:57 +03:00
log0recv.cc MDEV-16866 InnoDB fails to start upon crash recovery with "[ERROR] InnoDB: Redo log crypto: failed to decrypt log block" 2019-06-12 12:17:13 +05:30