[MDEV-23734]  InnoDB: File (unknown): 'read' returned OS error 205. Cannot continue operation Created: 2020-09-14  Updated: 2020-10-12  Resolved: 2020-10-12

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Affects Version/s: 10.4.12
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Atul Lalwani Assignee: Unassigned
Resolution: Incomplete Votes: 0
Labels: need_feedback
Environment:

Test

Attachments: Text File mariadblogs crash.txt    
Issue Links:
Relates
relates to MDEV-13542 Crashing on a corrupted page is unhel... Closed

 Description   

cluster status in kubernetes is giving error and we see the db is down due to bug message shown in error. Kindly check the attached logs and revert.

4 11:30:24 [ERROR] mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.

 Comments   
Comment by Marko Mäkelä [ 2020-09-14 ]

InnoDB can add 100 or 200 to the original error code. The command

perror 5

tells me the following:

OS error code   5:  Input/output error

Please check for any errors in

sudo dmesg
 
sudo smartctl -a /dev/sda

and other logs. Yes, as reported in MDEV-13542, InnoDB could handle theses better.

The stack trace in mariadblogs crash.txt is not resolved. Please try to follow https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ and provide a resolved stack trace.

Generated at Thu Feb 08 09:24:38 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.