Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Table full problems

Status
Not open for further replies.

svar

Programmer
Aug 12, 2001
349
GR
A curious thing: I get on a few tables(using InnoDB and 4.01) 'table full' errors. The funny thing is that these tabbles have about 90000 records, while the rest have about 40000; However, I also get the btable full for a table with 4700 records.
I start mysqld_safe --big-tables

Any ideas what to check?
Thanks, svar
 
What version of MySQL is it, I know that the table size limit was changed with 3.23(?) from a 4gig table to a maximum of several terrabytes theoretical depending on machine capabilities.

Also do you have any disk space left? ***************************************
Party on, dudes!
[cannon]
 
Thanks,. It is 4.01
there is a lot of space left(see below df -h)

Here is hostname.err
(On a 2GB RAM, 2x1000 CPU, )

InnoDB: Database was not shut down normally.
InnoDB: Starting recovery from log files...
InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 3 751045500
020418 0:50:33 InnoDB: Started
/usr/sbin/mysqld: ready for connections
InnoDB: Assertion failure in thread 40971 in file trx0trx.c line 228
InnoDB: We intentionally generate a memory trap.
InnoDB: Send a detailed bug report to mysql@lists.mysql.com
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=402649088
record_buffer=2093056
sort_buffer=2097144
max_used_connections=1
max_connections=10
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (record_buffer + sort_buffer)*max_connections = 434131 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

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 range sanity check OK, backtrace follows:
0x807db7f
0x823d60a
0x8179eac
0x80d50b7
0x80cd82d
0x807798d
0x807d88a
0x8082515
0x824f1b8
0x823d383
0x823ab69
0x807d905
0x8084403
0x823baa7
0x826c1ca
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read and follow instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do
resolve it
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at (nil) is invalid pointer
thd->thread_id=2916

Successfully dumped variables, if you ran with --log, take a look at the
details of what thread 2916 did to cause the crash. In some cases of really
bad corruption, the values shown above may be invalid.

The manual page at contains
information that should help you find out what is causing the crash.

Number of processes running now: 0
020418 14:01:56 mysqld restarted
InnoDB: Warning: operating system error number 2 in a file operation.
InnoDB: Cannot continue operation.

# Example mysql config file for very large systems.
#
# This is for large system with memory of 1G-2G where the system runs mainly
# MySQL.
#
# You can copy this file to
# /etc/mf.cnf to set global options,
# mysql-data-dir/my.cnf to set server-specific options (in this
# installation this directory is /var/lib/mysql) or
# ~/.my.cnf to set user-specific options.
#
# One can in this file use all long options that the program supports.
# If you want to know which options a program support, run the program
# with --help option.

# The following options will be passed to all MySQL clients
[client]
#password = your_password
port = 3306
socket = /var/lib/mysql/mysql.sock

# Here follows entries for some specific programs

# The MySQL server
[mysqld]
port = 3306
socket = /var/lib/mysql/mysql.sock
skip-locking
set-variable = key_buffer=384M
set-variable = max_allowed_packet=1M
set-variable = table_cache=512
set-variable = max_connections=10
set-variable = tmp_table_size=400M
set-variable = sort_buffer=2M
set-variable = record_buffer=2M
set-variable = thread_cache=8
set-variable = thread_concurrency=4 # Try number of CPU's*2
#set-variable = myisam_sort_buffer_size=64M
set-variable = myisam_sort_buffer_size=4M
innodb_data_file_path=ibdata1:2000M;ibdata2:2000M;ibdata3:2000M;ibdata4:2000M;ibdata5:2000M;ibdata6:2000M;ibdata7:2000M;ibdata8:2000M;/usr/ibdata/ibdata9:2000M;/usr/ibdata/ibdata10:2000M
#Comment works ok with:
#innodb_data_file_path=ibdata1:2000M;ibdata2:2000M;ibdata3:2000M;ibdata4:2000M;ibdata5:2000M;ibdata6:2000M;ibdata7:2000M;ibdata8:2000M
# Also adding ibdata9:2000M to /var/lib/mysql does not work
log-bin
server-id = 1
#set-variable = open-files-limit=8192 #ulimit is 1024,hard 8192
set-variable = innodb_buffer_pool_size=750M
set-variable = innodb_additional_mem_pool_size=400M

# Uncomment the following if you are using BDB tables
#set-variable = bdb_cache_size=384M
#set-variable = bdb_max_lock=100000

# Point the following paths to different dedicated disks
#tmpdir = /tmp/
#log-update = /path-to-dedicated-directory/hostname

[mysqldump]
quick
set-variable = max_allowed_packet=256M

[mysql]
no-auto-rehash
#safe-updates # Remove the comment character if you are not familiar with SQL

[isamchk]
set-variable = key_buffer=256M
set-variable = sort_buffer=256M
set-variable = read_buffer=2M
set-variable = write_buffer=2M

[myisamchk]
#set-variable = key_buffer=256M
#set-variable = sort_buffer=256M
#set-variable = read_buffer=2M
#set-variable = write_buffer=2M
set-variable = key_buffer=25M
set-variable = sort_buffer=25M
set-variable = read_buffer=2M
set-variable = write_buffer=2M

[mysqlhotcopy]
interactive-timeout










------------------------df -h

Filesystem Size Used Avail Use% Mounted on
/dev/sda5 10G 758M 9.4G 8% /
/dev/sda1 45M 3.8M 39M 9% /boot
/dev/vg0home/vg0home 17G 16G 1.4G 92% /home
/dev/sda6 12G 1.6G 10G 13% /usr
/dev/sda7 6.9G 104M 6.7G 2% /var
/dev/vg0mysql/vg0mysql
34G 19G 15G 54% /var/lib/mysql
shmfs 1007M 0 1006M 0% /dev/shmt
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top