On Tue, Feb 22, 2022 at 10:42 PM Filipe Manana <fdmanana@xxxxxxxxxx> wrote: > I gave it a try, but it fails setting up io_uring: > > 2022-02-22 11:27:13 0 [Note] mysqld: O_TMPFILE is not supported on /tmp (disabling future attempts) > 2022-02-22 11:27:13 0 [Warning] mysqld: io_uring_queue_init() failed with errno 1 > 2022-02-22 11:27:13 0 [Warning] InnoDB: liburing disabled: falling back to innodb_use_native_aio=OFF > 2022-02-22 11:27:13 0 [Note] InnoDB: Initializing buffer pool, total size = 134217728, chunk size = 134217728 > 2022-02-22 11:27:13 0 [Note] InnoDB: Completed initialization of buffer pool > > So that's why it doesn't fail here, as it fallbacks to no aio mode. error 1 is EPERM. Seems it needs --privileged on the container startup as a podman argument (before the image name). Sorry I missed that > Any idea why it's failing to setup io_uring? > > I have the liburing2 and liburing-dev packages installed on debian, and > tried with a 5.17-rc4 kernel. Taking https://packages.debian.org/bookworm/mariadb-server-core-10.6 package: mariadb-install-db --no-defaults --datadir=/empty/btrfs/path --innodb-use-native-aio=0 mariadbd --no-defaults --datadir=/empty/btrfs/path --innodb-use-native-aio=1 should achieve the same thing.
