Server crashes as a result of error :InnoDB: Cannot rename file
Description
Environment
Attachments
Smart Checklist
Activity
Jira Bot January 23, 2021 at 4:56 PM
Hello ,
It's been 52 days since this issue went into Incomplete and we haven't heard
from you on this.
At this point, our policy is to Close this issue, to keep things from getting
too cluttered. If you have more information about this issue and wish to
reopen it, please reply with a comment containing "jira-bot=reopen".
Jira Bot January 15, 2021 at 3:56 PM
Hello ,
It's jira-bot again. Your bug report is important to us, but we haven't heard
from you since the previous notification. If we don't hear from you on
this in 7 days, the issue will be automatically closed.
Jira Bot December 31, 2020 at 3:56 PM
Hello ,
I'm jira-bot, Percona's automated helper script. Your bug report is important
to us but we've been unable to reproduce it, and asked you for more
information. If we haven't heard from you on this in 3 more weeks, the issue
will be automatically closed.
Lalit Choudhary December 2, 2020 at 2:57 PM
I tried to reproduce this crash with the given configuration, I can not reproduce it.
Please upgrade the percona server to the latest version. I tested with 5.7.31.
Jira Bot November 28, 2020 at 11:57 AM
Hello ,
It's been 52 days since this issue went into Incomplete and we haven't heard
from you on this.
At this point, our policy is to Close this issue, to keep things from getting
too cluttered. If you have more information about this issue and wish to
reopen it, please reply with a comment containing "jira-bot=reopen".
The following statement is executed:
OPTIMIZE NO_WRITE_TO_BINLOG TABLE snmpdata.binding_table
Mysql Server crashes and the following error is seen in the mysql log file:
[Warning] InnoDB: Cannot rename file ./snmpdata/binding_table.ibd (space id 735), retried 15000 times. There are either pending IOs or flushes or the file is being extended.
Crash occurs on 5/17/2020, 5/21/2020, and 8/18/2020 in the attached log file.