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

InnoDB: Operating system error number 4 in a file operation,

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • 10.3.38
    • None
    • Using MariaDB 10.3.38-MariaDB source revision
      CRIO v1.19.0 , containerd 12.x Ceph 14.2.7 and ceph-csi 3.1.1
      Kernel version: Linux 4.18.0-372.26.1.2210101416.el7_9.emrs.ulnx.x86_64 x86_64 generic k8 v1.21.14 crio_version v1.19.0

    Description

      During this older mariadb server 10.3.38 version noticed below crash , Currently interested if this is known issue and any info about fix in which specific release version it has being added ?

      Below are the details about the crash effort so far from https://mariadb.com/kb/en/operating-system-error-codes/
      4 EINTR Interrupted system call , Looking to understand the reason for the Interrupted system call triggered by mariadb process ?

      2024-03-27  7:25:08 0 [Note] Starting MariaDB 10.3.38-MariaDB source revision c73985f2ce8a391582787f3e310a011c1a712bec as process 48
      2024-03-27  7:25:08 0 [Note] InnoDB: Using Linux native AIO
      2024-03-27  7:25:08 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
      2024-03-27  7:25:08 0 [Note] InnoDB: Uses event mutexes
      2024-03-27  7:25:08 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
      2024-03-27  7:25:08 0 [Note] InnoDB: Number of pools: 1
      2024-03-27  7:25:08 0 [Note] InnoDB: Using SSE2 crc32 instructions
      2024-03-27  7:25:08 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
      2024-03-27  7:25:08 0 [Note] InnoDB: Completed initialization of buffer pool
      2024-03-27  7:25:08 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
      2024-03-27  7:25:08 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
      2024-03-27  7:25:08 0 [Note] InnoDB: Creating shared tablespace for temporary tables
      2024-03-27  7:25:08 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
      2024-03-27  7:25:08 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
      2024-03-27  7:25:08 0 [Note] InnoDB: 10.3.38 started; log sequence number 1941375; transaction id 352
      2024-03-27  7:25:08 0 [Note] InnoDB: Loading buffer pool(s) from /bitnami/mariadb/data/ib_buffer_pool
      2024-03-27  7:25:08 0 [Note] InnoDB: Buffer pool(s) load completed at 240327  7:25:08
      2024-03-27  7:25:09 0 [Note] Plugin 'FEEDBACK' is disabled.
      2024-03-27  7:25:09 0 [Note] Server socket created on IP: '127.0.0.1'.
      2024-03-27  7:25:09 0 [Note] Reading of all Master_info entries succeeded
      2024-03-27  7:25:09 0 [Note] Added new Master_info '' to hash table
      2024-03-27  7:25:09 0 [Note] /opt/bitnami/mariadb/sbin/mysqld: ready for connections.
      Version: '10.3.38-MariaDB'  socket: '/opt/bitnami/mariadb/tmp/mysql.sock'  port: 3306  Source distribution
      2024-03-27  7:25:10 0 [Note] /opt/bitnami/mariadb/sbin/mysqld (initiated by: unknown): Normal shutdown
      2024-03-27  7:25:10 0 [Note] InnoDB: FTS optimize thread exiting.
      2024-03-27  7:25:10 0 [Note] InnoDB: Starting shutdown...
      2024-03-27  7:25:10 0 [Note] InnoDB: Dumping buffer pool(s) to /bitnami/mariadb/data/ib_buffer_pool
      2024-03-27  7:25:10 0 [Note] InnoDB: Buffer pool(s) dump completed at 240327  7:25:10
      2024-03-27  7:25:12 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
      2024-03-27  7:25:12 0 [Note] InnoDB: Shutdown completed; log sequence number 1941384; transaction id 353
      2024-03-27  7:25:12 0 [Note] /opt/bitnami/mariadb/sbin/mysqld: Shutdown complete
       
      2024-03-27  7:25:12 0 [Note] Starting MariaDB 10.3.38-MariaDB source revision c73985f2ce8a391582787f3e310a011c1a712bec as process 1
      2024-03-27  7:25:13 0 [Note] InnoDB: Using Linux native AIO
      2024-03-27  7:25:13 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
      2024-03-27  7:25:13 0 [Note] InnoDB: Uses event mutexes
      2024-03-27  7:25:13 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
      2024-03-27  7:25:13 0 [Note] InnoDB: Number of pools: 1
      2024-03-27  7:25:13 0 [Note] InnoDB: Using SSE2 crc32 instructions
      2024-03-27  7:25:13 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
      2024-03-27  7:25:13 0 [Note] InnoDB: Completed initialization of buffer pool
      2024-03-27  7:25:13 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
      2024-03-27  7:25:13 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
      2024-03-27  7:25:13 0 [Note] InnoDB: Creating shared tablespace for temporary tables
      2024-03-27  7:25:13 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
      2024-03-27  7:25:13 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
      2024-03-27  7:25:13 0 [Note] InnoDB: Waiting for purge to start
      2024-03-27  7:25:13 0 [Note] InnoDB: 10.3.38 started; log sequence number 1941384; transaction id 352
      2024-03-27  7:25:13 0 [Note] InnoDB: Loading buffer pool(s) from /bitnami/mariadb/data/ib_buffer_pool
      2024-03-27  7:25:13 0 [Note] InnoDB: Buffer pool(s) load completed at 240327  7:25:13
      2024-03-27  7:25:13 0 [Note] Plugin 'FEEDBACK' is disabled.
      2024-03-27  7:25:13 0 [Note] Server socket created on IP: '::'.
      2024-03-27  7:25:13 0 [Note] Reading of all Master_info entries succeeded
      2024-03-27  7:25:13 0 [Note] Added new Master_info '' to hash table
      2024-03-27  7:25:13 0 [Note] /opt/bitnami/mariadb/sbin/mysqld: ready for connections.
      Version: '10.3.38-MariaDB'  socket: '/opt/bitnami/mariadb/tmp/mysql.sock'  port: 3306  Source distribution
      <<<<<<skipped some info>>>>
      2024-04-08  2:34:03 0 [ERROR] InnoDB: Operating system error number 4 in a file operation.
      2024-04-08  2:34:03 0 [ERROR] InnoDB: Error number 4 means 'Interrupted system call'
      2024-04-08  2:34:03 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
      2024-04-08 02:34:03 0x7fae356f9700  InnoDB: Assertion failure in file /bitnami/blacksmith-sandox/mariadb-10.3.38/storage/innobase/fil/fil0fil.cc line 4479
      InnoDB: Failing assertion: err == DB_SUCCESS
      InnoDB: We intentionally generate a memory trap.
      InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
      InnoDB: If you get repeated assertion failures or crashes, even
      InnoDB: immediately after the mysqld startup, there may be
      InnoDB: corruption in the InnoDB tablespace. Please refer to
      InnoDB: https://mariadb.com/kb/en/library/innodb-recovery-modes/
      InnoDB: about forcing recovery.
      240408  2:34:03 [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.
       
      To report this bug, see https://mariadb.com/kb/en/reporting-bugs
       
      We will try our best to scrape up some info that will hopefully help
      diagnose the problem, but since we have already crashed,
      something is definitely wrong and this may fail.
       
      Server version: 10.3.38-MariaDB source revision: c73985f2ce8a391582787f3e310a011c1a712bec
      key_buffer_size=134217728
      read_buffer_size=131072
      max_used_connections=7
      max_threads=153
      thread_count=12
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467435 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x0
      Attempting backtrace. You can use the following information to find out
      where mysqld died. If you see no messages after this, something went
      terribly wrong...
      stack_bottom = 0x0 thread_stack 0x49000
      /opt/bitnami/mariadb/sbin/mysqld(my_print_stacktrace+0x29)[0x561b62b60939]
      /opt/bitnami/mariadb/sbin/mysqld(handle_fatal_signal+0x54d)[0x561b6270036d]
      /lib/x86_64-linux-gnu/libpthread.so.0(+0x13140)[0x7fae58946140]
      /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x141)[0x7fae58796ce1]
      /lib/x86_64-linux-gnu/libc.so.6(abort+0x123)[0x7fae58780537]
      /opt/bitnami/mariadb/sbin/mysqld(+0x4e3b97)[0x561b62445b97]
      /opt/bitnami/mariadb/sbin/mysqld(+0x4f6ded)[0x561b62458ded]
      /opt/bitnami/mariadb/sbin/mysqld(+0x9f4140)[0x561b62956140]
      /lib/x86_64-linux-gnu/libpthread.so.0(+0x7ea7)[0x7fae5893aea7]
      /lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7fae5885aa2f]
      The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains
      information that should help you find out what is causing the crash.
      Writing a core file...
      Working directory at /bitnami/mariadb/data
      Resource Limits:
      Fatal signal 11 while backtracing
      

      Attachments

        Activity

          People

            danblack Daniel Black
            sridhar2288 Sridhar Kasula
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:

              Git Integration

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