MySQL ERROR 1878 Workaround

650) this.width=650; "src=" http://s1.51cto.com/wyfs02/M00/89/5F/wKioL1gRbvqjrVtcAAA4eVx2Dz8396.jpg "title=" icon 2. JPG "alt=" Wkiol1grbvqjrvtcaaa4evx2dz8396.jpg "/>

MySQL error 1878 incorrect resolution to reproduce

Part1: Large table Modified field

Mysql>alter TABLE ' ERP '

ADD COLUMN ' eas_status ' tinyint (3) unsigned not NULL DEFAULT 0 ' after ' totalprice ';

ERROR1878 (HY000): temporary file write failure.

Mysql>\q

As you can see, there are 1878 errors when adding a field.

Part2: Troubleshooting Process

First look at database error log

2016-10-27 10:19:22 7f5dca1bf700 innodb: error: write to file  (merge)  failed at offset 258998272.InnoDB: 1048576 bytes should have  Been written, only 651264 were written. innodb: operating system error number 0.innodb: check that your  Os and file system support files of this size. Innodb: check also that the disk is not full or a disk  quota exceeded. innodb: error number 0 means  ' Success '. Innodb: some operating system error numbers are described atinnodb:  http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html2016-10-27 10:35:34  7f5dcb42f700 innodb: error: write to file  (merge)  failed at  Offset 88080384.InnoDB: 1048576 bytes should have been written, only  782336 were written. innodb: operating system error number 0.innodb: check that your  Os and file system support files of this size. Innodb: check also that the disk is not full or a disk  quota exceeded. innodb: error number 0 means  ' Success '. Innodb: some operating system error numbers are described atinnodb:  http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html2016-10-27 10:37:02  7f5dd0076700 innodb: error: write to file  (merge)  failed at  Offset 88080384.innodb: 1048576 bytes should have been written, only  770048 were written. InnoDb: operating system error number 0.innodb: check that your os  and file system support files of this size. Innodb: check also that the disk is not full or a disk  quota exceeded. innodb: error number 0 means  ' Success '. Innodb: some operating system error numbers are described atinnodb:  http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html

View the error log to see insufficient disk space

Part3: Validation

[[Email protected]helei]# df-h

Filesystem Size used Avail use% mounted on

/dev/mapper/volgroup-lv_root

45G 43G 160M 100%/

Tmpfs 7.9G 1.2M 7.9G 1%/DEV/SHM

/DEV/SDA1 477M 90M 358M 21%/boot

You can see that there is not enough disk space to free up disk space,

-- summary --

< Span lang= "ZH-CN" style= "Font-size:14px;font-family:simsun;" xml:lang= "ZH-CN" because the remaining space size of the Tmpdir partition of MySQL is not Span lang= "en-US" style= "FONT-FAMILY:CALIBRI;FONT-SIZE:14PX;" xml:lang= "en-US" >erp  mysql in alter table

This article is from the "He Lei" blog, make sure to keep this source http://suifu.blog.51cto.com/9167728/1866212

MySQL ERROR 1878 Workaround