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

uring tmpfs InnoDB: IO Error: 125 during async write of X bytes, for file Y, returned 0

Details

    • Bug
    • Status: Stalled (View Workflow)
    • Major
    • Resolution: Unresolved
    • 10.6, 10.7(EOL), 10.8(EOL), 10.9(EOL), 10.10(EOL), 10.11, 11.0(EOL), 11.1(EOL), 11.2(EOL)
    • 10.6, 10.11
    • Storage Engine - InnoDB
    • None

    Description

      Almost always on kvm-deb-bullseye-aarch64 (old bb) worker. tmpfs based directory.

      Usually encryption.innodb* tests though mariabackup.huge_lsn too.

      Notable non-aarch64 exception:

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDBF-358 buildbot: raise memlock limits so uring is actually tested in containers

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Task - A task that needs to be done. MDEV-24883 add io_uring support for tpool

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-27593 Crashing on I/O error is unhelpful

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed
          links to

          Web Link debian bug 1020831

          Activity

            Transition Time In Source Status Execution Times
            Daniel Black made transition -
            Open Closed
            		167d 17h 30m 1
            Marko Mäkelä made transition -
            Closed Stalled
            		108d 13h 25m 1

            People

              Unassigned Unassigned
              danblack Daniel Black
              Votes:
              0 Vote for this issue
              Watchers:
              6 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.