F
F
Futurism2021-08-19 19:57:26
MySQL
Futurism, 2021-08-19 19:57:26

Why does MySQL crash when accessing a table?

Good afternoon.

There is a table in a DB, in it the data.
When reading from it - everything seems to be fine.
When writing new lines - too (although it seems to me that writing to it is much slower than it should be) .

When you try to delete old rows (by any method - and truncate, and delete), as well as when you try to delete or rename a table, the query hangs and MySQL crashes.

The error.log only writes the following:

2021-08-19T11:02:34.724839Z 0 [Warning] InnoDB: Retry attempts for reading partial data failed.
2021-08-19T11:02:34.724884Z 0 [ERROR] InnoDB: Tried to read 8192 bytes at offset 6692732928, but was only able to read 0
2021-08-19T11:02:34.724896Z 0 [ERROR] InnoDB: Operating system error number 5 in a file operation.
2021-08-19T11:02:34.724908Z 0 [ERROR] InnoDB: Error number 5 means 'Input/output error'
2021-08-19T11:02:34.724917Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2021-08-19T11:02:34.724934Z 0 [ERROR] InnoDB: File (unknown): 'read' returned OS error 105. Cannot continue operation
2021-08-19T11:02:34.724949Z 0 [ERROR] InnoDB: Cannot continue operation.
2021-08-19T11:02:36.926378Z 0 [Note] InnoDB: FTS optimize thread exiting.


smartctl says the disk is fine.
badblocks (in read only mode) doesn't find anything bad either.

What could it be and how to fix it?

Answer the question

In order to leave comments, you need to log in

1 answer(s)
L
Lazy @BojackHorseman MySQL, 2021-08-19
Tag

Judging by the forums - this is a hardware error. It is advised to restore to another medium from the last backup.
I personally did not come across this.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question