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

mysqld: O_TMPFILE is not supported on /tmp (disabling future attempts)

Details

    • Bug
    • Status: Closed (View Workflow)
    • Minor
    • Resolution: Not a Bug
    • 10.4.12
    • N/A
    • Configuration
    • None
    • UBUNTU 18.04 / Linux

    Description

      I cannot find what the cause of this message is.

      log file

      2020-04-09 7:41:33 0 [Note] InnoDB: Using Linux native AIO
      2020-04-09 7:41:33 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
      2020-04-09 7:41:33 0 [Note] InnoDB: Uses event mutexes
      2020-04-09 7:41:33 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
      2020-04-09 7:41:33 0 [Note] InnoDB: Number of pools: 1
      2020-04-09 7:41:33 0 [Note] InnoDB: Using SSE2 crc32 instructions
      2020-04-09 7:41:33 0 [Note] mysqld: O_TMPFILE is not supported on /tmp (disabling future attempts)
      2020-04-09 7:41:33 0 [Note] InnoDB: Initializing buffer pool, total size = 512M, instances = 1, chunk size = 128M
      2020-04-09 7:41:33 0 [Note] InnoDB: Completed initialization of buffer pool
      2020-04-09 7:41:33 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-09 7:41:33 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
      2020-04-09 7:41:33 0 [Note] InnoDB: Creating shared tablespace for temporary tables
      2020-04-09 7:41:33 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
      2020-04-09 7:41:33 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
      2020-04-09 7:41:33 0 [Note] InnoDB: Waiting for purge to start
      2020-04-09 7:41:33 0 [Note] InnoDB: 10.4.12 started; log sequence number 31625812963; transaction id 308873
      2020-04-09 7:41:33 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
      2020-04-09 7:41:33 0 [Note] Server socket created on IP: '::'.
      2020-04-09 7:41:33 7 [Note] Event Scheduler: scheduler thread started with id 7
      2020-04-09 7:41:33 0 [Note] /usr/sbin/mysqld: ready for connections.

      Attachments

        Issue Links

          Activity

            danblack Daniel Black added a comment -

            tmpfs filesystems don't support creating a file with `O_TMPFILE`, at least in your kernel version. I see it frequently too.

            Ultimately the warning is informational only and has no impact apart from there may be residual files in /tmp if the server crashes.

            It would be good if the linux kernel eventually did support it on tmpfs.

            danblack Daniel Black added a comment - tmpfs filesystems don't support creating a file with `O_TMPFILE`, at least in your kernel version. I see it frequently too. Ultimately the warning is informational only and has no impact apart from there may be residual files in /tmp if the server crashes. It would be good if the linux kernel eventually did support it on tmpfs.
            vincent.lemoine@iwa-consult.nl V H Lemoine added a comment -

            ok, thx, pls close this issue

            vincent.lemoine@iwa-consult.nl V H Lemoine added a comment - ok, thx, pls close this issue
            danblack Daniel Black added a comment -

            The slightly longer version of what happens is when the failure to create a file with the `O_TMPFILE` flag happens, the fallback is to create a file and then immediately delete it (which happened for years, it was just quiet about it).

            https://github.com/MariaDB/server/blob/c7ab676/mysys/mf_tempfile.c#L133

            danblack Daniel Black added a comment - The slightly longer version of what happens is when the failure to create a file with the `O_TMPFILE` flag happens, the fallback is to create a file and then immediately delete it (which happened for years, it was just quiet about it). https://github.com/MariaDB/server/blob/c7ab676/mysys/mf_tempfile.c#L133
            danblack Daniel Black added a comment -

            I was wrong - I was using it incorrectly MDEV-26601.

            danblack Daniel Black added a comment - I was wrong - I was using it incorrectly MDEV-26601 .

            People

              Unassigned Unassigned
              vincent.lemoine@iwa-consult.nl V H Lemoine
              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.