Re: fast index corruption... Help !

2001-01-16 Thread Jan Tegtmeier
Hi Joseph, >Hardware platform : > Dell PowerEdge 2450 bipro PIII/733, > 2Gb RAM, > integrated hardware RAID crontroller (PERC3) > with 2x18Gb disks configured > in RAID1 (mirroring) mode. > >Operating system: > Linux RedHat 6.2 (kernel 2.2.14 SMP) >[...] > I tried to use --safe-mode but I had to

fast index corruption... Help ! [Summary]

2001-01-14 Thread Joseph Bueno
Hello, I have posted several emails to this list during the last few days because of mysqld crashes and index corruptions. Since then I have made several modifications to the server but I still have occasional index corruptions (about one corruption every two hours, the figure seems to vary with

Re: fast index corruption... Help !

2001-01-14 Thread Sinisa Milivojevic
Joseph Bueno writes: > Sinisa Milivojevic a écrit : > > Yes, from MySQL-3.23.30-1.i386.rpm > > BTW, are there any known issues with: > > - glibc from RedHat 6.2 (I have checked Red Hat site there is > no update for it) > > - MySQL with SMP (I have been told to try with one CPU onl

Re: fast index corruption... Help !

2001-01-13 Thread Joseph Bueno
Sinisa Milivojevic a écrit : > > Joseph Bueno writes: > > Hello, > > > > I posted message below a few hours ago. > > Since then, I have tried to find how fast indexes become corrupt. > > I have run a CHECK TABLE QUICK > > on different tables in my database and run a > > REPAIR TABLE whe

Re: fast index corruption... Help !

2001-01-13 Thread Sinisa Milivojevic
Joseph Bueno writes: > Hello, > > I posted message below a few hours ago. > Since then, I have tried to find how fast indexes become corrupt. > I have run a CHECK TABLE QUICK > on different tables in my database and run a > REPAIR TABLE when an error is reported followed > by a CHECK T

fast index corruption... Help !

2001-01-12 Thread Joseph Bueno
Hello, I posted message below a few hours ago. Since then, I have tried to find how fast indexes become corrupt. I have run a CHECK TABLE QUICK on different tables in my database and run a REPAIR TABLE when an error is reported followed by a CHECK TABLE a few seconds later. Here is the output