2017-10-21 12:46:50 140037039915584 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

2017-10-21 12:46:50 140037039915584 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-10-21 12:46:50 140037039915584 [Note] InnoDB: The InnoDB memory heap is disabled
2017-10-21 12:46:50 140037039915584 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-10-21 12:46:50 140037039915584 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2017-10-21 12:46:50 140037039915584 [Note] InnoDB: Compressed tables use zlib 1.2.8
2017-10-21 12:46:50 140037039915584 [Note] InnoDB: Using Linux native AIO
2017-10-21 12:46:50 140037039915584 [Note] InnoDB: Using generic crc32 instructions
2017-10-21 12:46:50 140037039915584 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2017-10-21 12:46:50 140037039915584 [Note] InnoDB: Completed initialization of buffer pool
2017-10-21 12:46:50 140037039915584 [Note] InnoDB: Highest supported file format is Barracuda.
2017-10-21 12:46:50 140037039915584 [Note] InnoDB: The log sequence number 439362948 in ibdata file do not match the log sequence number 507624716 in the ib_logfiles!
2017-10-21 12:46:50 140037039915584 [ERROR] InnoDB: Tried to read 16384 bytes at offset 0. Was only able to read 3019.
2017-10-21 12:46:50 7f5cea050240  InnoDB: Operating system error number 1 in a file operation.
InnoDB: Error number 1 means 'Operation not permitted'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
 InnoDB: Operation read to file /build/mariadb-10.1-5BEZAc/mariadb-10.1-10.1.26/storage/xtradb/os/os0file.cc and at line 3174
2017-10-21 12:46:50 140037039915584 [ERROR] InnoDB: File (unknown): 'read' returned OS error 201. Cannot continue operation
171021 12:46:50 [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.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

Server version: 10.1.26-MariaDB-0+deb9u1
key_buffer_size=16777216
read_buffer_size=131072
max_used_connections=0
max_threads=153
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 352445 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0x0 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x55a22077936e]
/usr/sbin/mysqld(handle_fatal_signal+0x3bd)[0x55a2202bea4d]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x110c0)[0x7f5ce9cc30c0]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcf)[0x7f5ce85bdfcf]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x7f5ce85bf3fa]
/usr/sbin/mysqld(+0x889f2c)[0x55a2205a5f2c]
/usr/sbin/mysqld(+0x88e12b)[0x55a2205aa12b]
/usr/sbin/mysqld(+0x9c7ff6)[0x55a2206e3ff6]
/usr/sbin/mysqld(+0x9d3139)[0x55a2206ef139]
/usr/sbin/mysqld(+0x9d4222)[0x55a2206f0222]
/usr/sbin/mysqld(+0x87c280)[0x55a220598280]
/usr/sbin/mysqld(+0x90ac0e)[0x55a220626c0e]
/usr/sbin/mysqld(+0x8214ef)[0x55a22053d4ef]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x66)[0x55a2202c0b86]
/usr/sbin/mysqld(+0x422e55)[0x55a22013ee55]
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0x7da)[0x55a22014048a]
/usr/sbin/mysqld(+0x37afa3)[0x55a220096fa3]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x1a0d)[0x55a22009a78d]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7f5ce85ab2b1]
/usr/sbin/mysqld(_start+0x2a)[0x55a22008ec4a]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
2017-10-21 12:46:56 140313975095872 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

2017-10-21 12:46:56 140313975095872 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-10-21 12:46:56 140313975095872 [Note] InnoDB: The InnoDB memory heap is disabled
2017-10-21 12:46:56 140313975095872 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-10-21 12:46:56 140313975095872 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2017-10-21 12:46:56 140313975095872 [Note] InnoDB: Compressed tables use zlib 1.2.8
2017-10-21 12:46:56 140313975095872 [Note] InnoDB: Using Linux native AIO
2017-10-21 12:46:56 140313975095872 [Note] InnoDB: Using generic crc32 instructions
2017-10-21 12:46:56 140313975095872 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2017-10-21 12:46:56 140313975095872 [Note] InnoDB: Completed initialization of buffer pool
2017-10-21 12:46:56 140313975095872 [Note] InnoDB: Highest supported file format is Barracuda.
2017-10-21 12:46:56 140313975095872 [Note] InnoDB: The log sequence number 439362948 in ibdata file do not match the log sequence number 507624716 in the ib_logfiles!
2017-10-21 12:46:56 140313975095872 [ERROR] InnoDB: Tried to read 16384 bytes at offset 0. Was only able to read 3019.
2017-10-21 12:46:56 7f9d64a48240  InnoDB: Operating system error number 1 in a file operation.
InnoDB: Error number 1 means 'Operation not permitted'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
 InnoDB: Operation read to file /build/mariadb-10.1-5BEZAc/mariadb-10.1-10.1.26/storage/xtradb/os/os0file.cc and at line 3174
2017-10-21 12:46:56 140313975095872 [ERROR] InnoDB: File (unknown): 'read' returned OS error 201. Cannot continue operation
171021 12:46:56 [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.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

Server version: 10.1.26-MariaDB-0+deb9u1
key_buffer_size=16777216
read_buffer_size=131072
max_used_connections=0
max_threads=153
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 352445 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0x0 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x561b268e136e]
/usr/sbin/mysqld(handle_fatal_signal+0x3bd)[0x561b26426a4d]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x110c0)[0x7f9d646bb0c0]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcf)[0x7f9d62fb5fcf]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x7f9d62fb73fa]
/usr/sbin/mysqld(+0x889f2c)[0x561b2670df2c]
/usr/sbin/mysqld(+0x88e12b)[0x561b2671212b]
/usr/sbin/mysqld(+0x9c7ff6)[0x561b2684bff6]
/usr/sbin/mysqld(+0x9d3139)[0x561b26857139]
/usr/sbin/mysqld(+0x9d4222)[0x561b26858222]
/usr/sbin/mysqld(+0x87c280)[0x561b26700280]
/usr/sbin/mysqld(+0x90ac0e)[0x561b2678ec0e]
/usr/sbin/mysqld(+0x8214ef)[0x561b266a54ef]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x66)[0x561b26428b86]
/usr/sbin/mysqld(+0x422e55)[0x561b262a6e55]
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0x7da)[0x561b262a848a]
/usr/sbin/mysqld(+0x37afa3)[0x561b261fefa3]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x1a0d)[0x561b2620278d]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7f9d62fa32b1]
/usr/sbin/mysqld(_start+0x2a)[0x561b261f6c4a]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.