All work

Select view

Select search mode

 
50 of 815

Disabling the table encryption while innodb-force-recovery=6 or read-only=1 leads to a server crash

Won't Do

Description

gdb:

sql:

Reproduced on debug build of: RM-390 (57a9574def950d8dfc8ae5ba6f1367a7bad39622)

I'm able to reproduce this on a release build as well:

Environment

None

Details

Assignee

Reporter

Time tracking

15m logged

Affects versions

Priority

Created November 1, 2018 at 4:55 AM
Updated March 4, 2025 at 9:02 PM
Resolved March 4, 2025 at 9:02 PM

Activity

Show:

Julia Vural 
March 4, 2025 at 9:02 PM

It appears that this issue is no longer being worked on, so we are closing it for housekeeping purposes. If you believe the issue still exists, please open a new ticket after confirming it's present in the latest release.

Tomislav Plavcic 
January 28, 2020 at 9:34 PM

I have another case where --read-only=1 so this is probably related to the fact that in both cases the server is in read-only mode. From what I see this affects 5.7.29 (debug/release), but not 8.0.18 (since the variable innodb_force_recovery is not available there).

Another test case:

GDB:

Hrvoje Matijakovic 
November 1, 2018 at 5:04 AM

Setting the innodb_force_recovery to values between 0-5 works ok: