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

starting server with huge innodb-log-buffer-size may fail

    XMLWordPrintable

    Details

      Description

      Innodb tries to read more than 2GB from redo log, from an existing large redo log.
      This appears to succeed, but due to the tpool::pread() returning int, it is converted to negative value,

      C:\work\server\xxx\sql\RelWithDebInfo>mysqld --console --innodb-log-buffer-size=20G
      2022-02-10 15:11:27 0 [Note] mysqld (server 10.8.2-MariaDB) starting as process 37624 ...
      2022-02-10 15:11:27 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
      2022-02-10 15:11:27 0 [Note] InnoDB: Number of transaction pools: 1
      2022-02-10 15:11:27 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
      2022-02-10 15:11:27 0 [Note] InnoDB: Initializing buffer pool, total size = 10.000GiB, chunk size = 160.000MiB
      2022-02-10 15:11:27 0 [Note] InnoDB: Completed initialization of buffer pool
      2022-02-10 15:11:28 0 [Note] InnoDB: File system buffers for log disabled (block size=4096 bytes)
      2022-02-10 15:11:29 0 [Warning] InnoDB: Retry attempts for reading partial data failed.
      2022-02-10 15:11:29 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
      2022-02-10 15:11:29 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
      2022-02-10 15:11:29 0 [ERROR] InnoDB: File (unknown): 'read' returned OS error 403. Cannot continue operation
      220210 15:11:29 [ERROR] mysqld got exception 0x80000003 ;
      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.8.2-MariaDB
      key_buffer_size=134217728
      read_buffer_size=131072
      max_used_connections=0
      max_threads=65537
      thread_count=0
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 143178824 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...
      server.dll!my_parameter_handler()[my_init.c:353]
      ucrtbase.dll!raise()
      ucrtbase.dll!abort()
      server.dll!os_file_handle_error_cond_exit()[os0file.cc:3159]
      server.dll!os_file_read_page()[os0file.cc:3040]
      server.dll!os_file_read_func()[os0file.cc:3430]
      server.dll!log_file_t::read()[log0log.cc:158]
      server.dll!recv_scan_log()[log0recv.cc:3539]
      server.dll!recv_recovery_from_checkpoint_start()[log0recv.cc:3999]
      server.dll!srv_start()[srv0start.cc:1196]
      server.dll!innodb_init()[ha_innodb.cc:4205]
      server.dll!ha_initialize_handlerton()[handler.cc:649]
      server.dll!plugin_initialize()[sql_plugin.cc:1462]
      server.dll!plugin_init()[sql_plugin.cc:1755]
      server.dll!init_server_components()[mysqld.cc:5088]
      server.dll!mysqld_main()[mysqld.cc:5704]
      mysqld.exe!__scrt_common_main_seh()[exe_common.inl:288]
      KERNEL32.DLL!BaseThreadInitThunk()
      ntdll.dll!RtlUserThreadStart()
      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 at C:\work\server\xxx\sql\data\
      Minidump written to C:\work\server\xxx\sql\data\mysqld.dmp
      

        Attachments

          Activity

            People

            Assignee:
            wlad Vladislav Vaintroub
            Reporter:
            wlad Vladislav Vaintroub
            Votes:
            0 Vote for this issue
            Watchers:
            1 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.