求救mysql error:the table is full

[yinyuehan823]

各位高手，小弟在往mysql中导入数据的时候遇到这样一个错误error:the table is full，我查看mysql打印出来的error:
Version: '5.0.27-community-nt' socket: '' port: 3306 MySQL Community Edition (GPL)
091124 21:41:24 InnoDB: Encountered a problem with file .\ibdata3
091124 21:41:24 InnoDB: Disk is full. Try to clean the disk to free space.
091124 21:41:41 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Normal shutdown

091124 21:41:43 [Warning] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Forcing close of thread 2 user: 'root'

我的mysql安装在C盘，datadir在D盘，C盘还有的空间是10.23G，D盘的空间还有27G。我在网上搜索两个解决（1、修改innodb_data_file_path的设置；2、修改

tmp_table_size ）都还是出现同样的错误

我实在不明白为什么会出现这样的错误，期待高手给解答，小弟不胜感激～！

[yinyuehan823]

附我的my.ini
# MySQL Server Instance Configuration File
# ----------------------------------------------------------------------
# Generated by the MySQL Server Instance Configuration Wizard
#
#
# Installation Instructions
# ----------------------------------------------------------------------
#
# On Linux you can copy this file to /etc/my.cnf to set global options,
# mysql-data-dir/my.cnf to set server-specific options
# (@localstatedir@ for this installation) or to
# ~/.my.cnf to set user-specific options.
#
# On Windows you should keep this file in the installation directory
# of your server (e.g. C:\Program Files\MySQL\MySQL Server X.Y). To
# make sure the server reads the config file use the startup option
# "--defaults-file".
#
# To run run the server from the command line, execute this in a
# command line shell, e.g.
# mysqld --defaults-file="C:\Program Files\MySQL\MySQL Server X.Y\my.ini"
#
# To install the server as a Windows service manually, execute this in a
# command line shell, e.g.
# mysqld --install MySQLXY --defaults-file="C:\Program Files\MySQL\MySQL Server X.Y\my.ini"
#
# And then execute this in a command line shell to start the server, e.g.
# net start MySQLXY
#
#
# Guildlines for editing this file
# ----------------------------------------------------------------------
#
# In this file, you can use all long options that the program supports.
# If you want to know the options a program supports, start the program
# with the "--help" option.
#
# More detailed information about the individual options can also be
# found in the manual.
#
#
# CLIENT SECTION
# ----------------------------------------------------------------------
#
# The following options will be read by MySQL client applications.
# Note that only client applications shipped by MySQL are guaranteed
# to read this section. If you want your own MySQL client program to
# honor these values, you need to specify it as an option during the
# MySQL client library initialization.
#
[client]

port=3306

[mysql]

default-character-set=utf8


# SERVER SECTION
# ----------------------------------------------------------------------
#
# The following options will be read by the MySQL Server. Make sure that
# you have installed the server correctly (see above) so it reads this
# file.
#
[mysqld]

# The TCP/IP Port the MySQL Server will listen on
port=3306


#Path to installation directory. All paths are usually resolved relative to this.
basedir="C:/Program Files/MySQL/MySQL Server 5.0/"

tmpdir="C:/tmp"

#Path to the database root
#datadir="C:/Program Files/MySQL/MySQL Server 5.0/Data/"
datadir="D:/MySQL/data/"

# The default character set that will be used when a new schema or table is
# created and no character set is defined
default-character-set=utf8

# The default storage engine that will be used when create new tables when
default-storage-engine=INNODB

# Set the SQL mode to strict
# sql-mode="STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION"

# The maximum amount of concurrent sessions the MySQL server will
# allow. One of these connections will be reserved for a user with
# SUPER privileges to allow the administrator to login even if the
# connection limit has been reached.
max_connections=100

# Query cache is used to cache SELECT results and later return them
# without actual executing the same query once again. Having the query
# cache enabled may result in significant speed improvements, if your
# have a lot of identical queries and rarely changing tables. See the
# "Qcache_lowmem_prunes" status variable to check if the current value
# is high enough for your load.
# Note: In case your tables change very often or if your queries are
# textually different every time, the query cache may result in a
# slowdown instead of a performance improvement.
query_cache_size=0

# The number of open tables for all threads. Increasing this value
# increases the number of file descriptors that mysqld requires.
# Therefore you have to make sure to set the amount of open files
# allowed to at least 4096 in the variable "open-files-limit" in
# section [mysqld_safe]
table_cache=256

# Maximum size for internal (in-memory) temporary tables. If a table
# grows larger than this value, it is automatically converted to disk
# based table This limitation is for a single table. There can be many
# of them.
tmp_table_size=40M


# How many threads we should keep in a cache for reuse. When a client
# disconnects, the client's threads are put in the cache if there aren't
# more than thread_cache_size threads from before. This greatly reduces
# the amount of thread creations needed if you have a lot of new
# connections. (Normally this doesn't give a notable performance
# improvement if you have a good thread implementation.)
thread_cache_size=8

