On Tuesday, September 25, 2018 at 11:48 Kenneth Penza ([email protected]) wrote: > Startup messages: > > Sep 25 10:40:53 srv1 mysqld: 2018-09-25 10:40:52 0 [Note] InnoDB: Opened 8 > undo tablespaces > Sep 25 10:40:53 srv1 mysqld: 2018-09-25 10:40:53 0 [Warning] InnoDB: Failed > to set memory to DODUMP: Invalid argument ptr 0x2aaac5400000 size 2097152 > Sep 25 10:40:53 srv1 mysqld: 2018-09-25 10:40:53 0 [Note] InnoDB: 128 out of > 128 rollback segments in 8 undo tablespaces are active. > > Shutdown messages: > > Sep 25 10:41:18 srv1 mysqld: 2018-09-25 10:41:18 0 [Note] InnoDB: Buffer > pool(s) dump completed at 180925 10:41:18 > Sep 25 10:41:19 srv1 mysqld: 2018-09-25 10:41:19 0 [Warning] InnoDB: Failed > to set memory to DODUMP: Invalid argument ptr 0x2aaac3400000 size 33554432 > Sep 25 10:41:19 srv1 mysqld: 2018-09-25 10:41:19 0 [Note] InnoDB: Shutdown > completed; log sequence number 1522725; transaction id 22 > > Do you have ideas on what is causing "InnoDB: Failed to set memory to DODUMP: > Invalid argument ptr .. " warning?
Thanks to your report, Daniel Black (the author of a contribution that excludes large InnoDB buffers from core dumps) found out that it is a bug in the Linux kernel. His fix will be in the 4.19 kernel, and it was also included in a backport queue for the maintenance updates of older kernels: https://lwn.net/Articles/767784/ https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/commit/?id=c386d043e8e7718b218731b2868453335245ceeb For future reference, I have updated https://jira.mariadb.org/browse/MDEV-10814 with this information. -- Marko Mäkelä, Lead Developer InnoDB MariaDB Corporation _______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
