[DiscordArchive] are you not running a server?
[DiscordArchive] are you not running a server?
Original source
that way it's non-destructive
rektbyfaith
02-15-2024, 03:51 AM #11Archived author: Anchy • Posted: 2024-02-15T03:51:40.203000+00:00
Original source
that way it's non-destructive
Original source
Coming from google search:
```
It's a corruption.
See the failed assertion - page_is_comp(next_page) == page_is_comp(page). It checks if a next page is in the same format (COMPACT or REDUNDANT) as the current one.
InnoDB index can be in either format, but the mix is impossible.
So, go ahead with innodb_force_recovery=1,2,3,4,5,6 (try each value until MySQL starts), dump databases and re-create InnoDB tablespace from scratch.
If MySQL doesn't start even with innodb_force_recovery=6 or crashes when you query it (btw, add option --skip-lock-tables to mysqldump, it helps sometimes) then check out https://twindb.com/recover-corrupt-mysql-database/
```
Yours says `btr_page_get_prev(page, mtr) == FIL_NULL` but the idea is still the same.
rektbyfaith
02-15-2024, 09:54 AM #12Archived author: Revision • Posted: 2024-02-15T09:54:58.331000+00:00
Original source
Coming from google search:
```
It's a corruption.
See the failed assertion - page_is_comp(next_page) == page_is_comp(page). It checks if a next page is in the same format (COMPACT or REDUNDANT) as the current one.
InnoDB index can be in either format, but the mix is impossible.
So, go ahead with innodb_force_recovery=1,2,3,4,5,6 (try each value until MySQL starts), dump databases and re-create InnoDB tablespace from scratch.
If MySQL doesn't start even with innodb_force_recovery=6 or crashes when you query it (btw, add option --skip-lock-tables to mysqldump, it helps sometimes) then check out https://twindb.com/recover-corrupt-mysql-database/
```
Yours says `btr_page_get_prev(page, mtr) == FIL_NULL` but the idea is still the same.