#*** MyISAM Specific options

# The maximum size of the temporary file MySQL is allowed to use while
# recreating the index (during REPAIR, ALTER TABLE or LOAD DATA INFILE.
# If the file-size would be bigger than this, the index will be created
# through the key cache (which is slower).
myisam_max_sort_file_size=100G

# If the temporary file used for fast index creation would be bigger
# than using the key cache by the amount specified here, then prefer the
# key cache method. This is mainly used to force long character keys in
# large tables to use the slower key cache method to create the index.
myisam_max_extra_sort_file_size=100G

# If the temporary file used for fast index creation would be bigger
# than using the key cache by the amount specified here, then prefer the
# key cache method. This is mainly used to force long character keys in
# large tables to use the slower key cache method to create the index.
myisam_sort_buffer_size=34M

# Size of the Key Buffer, used to cache index blocks for MyISAM tables.
# Do not set it larger than 30% of your available memory, as some memory
# is also required by the OS to cache rows. Even if you're not using
# MyISAM tables, you should still set it to 8-64M as it will also be
# used for internal temporary disk tables.
key_buffer_size=25M

# Size of the buffer used for doing full table scans of MyISAM tables.
# Allocated per thread, if a full scan is needed.
read_buffer_size=64K
read_rnd_buffer_size=256K

# This buffer is allocated when MySQL needs to rebuild the index in
# REPAIR, OPTIMZE, ALTER table statements as well as in LOAD DATA INFILE
# into an empty table. It is allocated per thread so be careful with
# large settings.
sort_buffer_size=256K


#*** INNODB Specific options ***


# Use this option if you have a MySQL server with InnoDB support enabled
# but you do not plan to use it. This will save memory and disk space
# and speed up some things.
#skip-innodb

# Additional memory pool that is used by InnoDB to store metadata
# information. If InnoDB requires more memory for this purpose it will
# start to allocate it from the OS. As this is fast enough on most
# recent operating systems, you normally do not need to change this
# value. SHOW INNODB STATUS will display the current amount used.
innodb_additional_mem_pool_size=2M

# If set to 1, InnoDB will flush (fsync) the transaction logs to the
# disk at each commit, which offers full ACID behavior. If you are
# willing to compromise this safety, and you are running small
# transactions, you may set this to 0 or 2 to reduce disk I/O to the
# logs. Value 0 means that the log is only written to the log file and
# the log file flushed to disk approximately once per second. Value 2
# means the log is written to the log file at each commit, but the log
# file is only flushed to disk approximately once per second.
innodb_flush_log_at_trx_commit=1

# The size of the buffer InnoDB uses for buffering log data. As soon as
# it is full, InnoDB will have to flush it to disk. As it is flushed
# once per second anyway, it does not make sense to have it very large
# (even with long transactions).
innodb_log_buffer_size=1M

# InnoDB, unlike MyISAM, uses a buffer pool to cache both indexes and
# row data. The bigger you set this the less disk I/O is needed to
# access data in tables. On a dedicated database server you may set this
# parameter up to 80% of the machine physical memory size. Do not set it
# too large, though, because competition of the physical memory may
# cause paging in the operating system. Note that on 32bit systems you
# might be limited to 2-3.5G of user level memory per process, so do not
# set it too high.
innodb_buffer_pool_size=47M

# Size of each log file in a log group. You should set the combined size
# of log files to about 25%-100% of your buffer pool size to avoid
# unneeded buffer pool flush activity on log file overwrite. However,
# note that a larger logfile size will increase the time needed for the
# recovery process.
innodb_log_file_size=24M

# Number of threads allowed inside the InnoDB kernel. The optimal value
# depends highly on the application, hardware as well as the OS
# scheduler properties. A too high value may lead to thread thrashing.
innodb_thread_concurrency=8
innodb_data_file_path = ibdata1:3000M;ibdata2:3000M;ibdata3:4000M:autoextend

[ACMAIN_CHM]

091124 21:41:24 InnoDB: Disk is full. Try to clean the disk to free space.

检查你的磁盘空间，或分配的磁盘配额。

[yinyuehan823]

[Quote=引用 3 楼 acmain_chm 的回复:]
091124 21:41:24  InnoDB:Disk is full.Try to clean the disk to free space.

检查你的磁盘空间，或分配的磁盘配额。
[/Quote]
我C盘空间还有10.23G，D盘还有27G空间
能否具体点怎么检查，谢谢～

[yinyuehan823]

[Quote=引用 3 楼 acmain_chm 的回复:]
091124 21:41:24  InnoDB:Disk is full.Try to clean the disk to free space.

检查你的磁盘空间，或分配的磁盘配额。
[/Quote]

我刚才计算了一下，我D盘的3个ibdata 总量加起来是10.332G，C盘剩余10.23G, 是否是因为我的data dir还会以某种方式检查data dir大小和C盘比较？

[ACMAIN_CHM]

