Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-23734

InnoDB: File (unknown): 'read' returned OS error 205. Cannot continue operation

Details

    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.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-13542 Crashing on a corrupted page is unhelpful

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            atullalwani Atul Lalwani created issue -
            marko Marko Mäkelä added a comment -

            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.

            marko Marko Mäkelä added a comment - 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.
            marko Marko Mäkelä made changes -
            Field Original Value New Value
            marko Marko Mäkelä made changes -
            Component/s Storage Engine - InnoDB [ 10129 ]
            Labels need_feedback
            serg Sergei Golubchik made changes -
            Fix Version/s N/A [ 14700 ]
            Resolution Incomplete [ 4 ]
            Status Open [ 1 ] Closed [ 6 ]
            serg Sergei Golubchik made changes -
            Workflow MariaDB v3 [ 113480 ] MariaDB v4 [ 158370 ]

            People

              Unassigned Unassigned
              atullalwani Atul Lalwani
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.