>> Всем привет!
>> На Windows 10 build 1809 в Hyper-V стоит ubuntu 18.04. C некоторых
>> пор на /dev/sda2 стали появляться ошибки чтения, как на сбойном физическом
>> диске (не думал, что такое возможно) fsck, запущенная в безопасном режиме
>> вроде бы что-то правит, но после загрузки в нормальном режиме все-равно
>> показывает ошибки. В результате сбоит БД в mysql и он периодически
>> падает. Что можно сделать?
> какая файловая система в Ubuntu? а сам диск физический целый? может Windows
> тоже ругается на диск.ext4. Windows не ругается.
В логе mysql 8 (обновлен с 5.7) вот так.
2019-02-12T19:08:48.227501Z 0 [Warning] [MY-010915] [Server] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
2019-02-12T19:08:48.229451Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.15) starting as process 323
2019-02-12T19:08:52.804786Z 0 [System] [MY-010229] [Server] Starting crash recovery...
2019-02-12T19:08:52.821444Z 0 [System] [MY-010232] [Server] Crash recovery finished.
2019-02-12T19:08:53.375078Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2019-02-12T19:08:53.518043Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: '8.0.15' socket: '/var/run/mysqld/mysqld.sock' port: 3306 MySQL Community Server - GPL.
2019-02-12T19:08:53.550090Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Socket: '/var/run/mysqld/mysqlx.sock' bind-address: '0.0.0.0' port: 33060
2019-02-12T19:09:04.846450Z 0 [Warning] [MY-012638] [InnoDB] Retry attempts for reading partial data failed.
2019-02-12T19:09:04.846530Z 0 [ERROR] [MY-012642] [InnoDB] Tried to read 16384 bytes at offset 20496384, but was only able to read 0
2019-02-12T19:09:04.846542Z 0 [ERROR] [MY-012592] [InnoDB] Operating system error number 5 in a file operation.
2019-02-12T19:09:04.846560Z 0 [ERROR] [MY-012596] [InnoDB] Error number 5 means 'Input/output error'
2019-02-12T19:09:04.846574Z 0 [ERROR] [MY-012646] [InnoDB] File (unknown): 'read' returned OS error 105. Cannot continue operation
2019-02-12T19:09:04.846583Z 0 [ERROR] [MY-012981] [InnoDB] Cannot continue operation.
2019-02-12T19:09:04.948186Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: log0buf.cc:700:srv_shutdown_state <= SRV_SHUTDOWN_FLUSH_PHASE thread 140229207750400
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recove...
InnoDB: about forcing recovery.
19:09:04 UTC - 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.
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.
key_buffer_size=16777216
read_buffer_size=131072
max_used_connections=1
max_threads=500
thread_count=1
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 213938 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x7f886c0e4700
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 = 7f89a81d6c80 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace(unsigned char*, unsigned long)+0x3d) [0x55e148bbe57d]
/usr/sbin/mysqld(handle_fatal_signal+0x423) [0x55e147d4e7c3]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x34c7412890) [0x7f89bc1cd890]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7) [0x7f89ba5cae97]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x141) [0x7f89ba5cc801]
/usr/sbin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x2d5) [0x55e148e742c5]
/usr/sbin/mysqld(log_buffer_reserve(log_t&, unsigned long)+0x240) [0x55e148d152f0]
/usr/sbin/mysqld(mtr_t::Command::execute()+0x59) [0x55e148d4c8e9]
/usr/sbin/mysqld(mtr_t::commit()+0x89) [0x55e148d4cb39]
/usr/sbin/mysqld(+0x1fa98e5) [0x55e148e3d8e5]
/usr/sbin/mysqld(+0x1fa9fef) [0x55e148e3dfef]
/usr/sbin/mysqld(trx_purge(unsigned long, unsigned long, bool)+0x3d5) [0x55e148e44375]
/usr/sbin/mysqld(srv_purge_coordinator_thread()+0x819) [0x55e148e0e879]
/usr/sbin/mysqld(std::thread::_State_impl<std::thread::_Invoker<std::tuple<Runnable, void (*)()> > >::_M_run()+0x63) [0x55e148c80883]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x311b0bd57f) [0x7f89baff057f]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x34c74076db) [0x7f89bc1c26db]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x3f) [0x7f89ba6ad88f]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): is an invalid pointer
Connection ID (thread ID): 0
Status: NOT_KILLED
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.
