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

Maria DB crashes randomly on creating indexes

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 10.0.12
    • Fix Version/s: 10.0.13
    • Component/s: None
    • Labels:
      None
    • Environment:
      Windows 8.1 update

      Description

      Since i upgraded to 10.0.12 i have a lot of issues with mariadb crashing on innodb operations like create indexes and create primary keys.

      First i had problems with FTS indexes creation and SELECT FTS in queries, so i had to start mariadb in recovery mode to be able to dump all the databases and delete all data files to recreate everything from 0 and import all sql files.

      Now FTS works(doesn't crash the server) but i get random crash when creating indexes in tables(indexes of any kinds). Also for foreign keys.

      This is example of log entries when i start the server after a crash.
      with 10.0.10 i didn't had any problems.

      2014-07-08 10:08:40 206c InnoDB: Error: Write to file .\ib_logfile0 failed at offset 43800576.
      InnoDB: 512 bytes should have been written, only 512 were written.
      InnoDB: Operating system error number 6.
      InnoDB: Check that your OS and file system support files of this size.
      InnoDB: Check also that the disk is not full or a disk quota exceeded.
      InnoDB: Error number 6 means 'No such device or address'.
      InnoDB: Some operating system error numbers are described at
      InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
      2014-07-08 10:08:40 206c  InnoDB: Assertion failure in thread 8300 in file os0file.cc line 4738
      InnoDB: Failing assertion: ret
      InnoDB: We intentionally generate a memory trap.
      InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
      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: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
      InnoDB: about forcing recovery.
      140708 10:08:58 [Note] InnoDB: Using mutexes to ref count buffer pool pages
      140708 10:08:58 [Note] InnoDB: The InnoDB memory heap is disabled
      140708 10:08:58 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
      140708 10:08:58 [Note] InnoDB: Compressed tables use zlib 1.2.3
      140708 10:08:58 [Note] InnoDB: Not using CPU crc32 instructions
      140708 10:08:58 [Note] InnoDB: Initializing buffer pool, size = 128.0M
      140708 10:08:58 [Note] InnoDB: Completed initialization of buffer pool
      140708 10:08:58 [Note] InnoDB: Highest supported file format is Barracuda.
      140708 10:08:58 [Note] InnoDB: Log scan progressed past the checkpoint lsn 45412682
      140708 10:08:58 [Note] InnoDB: Database was not shutdown normally!
      140708 10:08:58 [Note] InnoDB: Starting crash recovery.
      140708 10:08:58 [Note] InnoDB: Reading tablespace information from the .ibd files...
      140708 10:08:59 [Note] InnoDB: Restoring possible half-written data pages 
      140708 10:08:59 [Note] InnoDB: from the doublewrite buffer...
      InnoDB: Doing recovery: scanned up to log sequence number 45415670
      140708 10:09:00 [Note] InnoDB: Starting an apply batch of log records to the database...
      InnoDB: Progress in percent: 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 
      InnoDB: Apply batch completed
      InnoDB: Last MySQL binlog file position 0 29349107, file name .\mysql-bin.000006
      140708 10:09:00 [Note] InnoDB: 128 rollback segment(s) are active.
      140708 10:09:01 [Note] InnoDB: Waiting for purge to start
      140708 10:09:01 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.17-65.0 started; log sequence number 45415670
      140708 10:09:01 [Note] Plugin 'FEEDBACK' is disabled.
      140708 10:09:01 [Note] Recovering after a crash using mysql-bin
      140708 10:09:01 [Note] Starting crash recovery...
      140708 10:09:01 [Note] Crash recovery finished.
      140708 10:09:01 [Note] Server socket created on IP: '::'.
      140708 10:09:01 [Note] Event Scheduler: Loaded 0 events
      140708 10:09:01 [Note] MySQL: ready for connections.
      Version: '10.0.12-MariaDB-log'  socket: ''  port: 3306  mariadb.org binary distribution

        Attachments

        1. my.ini
          5 kB
        2. variables.txt
          334 kB

          Activity

            People

            • Assignee:
              jplindst Jan Lindström
              Reporter:
              adisoftbn Adrian Nicoara
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: