I am running 2.4.18-smp. You said you upgraded to a 2.4 smp kernel and it solved the problem? What 2.4 version exactly did you run and was it a RedHat kernel? Thanks.
Richard Gabriel Director of Technology, CoreSense Inc. (518) 306-3043 x3951 ----- Original Message ----- From: "Joseph Bueno" <[EMAIL PROTECTED]> To: "Tom Roos" <[EMAIL PROTECTED]> Cc: "Richard Gabriel" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Wednesday, July 16, 2003 4:10 AM Subject: Re: Frequent Table Corruption - Please Help > Have you tried to use a non SMP kernel ? > I have also experienced table corruptions 2 years ago with > mysql 3.23.xx and a 2.2.14smp kernel. I had several servers > with the same configuration but only the most loaded had this > problem. I had no more corruptions in single CPU mode. > I upgraded later to a newer smp kernel (2.4) that solved the > problem. > > It may be a temporary fix until you schedule an upgrade. > > Hope this helps > Joseph Bueno > > Tom Roos wrote: > > hi guys > > > > i am runing the rh 2.4.20-18.7smp kernel with mysql 4.0.13 and i sometimes experience problems with table corruptions when volumes become high. > > > > i'm trying different parameters for mysqld to see if the problem goes away. > > > > tom > > > > -----Original Message----- > > From: Richard Gabriel [mailto:[EMAIL PROTECTED] > > Sent: 15 July 2003 22:35 > > To: Heikki Tuuri; [EMAIL PROTECTED] > > Subject: Re: Frequent Table Corruption - Please Help > > > > > > Thank you very much for the help. I will schedule the upgrade and see if > > helps. I have 2 other machines running 2.4.18 without problems, but they > > also do not run the volume that the problematic machine has and they do not > > have RAID. Take care. > > > > Richard Gabriel > > Director of Technology, > > CoreSense Inc. > > (518) 306-3043 x3951 > > > > ----- Original Message ----- > > From: "Heikki Tuuri" <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Sent: Tuesday, July 15, 2003 4:08 PM > > Subject: Re: Frequent Table Corruption - Please Help > > > > > > > >>Richard, > >> > >>----- Original Message ----- > >>From: "Richard Gabriel" <[EMAIL PROTECTED]> > >>To: "Heikki Tuuri" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> > >>Sent: Tuesday, July 15, 2003 10:53 PM > >>Subject: Re: Frequent Table Corruption - Please Help > >> > >> > >> > >>>Thanks for the tip. I'll see about upgrading, but it won't be a small > >> > >>task. > >> > >>>Any reason why 2.4.18 problems wouldn't have effected MySQL 3.23? I'm > >>>trying to search for a solution that does not involve upgrading kernels > > > > on > > > >>>20 machines that are in production use right now. Thanks again! > >> > >>it may be worthwhile to test a new kernel in one of those problematic > >>computers. > >> > >>We believe corruption problems in RH 2.4.18/drivers are random. Then any > >>small change can provoke them. But we will probably never know what > > > > exactly > > > >>was wrong in some 2.4.18 computers. > >> > >> > >>>Richard Gabriel > >>>Director of Technology, > >>>CoreSense Inc. > >>>(518) 306-3043 x3951 > >> > >>Regards, > >> > >>Heikki > >> > >> > >> > >>>----- Original Message ----- > >>>From: "Heikki Tuuri" <[EMAIL PROTECTED]> > >>>To: <[EMAIL PROTECTED]> > >>>Sent: Tuesday, July 15, 2003 3:45 PM > >>>Subject: Re: Frequent Table Corruption - Please Help > >>> > >>> > >>> > >>>>Richard, > >>>> > >>>>you are running a Red Hat kernel 2.4.18? Kernels 2.4.20 seem to be > > > > much > > > >>>more > >>> > >>>>reliable. > >>>> > >>>>Best regards, > >>>> > >>>>Heikki Tuuri > >>>>Innobase Oy > >>>>http://www.innodb.com > >>>>Transactions, foreign keys, and a hot backup tool for MySQL > >>>>Order MySQL technical support from https://order.mysql.com/ > >>>> > >>>>----- Original Message ----- > >>>>From: "Richard Gabriel" <[EMAIL PROTECTED]> > >>>>Newsgroups: mailing.database.mysql > >>>>Sent: Tuesday, July 15, 2003 9:52 PM > >>>>Subject: Frequent Table Corruption - Please Help > >>>> > >>>> > >>>> > >>>>>Hi everyone, > >>>>> > >>>>>Since we upgraded to MySQL 4.0.13 from 3.23, we have been getting > >> > >>table > >> > >>>>>corruption often. It happens about twice per week (with about 500 > >>>>>queries per second average). I have even set up a cron to run > >>>>>mysqlcheck every hour to try to do some damage control. The biggest > >>>>>problem is that once the table is corrupted, it seems to be locked. > >>>>>Well, no clients can read from it. Once repaired, just one record > > > > is > > > >>>>>usually lost for each time the corruption occurs. I am not sure if > >> > >>this > >> > >>>>>is a MySQL bug or even how to reproduce it, but I was hoping that > >>>>>someone here could help. I have included all the information that I > >>>>>have about this below. Any insight is greatly appreciated! > >>>>> > >>>>> > >>>>>Here is the mysqlbug information: > >>>>> > >>>>> > >>>>>>Release: mysql-4.0.13 (Official MySQL RPM) > >>>>> > >>>>>>C compiler: 2.95.3 > >>>>>>C++ compiler: 2.95.3 > >>>>>>Environment: > >>>>> > >>>>>System: Linux *****.com 2.4.18-14smp #1 SMP Wed Sep 4 12:34:47 EDT > >> > >>2002 > >> > >>>>>i686 i686 i386 GNU/Linux > >>>>>Architecture: i686 > >>>>> > >>>>>Some paths: /usr/bin/perl /usr/bin/make /usr/bin/gmake /usr/bin/gcc > >>>>>/usr/bin/ccGCC: Reading specs from > >>>>>/usr/lib/gcc-lib/i386-redhat-linux/3.2/specs > >>>>>Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > >>>>>--infodir=/usr/share/info --enable-shared --enable-threads=posix > >>>>>--disable-checking --host=i386-redhat-linux --with-system-zlib > >>>>>--enable-__cxa_atexit > >>>>>Thread model: posix > >>>>>gcc version 3.2 20020903 (Red Hat Linux 8.0 3.2-7) > >>>>>Compilation info: CC='gcc' CFLAGS='-O6 -fno-omit-frame-pointer > >>>>>-mpentium' CXX='g++' CXXFLAGS='-O6 -fno-omit-frame-pointer > >>>>>-felide-constructors -fno-exceptions -fno-rtti -mpentium' > > > > LDFLAGS='' > > > >>>>>ASFLAGS='' > >>>>>LIBC: > >>>>>lrwxrwxrwx 1 root root 14 Nov 1 2002 > > > > /lib/libc.so.6 > > > >>>>>-> libc-2.2.93.so > >>>>>-rwxr-xr-x 1 root root 1235468 Sep 5 2002 > >>>>>/lib/libc-2.2.93.so > >>>>>-rw-r--r-- 1 root root 2233342 Sep 5 2002 > >> > >>/usr/lib/libc.a > >> > >>>>>-rw-r--r-- 1 root root 178 Sep 5 2002 > >> > >>/usr/lib/libc.so > >> > >>>>>Configure command: ./configure '--disable-shared' > >>>>>'--with-mysqld-ldflags=-all-static' > >> > >>'--with-client-ldflags=-all-static' > >> > >>>>>'--without-berkeley-db' '--with-innodb' '--without-vio' > >>>>>'--without-openssl' '--enable-assembler' '--enable-local-infile' > >>>>>'--with-mysqld-user=mysql' > >>>>>'--with-unix-socket-path=/var/lib/mysql/mysql.sock' '--prefix=/' > >>>>>'--with-extra-charsets=complex' '--exec-prefix=/usr' > >>>>>'--libexecdir=/usr/sbin' '--sysconfdir=/etc' '--datadir=/usr/share' > >>>>>'--localstatedir=/var/lib/mysql' '--infodir=/usr/share/info' > >>>>>'--includedir=/usr/include' '--mandir=/usr/share/man' > >>>>>'--with-embedded-server' '--enable-thread-safe-client' > >>>>>'--with-comment=Official MySQL RPM' > >> > >>'CFLAGS=-O6 -fno-omit-frame-pointer > >> > >>>>>-mpentium' 'CXXFLAGS=-O6 -fno-omit-frame-pointer > >>>>>-felide-constructors -fno-exceptions -fno-rtti -mpentium' > >>>>> > >>>>> > >>>>> > >>>>>Other System Information: > >>>>>The system is running hardware RAID-10 with SCSI drives. It has 4 > >> > >>Xeon > >> > >>>>>processors at 2.2GHz each, 2GB RAM. > >>>>> > >>>>> > >>>>> > >>>>>MySQL Configuration (my.cnf): > >>>>>[mysqld] > >>>>>set-variable = max_connections=1000 > >>>>>set-variable = delayed_queue_size=100000 > >>>>> > >>>>>innodb_data_file_path=ibdata:30M:autoextend:max:2000M > >>>>># Set buffer pool size to > >>>>># 50 - 80 % of your computer's > >>>>># memory > >>>>>set-variable = innodb_buffer_pool_size=1G > >>>>>set-variable = innodb_additional_mem_pool_size=20M > >>>>># Set the log file size to about > >>>>># 15 % of the buffer pool size > >>>>>set-variable = innodb_log_file_size=150M > >>>>>set-variable = innodb_log_buffer_size=8M > >>>>># > >>>>> > >>>>>log-bin > >>>>>server-id=1 > >>>>>master-host=192.168.1.3 > >>>>>master-user=repl > >>>>>master-password=***** > >>>>>master-port=3306 > >>>>> > >>>>>set-variable = query_cache_size=268435456 > >>>>> > >>>>> > >>>>> > >>>>>Log Entries: > >>>>>[The first entry is repeated many times. The second is from the > >>>>>mysqlcheck cron that repairs the tables] > >>>>> > >>>>>030715 0:43:49 read_const: Got error 127 when reading table **** > >>>>>030715 2:00:31 Note: Found 23550 of 23551 rows when repairing **** > >>>>> > >>>>> > >>>>>Thanks again for your help in advance! > >>>>> > >>>>>-- > >>>>>Richard Gabriel <[EMAIL PROTECTED]> > >>>>> > >>>>>-- > >>>>>MySQL General Mailing List > >>>>>For list archives: http://lists.mysql.com/mysql > >>>>>To unsubscribe: > >>>> > >>>>http://lists.mysql.com/[EMAIL PROTECTED] > >>>> > >>>> > >>>> > >>>>-- > >>>>MySQL General Mailing List > >>>>For list archives: http://lists.mysql.com/mysql > >>>>To unsubscribe: > >>> > >>>http://lists.mysql.com/[EMAIL PROTECTED] > >>> > >>>> > >> > >> > >>-- > >>MySQL General Mailing List > >>For list archives: http://lists.mysql.com/mysql > >>To unsubscribe: > > > > http://lists.mysql.com/[EMAIL PROTECTED] > > > >> > > > > > > > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
