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

InnoDB: fdatasync() returned 112

    XMLWordPrintable

Details

    Description

      Crashed with the following text:
      2024-04-04 21:02:53-05:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:11.3.2+maria~ubu2204 started.
      2024-04-04 21:02:54-05:00 [Note] [Entrypoint]: MariaDB upgrade not required
      2024-04-04 21:02:54 0 [Note] Starting MariaDB 11.3.2-MariaDB-1:11.3.2+maria~ubu2204 source revision 068a6819eb63bcb01fdfa037c9bf3bf63c33ee42 as process 1
      2024-04-04 21:02:54 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
      2024-04-04 21:02:54 0 [Note] InnoDB: Number of transaction pools: 1
      2024-04-04 21:02:54 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
      2024-04-04 21:02:54 0 [Note] mariadbd: O_TMPFILE is not supported on /tmp (disabling future attempts)
      2024-04-04 21:02:54 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB
      2024-04-04 21:02:54 0 [Note] InnoDB: Completed initialization of buffer pool
      2024-04-04 21:02:54 0 [Note] InnoDB: Buffered log writes (block size=512 bytes)
      2024-04-04 21:02:54 0 [Note] InnoDB: Resetting space id's in the doublewrite buffer
      2024-04-04 21:02:55 0 [Note] InnoDB: End of log at LSN=243719473440
      2024-04-04 21:02:55 0 [Note] InnoDB: Opened 3 undo tablespaces
      2024-04-04 21:02:55 0 [Note] InnoDB: 128 rollback segments in 3 undo tablespaces are active.
      2024-04-04 21:02:55 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ...
      2024-04-04 21:02:55 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB.
      2024-04-04 21:02:55 0 [Note] InnoDB: log sequence number 243719473440; transaction id 12610063
      2024-04-04 21:02:55 0 [Note] Plugin 'FEEDBACK' is disabled.
      2024-04-04 21:02:55 0 [Note] Plugin 'wsrep-provider' is disabled.
      2024-04-04 21:02:55 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
      2024-04-04 21:02:55 0 [Note] Server socket created on IP: '0.0.0.0'.
      2024-04-04 21:02:55 0 [Note] Server socket created on IP: '::'.
      2024-04-04 21:02:55 0 [Note] mariadbd: Event Scheduler: Loaded 0 events
      2024-04-04 21:02:55 0 [Note] mariadbd: ready for connections.
      Version: '11.3.2-MariaDB-1:11.3.2+maria~ubu2204' socket: '/run/mysqld/mysqld.sock' port: 3306 mariadb.org binary distribution
      2024-04-04 21:02:55 0 [Note] InnoDB: Buffer pool(s) load completed at 240404 21:02:55
      2024-04-04 22:50:20 0 [ERROR] [FATAL] InnoDB: fdatasync() returned 112
      240404 22:50:20 [ERROR] mysqld got signal 6 ;
      Sorry, we probably made a mistake, and this is a bug.
      Your assistance in bug reporting will enable us to fix this for the next release.
      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: 11.3.2-MariaDB-1:11.3.2+maria~ubu2204 source revision: 068a6819eb63bcb01fdfa037c9bf3bf63c33ee42
      key_buffer_size=134217728
      read_buffer_size=131072
      max_used_connections=4
      max_threads=153
      thread_count=4
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 468064 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
      Printing to addr2line failed
      mariadbd(my_print_stacktrace+0x32)[0x55c5810b88a2]
      mariadbd(handle_fatal_signal+0x478)[0x55c580b89488]
      /lib/x86_64-linux-gnu/libc.so.6(+0x42520)[0x7f2247824520]
      /lib/x86_64-linux-gnu/libc.so.6(pthread_kill+0x12c)[0x7f22478789fc]
      /lib/x86_64-linux-gnu/libc.so.6(raise+0x16)[0x7f2247824476]
      /lib/x86_64-linux-gnu/libc.so.6(abort+0xd3)[0x7f224780a7f3]
      mariadbd(+0x6d15a5)[0x55c5807865a5]
      mariadbd(+0x6b6f14)[0x55c58076bf14]
      mariadbd(+0xe05b00)[0x55c580ebab00]
      mariadbd(+0xe06544)[0x55c580ebb544]
      mariadbd(+0xea20ba)[0x55c580f570ba]
      mariadbd(_ZN5tpool19thread_pool_generic13timer_generic7executeEPv+0x40)[0x55c58104dd60]
      mariadbd(_ZN5tpool4task7executeEv+0x3a)[0x55c58104e82a]
      mariadbd(_ZN5tpool19thread_pool_generic11worker_mainEPNS_11worker_dataE+0x5f)[0x55c58104c8cf]
      /lib/x86_64-linux-gnu/libstdc++.so.6(+0xdc253)[0x7f2247bce253]
      /lib/x86_64-linux-gnu/libc.so.6(+0x94ac3)[0x7f2247876ac3]
      /lib/x86_64-linux-gnu/libc.so.6(clone+0x44)[0x7f2247907a04]
      The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/ contains
      information that should help you find out what is causing the crash.
      Writing a core file...
      Working directory at /var/lib/mysql
      Resource Limits:
      Limit Soft Limit Hard Limit Units
      Max cpu time unlimited unlimited seconds
      Max file size unlimited unlimited bytes
      Max data size unlimited unlimited bytes
      Max stack size 8388608 unlimited bytes
      Max core file size unlimited unlimited bytes
      Max resident set unlimited unlimited bytes
      Max processes unlimited unlimited processes
      Max open files 1048576 1048576 files
      Max locked memory 65536 65536 bytes
      Max address space unlimited unlimited bytes
      Max file locks unlimited unlimited locks
      Max pending signals 255218 255218 signals
      Max msgqueue size 819200 819200 bytes
      Max nice priority 0 0
      Max realtime priority 0 0
      Max realtime timeout unlimited unlimited us
      Core pattern: |/usr/share/apport/apport -p%p -s%s -c%c -d%d -P%P -u%u -g%g – %E
      Kernel version: Linux version 5.15.0-101-generic (buildd@lcy02-amd64-032) (gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #111-Ubuntu SMP Tue Mar 5 20:16:58 UTC 2024
      Fatal signal 11 while backtracing

      Attachments

        Activity

          People

            danblack Daniel Black
            livlif2fullest Robert Grandidier
            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.