Details
-
Bug
-
Status: Closed (View Workflow)
-
Blocker
-
Resolution: Fixed
-
10.4.10
-
Linux 4.19.98-gentoo x86_64 AMD EPYC 7451, XFS on software RAID1 of two NVMe drives
Description
Server has following configuration:
innodb_flush_method = O_DIRECT
|
More intensively it's used ("intensive" means 20-30 select queries in processlist, 1-2 insert queries updating multiple rows), more frequent following situation is:
2020-01-28 16:40:58 0 [ERROR] InnoDB: Operating system error number 22 in a file operation. |
2020-01-28 16:40:58 0 [ERROR] InnoDB: Error number 22 means 'Invalid argument' |
2020-01-28 16:40:58 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ |
2020-01-28 16:40:58 0 [ERROR] InnoDB: File ./user_167583/email.ibd: 'Linux aio' returned OS error 222. Cannot continue operation |
200128 16:40:58 [ERROR] mysqld got signal 6 ; |
This could be because you hit a bug. It is also possible that this binary |
or one of the libraries it was linked against is corrupt, improperly built,
|
or misconfigured. This error can also be caused by malfunctioning hardware.
|
and corresponding system message:
[Tue Jan 28 16:40:58 2020] mysqld[48573]: segfault at 0 ip 000055a53fc5a5a1 sp 00007e93a6eb1e60 error 6 in mysqld[55a53f426000+8ac000] |
[Tue Jan 28 16:40:58 2020] Code: c7 04 24 00 00 00 00 48 89 ea 4c 89 ee 44 89 f7 e8 14 cf 7c ff 49 89 c7 48 39 c5 0f 84 f8 00 00 00 e8 63 1d 00 00 41 8b 0c 24 <89> 08 85 c9 74 39 49 83 ff ff 0f 84 9f 00 00 00 f6 c3 06 75 2a 4d |
This happens once in several hours. However, this is an issue as node is a part of galera cluster and crash renders into snapshot transfer to failed node.
Changing configuration to
#innodb_flush_method = O_DIRECT
|
innodb_use_native_aio = 0 |
"solves" stability issue with setting flush method to default fsync() one.
Expected behavior would be stable mariadb operation with O_DIRECT.
Attachments
Issue Links
- relates to
-
-
- Closed
-