1. First fulldisk entries including an automatic mysql restart:

2017-06-02T10:30:52+02:00 databaseserver mysqld[13409]: InnoDB: posix_fallocate(): Failed to preallocate data for file ./XYZ/ZYX.ibd, desired size 4194304 byt
es. Operating system error number 28. Check that the disk is not full or a disk quota exceeded. Make sure the file system supports this function. Some operating system error numbers are des
cribed at http://dev.mysql.com/doc/refman/5.7/en/ operating-system-error-codes.html
2017-06-02T10:30:52+02:00 databaseserver mysqld[13409]: InnoDB: 1048576 bytes should have been written. Only 233472 bytes written. Retrying for the remaining bytes.
2017-06-02T10:30:52+02:00 databaseserver mysqld[13409]: InnoDB: Retry attempts for writing partial data failed.
2017-06-02T10:30:52+02:00 databaseserver mysqld[13409]: InnoDB: Write to file ./XYZ/ZYX.ibdfailed at offset 17869832192, 1048576 bytes should have been writte
n, only 233472 were written. Operating system error number 28. Check that your OS and file system support files of this size. Check also that the disk is not full or a disk quota exceeded.
2017-06-02T10:30:52+02:00 databaseserver mysqld[13409]: InnoDB: Error number 28 means 'No space left on device'
2017-06-02T10:30:52+02:00 databaseserver mysqld[13409]: InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2017-06-02T10:30:52+02:00 databaseserver mysqld[13409]: InnoDB: Error while writing 4194304 zeroes to ./XYZ/ZYX.ibd starting at offset 17867735040
2017-06-02T10:30:52+02:00 databaseserver mysqld[13409]: /usr/sbin/mysqld: The table 'Reiseruecktrittsversicherung_tmp' is full
2017-06-02T10:30:56+02:00 databaseserver mysqld[13409]: InnoDB: posix_fallocate(): Failed to preallocate data for file ./XYZ/ZYX.ibd, desired size 16384 bytes. Operating system
error number 28. Check that the disk is not full or a disk quota exceeded. Make sure the file system supports this function. Some operating system error numbers are described at http://dev.
mysql.com/doc/refman/5.7/en/ operating-system-error-codes.html
2017-06-02T10:30:56+02:00 databaseserver mysqld[13409]: InnoDB: Retry attempts for writing partial data failed.
2017-06-02T10:30:56+02:00 databaseserver mysqld[13409]: InnoDB: Error while writing 16384 zeroes to ./XYZ/ZYX.ibd starting at offset 655360

2017-06-02T10:30:57+02:00 databaseserver mysqld[29201]: /usr/sbin/mysqld (mysqld 5.7.17-11) starting as process 29201 ...
2017-06-02T10:30:57+02:00 databaseserver mysqld[29201]: InnoDB: Using innodb_file_format is deprecated and the parameter may be removed in future releases. See http://dev.mysql.com/doc/refman/5.7/en/innodb-file-format.html
2017-06-02T10:30:57+02:00 databaseserver mysqld[29201]: InnoDB: PUNCH HOLE support available
2017-06-02T10:30:57+02:00 databaseserver mysqld[29201]: InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-06-02T10:30:57+02:00 databaseserver mysqld[29201]: InnoDB: Uses event mutexes
2017-06-02T10:30:57+02:00 databaseserver mysqld[29201]: InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2017-06-02T10:30:57+02:00 databaseserver mysqld[29201]: InnoDB: Compressed tables use zlib 1.2.8
2017-06-02T10:30:57+02:00 databaseserver mysqld[29201]: InnoDB: Using Linux native AIO
2017-06-02T10:30:57+02:00 databaseserver mysqld[29201]: InnoDB: Number of pools: 1
2017-06-02T10:30:57+02:00 databaseserver mysqld[29201]: InnoDB: Using CPU crc32 instructions
2017-06-02T10:30:57+02:00 databaseserver mysqld[29201]: InnoDB: Initializing buffer pool, total size = 15G, instances = 8, chunk size = 128M
2017-06-02T10:30:57+02:00 databaseserver mysqld[29201]: InnoDB: Completed initialization of buffer pool
2017-06-02T10:30:57+02:00 databaseserver mysqld[29201]: InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2017-06-02T10:30:57+02:00 databaseserver mysqld[29201]: InnoDB: Recovering partial pages from the parallel doublewrite buffer at /var/lib/mysql/xb_doublewrite
2017-06-02T10:30:57+02:00 databaseserver mysqld[29201]: InnoDB: Highest supported file format is Barracuda.
2017-06-02T10:30:58+02:00 databaseserver mysqld[29201]: InnoDB: Log scan progressed past the checkpoint lsn 128486080987
2017-06-02T10:30:58+02:00 databaseserver mysqld[29201]: InnoDB: Doing recovery: scanned up to log sequence number 128491323392
2017-06-02T10:30:58+02:00 databaseserver mysqld[29201]: InnoDB: Doing recovery: scanned up to log sequence number 128496566272
2017-06-02T10:30:58+02:00 databaseserver mysqld[29201]: InnoDB: Doing recovery: scanned up to log sequence number 128501809152
2017-06-02T10:30:58+02:00 databaseserver mysqld[29201]: InnoDB: Doing recovery: scanned up to log sequence number 128507052032
2017-06-02T10:30:58+02:00 databaseserver mysqld[29201]: InnoDB: Doing recovery: scanned up to log sequence number 128512294912
2017-06-02T10:30:58+02:00 databaseserver mysqld[29201]: InnoDB: Doing recovery: scanned up to log sequence number 128517537792
2017-06-02T10:30:58+02:00 databaseserver mysqld[29201]: InnoDB: Doing recovery: scanned up to log sequence number 128522780672
2017-06-02T10:30:58+02:00 databaseserver mysqld[29201]: InnoDB: Doing recovery: scanned up to log sequence number 128490209280
2017-06-02T10:30:58+02:00 databaseserver mysqld[29201]: InnoDB: Doing recovery: scanned up to log sequence number 128495452160
2017-06-02T10:30:58+02:00 databaseserver mysqld[29201]: InnoDB: Doing recovery: scanned up to log sequence number 128500695040
2017-06-02T10:30:58+02:00 databaseserver mysqld[29201]: InnoDB: Doing recovery: scanned up to log sequence number 128505937920
2017-06-02T10:30:58+02:00 databaseserver mysqld[29201]: InnoDB: Doing recovery: scanned up to log sequence number 128511180800
2017-06-02T10:30:58+02:00 databaseserver mysqld[29201]: InnoDB: Doing recovery: scanned up to log sequence number 128516423680
2017-06-02T10:30:58+02:00 databaseserver mysqld[29201]: InnoDB: Doing recovery: scanned up to log sequence number 128521666560
2017-06-02T10:30:58+02:00 databaseserver mysqld[29201]: InnoDB: Doing recovery: scanned up to log sequence number 128523952620
2017-06-02T10:30:58+02:00 databaseserver mysqld[29201]: InnoDB: Database was not shutdown normally!
2017-06-02T10:30:58+02:00 databaseserver mysqld[29201]: InnoDB: Starting crash recovery.
2017-06-02T10:30:58+02:00 databaseserver mysqld[29201]: InnoDB: Recovered page [page id: space=56565, page number=38] from the doublewrite buffer.
2017-06-02T10:30:58+02:00 databaseserver mysqld[29201]: InnoDB: Page 1719 in the doublewrite buffer is not within space bounds: page [page id: space=56566, page number=20]
2017-06-02T10:30:58+02:00 databaseserver mysqld[29201]: InnoDB: Created parallel doublewrite buffer at /var/lib/mysql/xb_doublewrite, size 31457280 bytes
2017-06-02T10:30:58+02:00 databaseserver mysqld[29201]: InnoDB: Starting an apply batch of log records to the database...
2017-06-02T10:31:00+02:00 databaseserver mysqld[29201]: InnoDB: Apply batch completed
2017-06-02T10:31:33+02:00 databaseserver mysqld[29201]: InnoDB: Removed temporary tablespace data file: "ibtmp1"
2017-06-02T10:31:33+02:00 databaseserver mysqld[29201]: InnoDB: Creating shared tablespace for temporary tables
2017-06-02T10:31:33+02:00 databaseserver mysqld[29201]: InnoDB: Setting file '/var/lib/mysql/ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2017-06-02T10:31:33+02:00 databaseserver mysqld[29201]: InnoDB: File '/var/lib/mysql/ibtmp1' size is now 12 MB.
2017-06-02T10:31:33+02:00 databaseserver mysqld[29201]: InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2017-06-02T10:31:33+02:00 databaseserver mysqld[29201]: InnoDB: 32 non-redo rollback segment(s) are active.
2017-06-02T10:31:33+02:00 databaseserver mysqld[29201]: InnoDB: page_cleaner: 1000ms intended loop took 36070ms. The settings might not be optimal. (flushed=0, during the time.)
2017-06-02T10:31:33+02:00 databaseserver mysqld[29201]: InnoDB: Waiting for purge to start
2017-06-02T10:31:34+02:00 databaseserver mysqld[29201]: InnoDB: Percona XtraDB (http://www.percona.com) 5.7.17-11 started; log sequence number 128523952620
2017-06-02T10:31:34+02:00 databaseserver mysqld[29201]: InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2017-06-02T10:31:34+02:00 databaseserver mysqld[29201]: Plugin 'FEDERATED' is disabled.
2017-06-02T10:31:34+02:00 databaseserver mysqld[29201]: InnoDB: Buffer pool(s) load completed at 170602 10:31:34
2017-06-02T10:31:34+02:00 databaseserver mysqld[29201]: Found ca.pem, server-cert.pem and server-key.pem in data directory. Trying to enable SSL support using them.
2017-06-02T10:31:34+02:00 databaseserver mysqld[29201]: Skipping generation of SSL certificates as certificate files are present in data directory.
2017-06-02T10:31:34+02:00 databaseserver mysqld[29201]: CA certificate ca.pem is self signed.
2017-06-02T10:31:34+02:00 databaseserver mysqld[29201]: Skipping generation of RSA key pair as key files are present in data directory.
2017-06-02T10:31:34+02:00 databaseserver mysqld[29201]: Server hostname (bind-address): '*'; port: 3306
2017-06-02T10:31:34+02:00 databaseserver mysqld[29201]: IPv6 is available.
2017-06-02T10:31:34+02:00 databaseserver mysqld[29201]:   - '::' resolves to '::';
2017-06-02T10:31:34+02:00 databaseserver mysqld[29201]: Server socket created on IP: '::'.
2017-06-02T10:31:34+02:00 databaseserver mysqld[29201]: /usr/sbin/mysqld: Table './mysql/user' is marked as crashed and should be repaired
2017-06-02T10:31:34+02:00 databaseserver mysqld[29201]: Checking table:   './mysql/user'
2017-06-02T10:31:34+02:00 databaseserver mysqld[29201]: 1 client is using or hasn't closed the table properly
2017-06-02T10:31:34+02:00 databaseserver mysqld[29201]: /usr/sbin/mysqld: Table './mysql/db' is marked as crashed and should be repaired
2017-06-02T10:31:34+02:00 databaseserver mysqld[29201]: Checking table:   './mysql/db'
2017-06-02T10:31:34+02:00 databaseserver mysqld[29201]: 1 client is using or hasn't closed the table properly
2017-06-02T10:31:34+02:00 databaseserver mysqld[29201]: 'user' entry 'root@localhost' ignored in --skip-name-resolve mode.
2017-06-02T10:31:34+02:00 databaseserver mysqld[29201]: 'user' entry 'mysql.sys@localhost' ignored in --skip-name-resolve mode.
2017-06-02T10:31:34+02:00 databaseserver mysqld[29201]: 'db' entry 'sys mysql.sys@localhost' ignored in --skip-name-resolve mode.
2017-06-02T10:31:34+02:00 databaseserver mysqld[29201]: 'proxies_priv' entry '@ root@localhost' ignored in --skip-name-resolve mode.
2017-06-02T10:31:34+02:00 databaseserver mysqld[29201]: 'tables_priv' entry 'sys_config mysql.sys@localhost' ignored in --skip-name-resolve mode.
2017-06-02T10:31:34+02:00 databaseserver mysqld[29201]: Event Scheduler: Loaded 0 events
2017-06-02T10:31:34+02:00 databaseserver mysqld[29201]: Executing 'SELECT * FROM INFORMATION_SCHEMA.TABLES;' to get a list of tables using the deprecated partition engine. You may use the startup option '--disable-partition-engine-check' to skip this check.
2017-06-02T10:31:34+02:00 databaseserver mysqld[29201]: Beginning of list of non-natively partitioned tables
2017-06-02T10:31:51+02:00 databaseserver mysqld[29201]: End of list of non-natively partitioned tables
2017-06-02T10:31:51+02:00 databaseserver mysqld[29201]: /usr/sbin/mysqld: ready for connections.
2017-06-02T10:31:51+02:00 databaseserver mysqld[29201]: /usr/sbin/mysqld: Table './XYZ/wp_options' is marked as crashed and should be repaired
2017-06-02T10:31:51+02:00 databaseserver mysqld[29201]: /usr/sbin/mysqld: Table './XYZ/wp_options' is marked as crashed and should be repaired
2017-06-02T10:31:51+02:00 databaseserver mysqld[29201]: /usr/sbin/mysqld: Table './XYZ/wpms_options' is marked as crashed and should be repaired
2017-06-02T10:31:51+02:00 databaseserver mysqld[29201]: /usr/sbin/mysqld: Table './XYZ/wp_options' is marked as crashed and should be repaired
2017-06-02T10:31:51+02:00 databaseserver mysqld[29201]: /usr/sbin/mysqld: Table './XYZ/wp_options' is marked as crashed and should be repaired
2017-06-02T10:31:51+02:00 databaseserver mysqld[29201]: Checking table:   './XYZ/wp_options'
2017-06-02T10:31:51+02:00 databaseserver mysqld[29201]: Checking table:   './XYZ/wpms_options'
2017-06-02T10:31:51+02:00 databaseserver mysqld[29201]: Checking table:   './XYZ/wp_options'
2017-06-02T10:31:51+02:00 databaseserver mysqld[29201]: Checking table:   './XYZ/wp_options'
2017-06-02T10:31:51+02:00 databaseserver mysqld[29201]: /usr/sbin/mysqld: Table './XYZ/sys_registry' is marked as crashed and should be repaired
2017-06-02T10:31:51+02:00 databaseserver mysqld[29201]: /usr/sbin/mysqld: Table './XYZ/sys_registry' is marked as crashed and should be repaired
2017-06-02T10:31:51+02:00 databaseserver mysqld[29201]: Checking table:   './XYZ/sys_registry'
2017-06-02T10:31:51+02:00 databaseserver mysqld[29201]: /usr/sbin/mysqld: Table './XYZ/wp_posts' is marked as crashed and should be repaired
2017-06-02T10:31:51+02:00 databaseserver mysqld[29201]: Checking table:   './XYZ/wp_posts'
2017-06-02T10:31:51+02:00 databaseserver mysqld[29201]: InnoDB: 16384 bytes should have been written. Only 12288 bytes written. Retrying for the remaining bytes.
2017-06-02T10:31:51+02:00 databaseserver mysqld[29201]: InnoDB: Retry attempts for writing partial data failed.
2017-06-02T10:31:51+02:00 databaseserver mysqld[29201]: InnoDB: Write to file /var/lib/mysql/ib_25589_492862_trunc.logfailed at offset 0, 16384 bytes should have been written, only 12288 were written. Operating system error number 28. Check that your OS and file system support files of this size. Check also that the disk is not full or a disk quota exceeded.
2017-06-02T10:31:51+02:00 databaseserver mysqld[29201]: InnoDB: Error number 28 means 'No space left on device'
2017-06-02T10:31:51+02:00 databaseserver mysqld[29201]: InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html

2. A whole lot of fulldisk errors leading up to a fatal error:

[...]
2017-06-02T10:35:16+02:00 databaseserver mysqld[29201]: InnoDB: Retry attempts for writing partial data failed.
2017-06-02T10:35:16+02:00 databaseserver mysqld[29201]: InnoDB: Error while writing 20480 zeroes to ./XYZ/ZYX.ibd starting at offset 126976
2017-06-02T10:35:16+02:00 databaseserver mysqld[29201]: InnoDB: posix_fallocate(): Failed to preallocate data for file ./XYZ/ZYX.ibd, desired size 32768 bytes. Operating
 system error number 28. Check that the disk is not full or a disk quota exceeded. Make sure the file system supports this function. Some operating system error numbers are described at htt
p://dev.mysql.com/doc/refman/5.7/en/ operating-system-error-codes.html
2017-06-02T10:35:16+02:00 databaseserver mysqld[29201]: InnoDB: Retry attempts for writing partial data failed.
2017-06-02T10:35:16+02:00 databaseserver mysqld[29201]: InnoDB: Error while writing 32768 zeroes to ./XYZ/ZYX.ibd starting at offset 180224
2017-06-02T10:35:16+02:00 databaseserver mysqld[29201]: InnoDB: posix_fallocate(): Failed to preallocate data for file ./XYZ/ZYX.ibd, desired size 20480 bytes. Operating syste
m error number 28. Check that the disk is not full or a disk quota exceeded. Make sure the file system supports this function. Some operating system error numbers are described at http://de
v.mysql.com/doc/refman/5.7/en/ operating-system-error-codes.html
2017-06-02T10:35:16+02:00 databaseserver mysqld[29201]: InnoDB: Retry attempts for writing partial data failed.
2017-06-02T10:35:16+02:00 databaseserver mysqld[29201]: InnoDB: Error while writing 20480 zeroes to ./XYZ/ZYX.ibd starting at offset 126976
2017-06-02T10:35:16+02:00 databaseserver mysqld[29201]: [FATAL] InnoDB: Out of tablespace during rollback. Consider increasing your tablespace.

3. Starting percona now results in a segfault crash (careful: Timestamps are +00 now, whereas above are +02):

root@databaseserver:/var/lib/mysql > /usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql --plugin-dir=/usr/lib/mysql/plugin --open-files-limit=65535 --pid-file=/var/run/mysqld/mysqld.pid --socket=/var/run/mysqld/mysqld.sock --port=3306 --log-syslog=0 
2017-06-02T09:08:29.789779Z 0 [Warning] options --log-slow-admin-statements, --log-queries-not-using-indexes and --log-slow-slave-statements have no effect if --slow-query-log is not set
2017-06-02T09:08:29.789836Z 0 [Warning] 'NO_AUTO_CREATE_USER' sql mode was not set.
2017-06-02T09:08:29.791141Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.17-11) starting as process 17352 ...
2017-06-02T09:08:29.805332Z 0 [Warning] InnoDB: Using innodb_file_format is deprecated and the parameter may be removed in future releases. See http://dev.mysql.com/doc/refman/5.7/en/innodb-file-format.html
2017-06-02T09:08:29.805472Z 0 [Note] InnoDB: PUNCH HOLE support available
2017-06-02T09:08:29.805506Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-06-02T09:08:29.805533Z 0 [Note] InnoDB: Uses event mutexes
2017-06-02T09:08:29.805560Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2017-06-02T09:08:29.805587Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.8
2017-06-02T09:08:29.805615Z 0 [Note] InnoDB: Using Linux native AIO
2017-06-02T09:08:29.805893Z 0 [Note] InnoDB: Number of pools: 1
2017-06-02T09:08:29.806028Z 0 [Note] InnoDB: Using CPU crc32 instructions
2017-06-02T09:08:29.807278Z 0 [Note] InnoDB: Initializing buffer pool, total size = 15G, instances = 8, chunk size = 128M
2017-06-02T09:08:30.156376Z 0 [Note] InnoDB: Completed initialization of buffer pool
2017-06-02T09:08:30.244706Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2017-06-02T09:08:30.256638Z 0 [Note] InnoDB: Recovering partial pages from the parallel doublewrite buffer at /var/lib/mysql/xb_doublewrite
2017-06-02T09:08:30.292604Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2017-06-02T09:08:30.353287Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 128511049681
2017-06-02T09:08:30.368590Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 128516292096
2017-06-02T09:08:30.383727Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 128521534976
2017-06-02T09:08:30.414418Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 128526777856
2017-06-02T09:08:30.492101Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 128513867264
2017-06-02T09:08:30.510786Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 128519110144
2017-06-02T09:08:30.532926Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 128524353024
2017-06-02T09:08:30.555551Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 128529595904
2017-06-02T09:08:30.563639Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 128531338136
2017-06-02T09:08:30.563746Z 0 [Note] InnoDB: Database was not shutdown normally!
2017-06-02T09:08:30.563784Z 0 [Note] InnoDB: Starting crash recovery.
2017-06-02T09:08:30.622790Z 0 [Note] InnoDB: Created parallel doublewrite buffer at /var/lib/mysql/xb_doublewrite, size 31457280 bytes
2017-06-02T09:08:30.649020Z 0 [Note] InnoDB: 1 transaction(s) which must be rolled back or cleaned up in total 1 row operations to undo
2017-06-02T09:08:30.649115Z 0 [Note] InnoDB: Trx id counter is 68368640
2017-06-02T09:08:30.656674Z 0 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 09:08:31 UTC - mysqld got signal 11 ;
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.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.
Please help us make Percona Server better by reporting any
bugs at http://bugs.percona.com/

