求教军哥（已解决）
早上发现网站读取不到数据，打不开，排除了其他，发现数据库打不开，删除了bin文件还是打不开，也登不上phpmyadmin。Version: '5.5.48-log'socket: '/tmp/mysql.sock'port: 0Source distribution
1703262:56:46 Disk is full writing './mysql-bin.000003' (Errcode: 28). Waiting for someone to free space... (Expect up to 60 secs delay for server to continue after freeing disk space)
1703262:56:46 Retry in 60 secs. Message reprinted in 600 secs
1703263:06:46 Disk is full writing './mysql-bin.000003' (Errcode: 28). Waiting for someone to free space... (Expect up to 60 secs delay for server to continue after freeing disk space)
1703263:06:46 Retry in 60 secs. Message reprinted in 600 secs
1703263:16:46 Disk is full writing './mysql-bin.000003' (Errcode: 28). Waiting for someone to free space... (Expect up to 60 secs delay for server to continue after freeing disk space)
1703263:16:46 Retry in 60 secs. Message reprinted in 600 secs
1703263:26:46 Disk is full writing './mysql-bin.000003' (Errcode: 28). Waiting for someone to free space... (Expect up to 60 secs delay for server to continue after freeing disk space)
1703263:26:46 Retry in 60 secs. Message reprinted in 600 secs
1703263:36:46 Disk is full writing './mysql-bin.000003' (Errcode: 28). Waiting for someone to free space... (Expect up to 60 secs delay for server to continue after freeing disk space)
1703263:36:46 Retry in 60 secs. Message reprinted in 600 secs
1703263:46:46 Disk is full writing './mysql-bin.000003' (Errcode: 28). Waiting for someone to free space... (Expect up to 60 secs delay for server to continue after freeing disk space)
1703263:46:46 Retry in 60 secs. Message reprinted in 600 secs
1703263:56:46 Disk is full writing './mysql-bin.000003' (Errcode: 28). Waiting for someone to free space... (Expect up to 60 secs delay for server to continue after freeing disk space)
1703263:56:46 Retry in 60 secs. Message reprinted in 600 secs
1703264:50:00 Disk is full writing './mysql-bin.000003' (Errcode: 28). Waiting for someone to free space... (Expect up to 60 secs delay for server to continue after freeing disk space)
1703264:50:00 Retry in 60 secs. Message reprinted in 600 secs
1703265:00:00 Disk is full writing './mysql-bin.000003' (Errcode: 28). Waiting for someone to free space... (Expect up to 60 secs delay for server to continue after freeing disk space)
1703265:00:00 Retry in 60 secs. Message reprinted in 600 secs
1703265:10:00 Disk is full writing './mysql-bin.000003' (Errcode: 28). Waiting for someone to free space... (Expect up to 60 secs delay for server to continue after freeing disk space)
1703265:10:00 Retry in 60 secs. Message reprinted in 600 secs
1703265:20:00 Disk is full writing './mysql-bin.000003' (Errcode: 28). Waiting for someone to free space... (Expect up to 60 secs delay for server to continue after freeing disk space)
1703265:20:00 Retry in 60 secs. Message reprinted in 600 secs
1703265:30:00 Disk is full writing './mysql-bin.000003' (Errcode: 28). Waiting for someone to free space... (Expect up to 60 secs delay for server to continue after freeing disk space)
1703265:30:00 Retry in 60 secs. Message reprinted in 600 secs
1703265:40:00 Disk is full writing './mysql-bin.000003' (Errcode: 28). Waiting for someone to free space... (Expect up to 60 secs delay for server to170326 11:31:48 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/var
170326 11:31:48 /usr/local/mysql/bin/mysqld (mysqld 5.5.48-log) starting as process 1776 ...
170326 11:31:48 Plugin 'FEDERATED' is disabled.
170326 11:31:48 InnoDB: The InnoDB memory heap is disabled
170326 11:31:48 InnoDB: Mutexes and rw_locks use GCC atomic builtins
170326 11:31:48 InnoDB: Compressed tables use zlib 1.2.7
170326 11:31:48 InnoDB: Initializing buffer pool, size = 16.0M
170326 11:31:48 InnoDB: Completed initialization of buffer pool
170326 11:31:48 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
170326 11:31:48InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Last MySQL binlog file position 0 178003240, file name ./mysql-bin.000001
170326 11:31:48InnoDB: Waiting for the background threads to start
170326 11:31:49 InnoDB: 5.5.48 started; log sequence number 2510071
170326 11:31:49 Recovering after a crash using mysql-bin
170326 11:31:50 Error in Log_event::read_log_event(): 'read error', data_len: 610, event_type: 2
170326 11:31:50 Starting crash recovery...
170326 11:31:50 Crash recovery finished.
03:31:50 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.
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.
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=500
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 = 406149 Kbytes 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 0x40000
/usr/local/mysql/bin/mysqld(my_print_stacktrace+0x20)
/usr/local/mysql/bin/mysqld(handle_fatal_signal+0x359)
/usr/lib64/libpthread.so.0(+0xf100)
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.
170326 11:31:50 mysqld_safe mysqld from pid file /usr/local/mysql/var/vultr.guest.pid ended
170326 12:08:11 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/var
170326 12:08:11 /usr/local/mysql/bin/mysqld (mysqld 5.5.48-log) starting as process 3331 ...
170326 12:08:11 Plugin 'FEDERATED' is disabled.
170326 12:08:11 InnoDB: The InnoDB memory heap is disabled
170326 12:08:11 InnoDB: Mutexes and rw_locks use GCC atomic builtins
170326 12:08:11 InnoDB: Compressed tables use zlib 1.2.7
170326 12:08:11 InnoDB: Initializing buffer pool, size = 16.0M
170326 12:08:11 InnoDB: Completed initialization of buffer pool
170326 12:08:11 InnoDB: highest supported file format is Barracuda.
InnoDB: The user has set SRV_FORCE_NO_LOG_REDO on
InnoDB: Skipping log redo
170326 12:08:11InnoDB: Waiting for the background threads to start
170326 12:08:12 InnoDB: 5.5.48 started; log sequence number 0
170326 12:08:12 InnoDB: !!! innodb_force_recovery is set to 6 !!!
/usr/local/mysql/bin/mysqld: File './mysql-bin.000003' not found (Errcode: 2)
170326 12:08:12 Failed to open log (file './mysql-bin.000003', errno 2)
170326 12:08:12 Could not open log file
170326 12:08:12 Can't init tc log
170326 12:08:12 Aborting
170326 12:08:12InnoDB: Starting shutdown...
170326 12:08:12InnoDB: Shutdown completed; log sequence number 8204
170326 12:08:12 /usr/local/mysql/bin/mysqld: Shutdown complete
170326 12:08:12 mysqld_safe mysqld from pid file /usr/local/mysql/var/vultr.guest.pid ended
170326 12:16:24 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/var
170326 12:16:24 /usr/local/mysql/bin/mysqld (mysqld 5.5.48-log) starting as process 4041 ...
170326 12:16:24 Plugin 'FEDERATED' is disabled.
170326 12:16:24 InnoDB: The InnoDB memory heap is disabled
170326 12:16:24 InnoDB: Mutexes and rw_locks use GCC atomic builtins
170326 12:16:24 InnoDB: Compressed tables use zlib 1.2.7
170326 12:16:24 InnoDB: Initializing buffer pool, size = 16.0M
170326 12:16:24 InnoDB: Completed initialization of buffer pool
170326 12:16:24 InnoDB: highest supported file format is Barracuda.
170326 12:16:24InnoDB: Error: page 7 log sequence number 2503350
InnoDB: is in the future! Current system log sequence number 8204.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
170326 12:16:24InnoDB: Waiting for the background threads to start
170326 12:16:25 InnoDB: 5.5.48 started; log sequence number 8204
/usr/local/mysql/bin/mysqld: File './mysql-bin.000003' not found (Errcode: 2)
170326 12:16:25 Failed to open log (file './mysql-bin.000003', errno 2)
170326 12:16:25 Could not open log file
170326 12:16:25 Can't init tc log
170326 12:16:25 Aborting
170326 12:16:25InnoDB: Starting shutdown...
170326 12:16:25InnoDB: Shutdown completed; log sequence number 8204
170326 12:16:25 /usr/local/mysql/bin/mysqld: Shutdown complete
170326 12:16:25 mysqld_safe mysqld from pid file /usr/local/mysql/var/vultr.guest.pid ended
[ 本帖最后由 yancy 于 2017-3-26 12:43 编辑 ] 第一行占的比较多，
Filesystem SizeUsed Avail Use% Mounted on
/dev/vda1 20G 17G2.6G87% /
devtmpfs 488M 0488M 0% /dev
tmpfs 497M 0497M 0% /dev/shm
tmpfs 497M 13M484M 3% /run
tmpfs 497M 0497M 0% /sys/fs/cgroup
tmpfs 100M 0100M 0% /run/user/0 还要删掉bin.index，删除完就能重启数据库
页:
[1]