下面给出的是我得到的mysql错误日志。我们的应用程序每秒只能获得10-20个请求,但每隔半小时我就会在mysql日志中收到此错误,并且mysql会自动停止。Mysql服务器频繁关闭
2014-10-29 16:52:01 5114 InnoDB: Encountered a problem with file .\ib_logfile1
2014-10-29 16:52:01 5114 InnoDB: Disk is full. Try to clean the disk to free space.
2014-10-29 16:52:01 5114 InnoDB: Assertion failure in thread 20756 in file fil0fil.cc line 5475
InnoDB: Failing assertion: ret
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/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
2014-10-29 16:52:17 44652 [ERROR] C:/Program Files (x86)/MySQL/MySQL Server 5.6/bin\mysqld: Sort aborted: Error writing file 'C:\DOCUME~1\NETWOR~1\LOCALS~1\Temp\MY8E87.tmp' (Errcode: 28 - No space left on device)
2014-10-29 16:52:21 44652 [ERROR] C:/Program Files (x86)/MySQL/MySQL Server 5.6/bin\mysqld: Sort aborted: Error writing file 'C:\DOCUME~1\NETWOR~1\LOCALS~1\Temp\MY8E86.tmp' (Errcode: 28 - No space left on device)
正如你指定的,我去了并检查文件路径(正如你怀疑mysql清除了所有文件)。但我担心的是,由于文件路径位于C:驱动器,我的C驱动器有5 GB的可用空间,因此显示的原因是什么(错误代码:28 - 设备上没有剩余空间) – user1850594 2014-10-29 13:05:11
5GB可用空间临时文件在2014年并不是很多。你可以免费获得20或30GB的数据,看看它是否能够稳定你的系统? – 2014-10-29 17:10:53
正如您所建议的,我将temp文件夹变量TMP和TEMP更改为具有400GB可用空间的另一个驱动器,但问题仍然存在。有趣的是,即使在改变之后,日志仍然显示C:\ DOCUME〜1 \ NETWOR〜1 \ LOCALS〜1 \ Temp \。我交叉检查了用户和系统的其他环境变量,并确认没有声明其他临时变量。 – user1850594 2014-10-30 04:40:01