先检查一下
innodb_data_file_path = ibdata1:3000M;ibdata2:3000M;ibdata3:4000M:autoextend
这三个文件都有没有生成？ datadir="D:/MySQL/data/" 中的相关文件都在不在？ 比如 mysql 目录及其它文件。

建议把 datadir="D:/MySQL/data/" 改到C盘试一下。 当然先把 innodb_data_file_path 改小一些，你的C盘总共才 10G.

[yinyuehan823]

回复楼上的：

我的三个文件都生成了，以前一直在C盘，后来是因为里面数据量太大，我把他移到D盘的，改成C盘肯定是不行，因为现在里面的数据已经超过10.23G，我能正常启动，也能正常查询数据，但不能insert 数据

[yinyuehan823]

因为我还要导入大概2G的数据，上午导入前一张表的数据还可以正常导入

[ACMAIN_CHM]

tmpdir="C:/tmp"

也改到D盘试一下。

[yinyuehan823]

[Quote=引用 9 楼 acmain_chm 的回复:]
tmpdir="C:/tmp"

也改到D盘试一下。
[/Quote]

不可以，还是一样的错误

[ACMAIN_CHM]

innodb_data_file_path = ibdata1:3000M;ibdata2:3000M;ibdata3:3000M:autoextend

把 ibdata3 改为 3G, 4G刚好是上限。

[yinyuehan823]

[Quote=引用 13 楼 vinsonshen 的回复:]
直接到目录下，看看现在ibdata3文件到底有多大？看了下你参数里是预定初始大小是4G的，看看跟这个值是否一致？
[/Quote]

我的这个ibdata3是4.193G，最后一个是扩展的，我同事的就一个ibdata 到达15G都没有问题

[yinyuehan823]

[Quote=引用 12 楼 vinsonshen 的回复:]
091124 21:41:24  InnoDB: Encountered a problem with file .\ibdata3
091124 21:41:24  InnoDB: Disk is full. Try to clean the disk to free space.


-------------------------------------------------
问题所在是“ibdata3”，检查该文件所属的磁盘空间是否还有空余？是否该文件达到了操作系统对文件最大大小的限制？
[/Quote]

这个磁盘还有27G，空余是肯定有的

[wwwwb]

磁盘格式是什么？如果不行，用工MYSQLDUMP备份出来，删除ib*,*,重新启动MYSQL，会重新建立
IB*，*，再将数据导回去

[vinsonshen]

[Quote=引用 14 楼 yinyuehan823 的回复:]
引用 13 楼 vinsonshen 的回复:
直接到目录下，看看现在ibdata3文件到底有多大？看了下你参数里是预定初始大小是4G的，看看跟这个值是否一致？


我的这个ibdata3是4.193G，最后一个是扩展的，我同事的就一个ibdata 到达15G都没有问题
[/Quote]

这个还要看磁盘格式有关系的呢，确认你和你同事存放数据的磁盘格式一样？

[ACMAIN_CHM]

[Quote]我的这个ibdata3是4.193G，最后一个是扩展的，我同事的就一个ibdata 到达15G都没有问题[/Quote]

如果你的D盘是 NTFS 则没有问题，需要去检查一下权限。
如果你的D盘是FAT，则这个文件就太大了。官方文档中说明是最大支持到 4G

[yinyuehan823]

[Quote=引用 18 楼 acmain_chm 的回复:]
引用我的这个ibdata3是4.193G，最后一个是扩展的，我同事的就一个ibdata 到达15G都没有问题

如果你的D盘是 NTFS 则没有问题，需要去检查一下权限。
如果你的D盘是FAT，则这个文件就太大了。官方文档中说明是最大支持到 4G
[/Quote]

谢谢，我已经解决了，是因为我的文件系统式FAT32的，我转换为NTFS后就可以用了

[yinyuehan823]

小弟在此感谢各位高手的指点与关注~

[vinsonshen]

[Quote=引用 19 楼 yinyuehan823 的回复:]
引用 18 楼 acmain_chm 的回复:
引用我的这个ibdata3是4.193G，最后一个是扩展的，我同事的就一个ibdata 到达15G都没有问题

如果你的D盘是 NTFS 则没有问题，需要去检查一下权限。
如果你的D盘是FAT，则这个文件就太大了。官方文档中说明是最大支持到 4G


谢谢，我已经解决了，是因为我的文件系统式FAT32的，我转换为NTFS后就可以用了
[/Quote]
呵，一早就叫你检查磁盘格式的啦，不同格式对文件的最大大小限制有所不同的

[vinsonshen]

091124 21:41:24 InnoDB: Encountered a problem with file .\ibdata3
091124 21:41:24 InnoDB: Disk is full. Try to clean the disk to free space.


-------------------------------------------------
问题所在是“ibdata3”，检查该文件所属的磁盘空间是否还有空余？是否该文件达到了操作系统对文件最大大小的限制？

[vinsonshen]

直接到目录下，看看现在ibdata3文件到底有多大？看了下你参数里是预定初始大小是4G的，看看跟这个值是否一致？