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

InnoDB: Missing FILE_CREATE... before FILE_CHECKPOINT returns after a year

Details

    Description

      MariaDB 11.1.2-GA on Windows 11 Pro crashes every couple of days, sometimes couple of hours with "InnoDB: Missing FILE_CREATE, FILE_DELETE or FILE_MODIFY before FILE_CHECKPOINT". Having no other way (details below and in linked pages) I decided to throw it away and reinstall whole stack again. It works for another couple of days and then started to crash (actually: fails to start) with exactly the same error in the same conditions.

      I am a total newbie an may be wrong, but from my perspective this is a regression of either: MDEV-28870, MDEV-31410 or MDEV-28976.

      All the details, including all the attempts of self-resolve this issue are given in two connected questions at Server Fault and Database Administrators. There is also my own answer to the first one. It provides more details and brings some resolution attempts tried.

      Here only some quick summary:

      1. The whole story started with April 2023 edition (latest) of XAMPP 8.2.4 which claims to have MariaDB 10.4.28 on-board. It was a "never-ending story" of MariaDB running for couple of days and then being unable to start with:

      mysqld.exe: Aria engine: checkpoint failed
      mysqld.exe: Can't sync file 'C:\XAMPP\mysql\data\aria_log.00000001' to disk (Errcode: 9 "Bad file descriptor")
      mysqld.exe: Error writing file 'C:\XAMPP\mysql\data\aria_log.00000001' (Errcode: 9 "Bad file descriptor")

      2. Not being able to do anything (every clean reinstall of whole XAMPP or just MariaDB was always lasting for no more than five days) I have decided to upgrade to MariaDB 11.1.2-GA.

      Here the "never-ending story" started back only this time the problem is with:

      InnoDB: Missing FILE_CREATE, FILE_DELETE or FILE_MODIFY before FILE_CHECKPOINT

      Thing that I have tried to resolve the above:

      • Setting innodb_force_recovery on any value
      • Deleting ib_logfile0
      • Setting innodb_log_file_size = 48M
      • Setting innodb_buffer_pool_size = 10M

      The only thing that I have found working and able to resolve the above are hardcore solutions of:

      • Deleting my corrupted files
      • Reinstalling MariaDB
      • Reinstalling whole XAMPP stack

      However, I cannot repeat these tasks over and over again.

      Attachments

        Activity

          For what it is worth, the reported error message cannot be from MariaDB Server 10.4. The log record format was changed and the internal names for the records renamed in MDEV-12353 (MariaDB Server 10.5). In MDEV-14425 (MariaDB Server 10.8), the log file format was changed further.

          marko Marko Mäkelä added a comment - For what it is worth, the reported error message cannot be from MariaDB Server 10.4. The log record format was changed and the internal names for the records renamed in MDEV-12353 (MariaDB Server 10.5). In MDEV-14425 (MariaDB Server 10.8), the log file format was changed further.

          trejder, did you have any more crashes? You wrote "I will definitely provide you with the copy of ib_logfile0 file, whenever next-time crash appears."

          If you didn't — feel free to ignore this, it'll be closed after a month of no activity (and reopened, if you provide more information later). This my comment will keep it open till the end of December.

          serg Sergei Golubchik added a comment - trejder , did you have any more crashes? You wrote "I will definitely provide you with the copy of ib_logfile0 file, whenever next-time crash appears." If you didn't — feel free to ignore this, it'll be closed after a month of no activity (and reopened, if you provide more information later). This my comment will keep it open till the end of December.
          trejder Tomasz added a comment -

          Sergei, I haven't faced any new crashes, because for past month I am running MariaDB as Windows 11 system service. Where crashes does not occur.

          I can't switch back to non-service run (where crashes occur) because I am and the go-live moment of my project and can't waste any more hours to trying to reinstall MariaDB on my dev environment.

          I will try to do some more tests on non-service, crash-prone run a couple of weeks later when my project is over, sorry.

          trejder Tomasz added a comment - Sergei, I haven't faced any new crashes, because for past month I am running MariaDB as Windows 11 system service. Where crashes does not occur. I can't switch back to non-service run (where crashes occur) because I am and the go-live moment of my project and can't waste any more hours to trying to reinstall MariaDB on my dev environment. I will try to do some more tests on non-service, crash-prone run a couple of weeks later when my project is over, sorry.

          trejder, normally we close issues where we don't have enough information to do anything and the issue didn't have any activity for a month. Now this my comment counts as "activity", so the timer here is reset, but if nothing happens we'll close it in early February. Don't worry, though, there's no hurry, you can still comment any time you like and we'll reopen the issue as needed.

          serg Sergei Golubchik added a comment - trejder , normally we close issues where we don't have enough information to do anything and the issue didn't have any activity for a month. Now this my comment counts as "activity", so the timer here is reset, but if nothing happens we'll close it in early February. Don't worry, though, there's no hurry, you can still comment any time you like and we'll reopen the issue as needed.
          trejder Tomasz added a comment -

          Sergiei, I haven't provided any new feedback so far, because I wasn't able to reproduce this issue again. For the sake of stability of my project, I changed my local server configuration to run database server as a service. When run as a service it never faces the described problem. Yes, go ahead and close this ticket. If I ever manage to reproduce this issue again, I'll file another one and link to this one. Thank you.

          trejder Tomasz added a comment - Sergiei, I haven't provided any new feedback so far, because I wasn't able to reproduce this issue again. For the sake of stability of my project, I changed my local server configuration to run database server as a service. When run as a service it never faces the described problem. Yes, go ahead and close this ticket. If I ever manage to reproduce this issue again, I'll file another one and link to this one. Thank you.

          People

            marko Marko Mäkelä
            trejder Tomasz
            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.