function=io_uring_setup error=13 (Permission denied)

[lejeczek]

Hi guys.

Anybody has ever seen such a strange "misbehaviour" where volumes would not mount at OS boot?
I find in logs for a given volume mount:

[2026-08-08 14:53:04.232977 +0000] E [gf-io-uring.c:404:gf_io_uring_setup] 0-io: [MSGID:101240] Function call failed <{function=io_uring_setup()}, {error=13 (Permission denied)}>

Later, as soon as I can log into the system, I can mount all volumes just fine.
None of my volumes use storage.linux-io_uring

I'm on 11.2 version and on Centos 10 and I use systemd mounts to mount volumes.

many thanks L.

[lejeczek]

Just to share my finding briefly - this is at least in part(s) due to SELinux - building custom SE modules somewhat fixes some of these errors yet my vols still do not mount at boot-time.