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

ib_logfile0 is too small for innodb_thread_concurrency=0. The size of ib_logfile0 should be bigger than 200 kB * innodb_thread_concurrency.

Details

    Description

      main/ML_101.test   (The content does not matter.)
      --source include/have_innodb.inc
      CREATE TABLE t1 (col1 INT) ENGINE = InnoDB;
      DROP TABLE t1;
       
      ./mysql-test-run.pl --mem --mysqld=--innodb_page_size=64K --mysqld=--innodb_log_file_size=5000000 --mysqld=--innodb_buffer_pool_size=24M --record --mysqld=--default_storage_engine=innodb ML_101
      fails during bootstrap.
       
      ...
      2020-04-21 15:36:40 0 [Note] InnoDB: innodb_page_size=65536
      2020-04-21 15:36:40 0 [Note] InnoDB: Using Linux native AIO
      2020-04-21 15:36:40 0 [Note] InnoDB: The first innodb_system data file 'ibdata1' did not exist. A new tablespace will be created!
      2020-04-21 15:36:40 0 [Note] InnoDB: !!!!!!!! UNIV_DEBUG switched on !!!!!!!!!
      2020-04-21 15:36:40 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
      2020-04-21 15:36:40 0 [Note] InnoDB: Uses event mutexes
      2020-04-21 15:36:40 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
      2020-04-21 15:36:40 0 [Note] InnoDB: Number of pools: 1
      2020-04-21 15:36:40 0 [Note] InnoDB: Using SSE2 crc32 instructions
      2020-04-21 15:36:40 0 [Note] mariadbd: O_TMPFILE is not supported on /home/mleich/Server_bin/10.5_debug/mysql-test/var/tmp/ (disabling future attempts)
      2020-04-21 15:36:40 0 [Note] InnoDB: Initializing buffer pool, total size = 25165824, chunk size = 25165824
      2020-04-21 15:36:40 0 [Note] InnoDB: Completed initialization of buffer pool
      2020-04-21 15:36:40 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
      2020-04-21 15:36:40 0 [Note] InnoDB: Setting file './ibdata1' size to 12 MB. Physically writing the file full; Please wait ...
      2020-04-21 15:36:40 0 [Note] InnoDB: File './ibdata1' size is now 12 MB.
      2020-04-21 15:36:40 0 [Note] InnoDB: Setting log file ./ib_logfile101 size to 4980736 bytes
      2020-04-21 15:36:40 0 [ERROR] InnoDB: Cannot continue operation. ib_logfile0 is too small for innodb_thread_concurrency=0. The size of ib_logfile0 should be bigger than 200 kB * innodb_thread_concurrency. Please refer to https://mariadb.com/kb/en/library/innodb-system-variables/
             <== I am aware that there might be reasons why some action is impossible.
                      But the justification for the abort is not acceptable.
      origin/10.5 2f7d91bb6ce7bb34dd644e30590189bce37fb8f1 2020-04-14T18:43:03+03:00
       
      In addition the same test worked well on actual
      - 10.1, 10.2, 10.4, 10.4   (64K page size + innodb_log_file_size=5000000)
      - even 10.5 but only with
        - 64K pagesize +  innodb_log_file_size=8000000 or higher
        - 32K pagesize + even the small  innodb_log_file_size=5000000
       
      
      

      Attachments

        Issue Links

          Activity

            MDEV-14462 was already filed for a similar message.

            marko Marko Mäkelä added a comment - MDEV-14462 was already filed for a similar message.

            10.5.4  origin/10.5 c2a929185c147fc85bbf91e2c537bcdd98f2e680 2020-05-27T18:56:49+03:00
            2020-05-29 17:01:03 0 [Note] InnoDB: Header page consists of zero bytes in datafile: ./ibdata1, Space ID:0, Flags: 0
            2020-05-29 17:01:03 0 [ERROR] InnoDB: Corrupted page [page id: space=0, page number=0] of datafile './ibdata1' could not be found in the doublewrite buffer.
            2020-05-29 17:01:03 0 [ERROR] InnoDB: Plugin initialization aborted at srv0start.cc[1378] with error Data structure corruption
            2020-05-29 17:01:03 0 [Note] InnoDB: Starting shutdown...
             
            10.4.14 origin/10.4 4783494a5e21939424ecca92bf23d2df65528266 2020-05-29T16:19:15+03:00
            ./mysql-test-run.pl --mem --mysqld=--innodb_page_size=64K --mysqld=--innodb_log_file_size=5000000 --mysqld=--innodb_buffer_pool_size=24M --record --mysqld=--default_storage_engine=innodb --suite=innodb ML_101
            Logging: ./mysql-test-run.pl  --mem --mysqld=--innodb_page_size=64K --mysqld=--innodb_log_file_size=5000000 --mysqld=--innodb_buffer_pool_size=24M --record --mysqld=--default_storage_engine=innodb --suite=innodb ML_101
            vardir: /home/mleich/Server_bin/10.4_debug/mysql-test/var
            Removing old var directory...
            Creating var directory '/home/mleich/Server_bin/10.4_debug/mysql-test/var'...
             - symlinking 'var' to '/dev/shm/var_auto_cJt5'
            Checking supported features...
            MariaDB Version 10.4.14-MariaDB-debug
             - SSL connections supported
             - binaries are debug compiled
            Collecting tests...
            Installing system database...
             
            ==============================================================================
             
            TEST                                      RESULT   TIME (ms) or COMMENT
            --------------------------------------------------------------------------
             
            worker[1] Using MTR_BUILD_THREAD 300, with reserved ports 16000..16019
            innodb.ML_101 'innodb'                   [ pass ]      6
            --------------------------------------------------------------------------
            The servers were restarted 0 times
            Spent 0.006 of 14 seconds executing testcases
             
            Completed: All 1 tests were successful.
             
            
            

            mleich Matthias Leich added a comment - 10.5.4 origin/10.5 c2a929185c147fc85bbf91e2c537bcdd98f2e680 2020-05-27T18:56:49+03:00 2020-05-29 17:01:03 0 [Note] InnoDB: Header page consists of zero bytes in datafile: ./ibdata1, Space ID:0, Flags: 0 2020-05-29 17:01:03 0 [ERROR] InnoDB: Corrupted page [page id: space=0, page number=0] of datafile './ibdata1' could not be found in the doublewrite buffer. 2020-05-29 17:01:03 0 [ERROR] InnoDB: Plugin initialization aborted at srv0start.cc[1378] with error Data structure corruption 2020-05-29 17:01:03 0 [Note] InnoDB: Starting shutdown...   10.4.14 origin/10.4 4783494a5e21939424ecca92bf23d2df65528266 2020-05-29T16:19:15+03:00 ./mysql-test-run.pl --mem --mysqld=--innodb_page_size=64K --mysqld=--innodb_log_file_size=5000000 --mysqld=--innodb_buffer_pool_size=24M --record --mysqld=--default_storage_engine=innodb --suite=innodb ML_101 Logging: ./mysql-test-run.pl --mem --mysqld=--innodb_page_size=64K --mysqld=--innodb_log_file_size=5000000 --mysqld=--innodb_buffer_pool_size=24M --record --mysqld=--default_storage_engine=innodb --suite=innodb ML_101 vardir: /home/mleich/Server_bin/10.4_debug/mysql-test/var Removing old var directory... Creating var directory '/home/mleich/Server_bin/10.4_debug/mysql-test/var'... - symlinking 'var' to '/dev/shm/var_auto_cJt5' Checking supported features... MariaDB Version 10.4.14-MariaDB-debug - SSL connections supported - binaries are debug compiled Collecting tests... Installing system database...   ==============================================================================   TEST RESULT TIME (ms) or COMMENT --------------------------------------------------------------------------   worker[1] Using MTR_BUILD_THREAD 300, with reserved ports 16000..16019 innodb.ML_101 'innodb' [ pass ] 6 -------------------------------------------------------------------------- The servers were restarted 0 times Spent 0.006 of 14 seconds executing testcases   Completed: All 1 tests were successful.  

            People

              kevg Eugene Kosov (Inactive)
              mleich Matthias Leich
              Votes:
              0 Vote for this issue
              Watchers:
              2 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.