key_buffer_size=268435456
read_buffer_size=2097152
max_used_connections=0
max_threads=251
thread_count=0
connection_count=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 841679 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 = 0 thread_stack 0x80000
/usr/sbin/mysqld(my_print_stacktrace+0x3b)[0xe8e87b]
/usr/sbin/mysqld(handle_fatal_signal+0x489)[0x776159]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x11390)[0x7f32daf44390]
/usr/sbin/mysqld(_Z23page_cur_insert_rec_lowPhP12dict_index_tPKhPmP5mtr_t+0x370)[0x101d4c0]
/usr/sbin/mysqld(_Z25page_cur_parse_insert_recmPKhS0_P11buf_block_tP12dict_index_tP5mtr_t+0x680)[0x101f1a0]
/usr/sbin/mysqld[0xff650c]
79 /usr/sbin/mysqld(_Z22recv_recover_page_funcmP11buf_block_t+0x9dd)[0xff8ddd]
/usr/sbin/mysqld(_Z20buf_page_io_completeP10buf_page_tb+0x3e2)[0x116ea12]
/usr/sbin/mysqld(_Z12fil_aio_waitm+0x11f)[0x11ea0ff]
/usr/sbin/mysqld(io_handler_thread+0x108)[0x10ce108]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x76ba)[0x7f32daf3a6ba]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f32da3cf82d]
You may download the Percona Server operations manual by visiting
http://www.percona.com/software/percona-server/. You may find information
in the manual which will help you identify the cause of the crash.