[MDEV-22202] mysqld: O_TMPFILE is not supported on /tmp (disabling future attempts) Created: 2020-04-09  Updated: 2021-09-14  Resolved: 2020-04-09

Status: Closed
Project: MariaDB Server
Component/s: Configuration
Affects Version/s: 10.4.12
Fix Version/s: N/A

Type: Bug Priority: Minor
Reporter: V H Lemoine Assignee: Unassigned
Resolution: Not a Bug Votes: 0
Labels: None
Environment:

UBUNTU 18.04 / Linux


Issue Links:
Relates
relates to MDEV-23846 O_TMPFILE error in mysqlbinlog stream... Closed

 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.



 Comments   
Comment by Daniel Black [ 2020-04-09 ]

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.

Comment by V H Lemoine [ 2020-04-09 ]

ok, thx, pls close this issue

Comment by Daniel Black [ 2020-04-09 ]

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

Comment by Daniel Black [ 2021-09-14 ]

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

Generated at Thu Feb 08 09:12:58 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.