Re: Disasterous database corruption

2005-08-14 Thread Sergei Golubchik
Hi! On Aug 09, Daniel Kasak wrote: > Hi all. > > I've been testing out mysql-5.0.10 on my Powerbook ( Gentoo Linux PPC ), > and I've hit an incredibly unfortunate bug. It is demonstrated > adequately with the following: ... > Is anyone interested in examining what went wrong? ie should I create

Re: Disasterous database corruption

2005-08-10 Thread Fajar Priyanto
On Wednesday 10 August 2005 10:23 am, Daniel Kasak wrote: > Fajar Priyanto wrote: > >Well, it's not 5.0.x, it's 4.0.25-standard. I'm not sure how the error > > appears in the first place. What I notice when I open the database using > > phpMyadmin is that that particular troubled table status is "i

Re: Disasterous database corruption

2005-08-09 Thread Daniel Kasak
Fajar Priyanto wrote: Well, it's not 5.0.x, it's 4.0.25-standard. I'm not sure how the error appears in the first place. What I notice when I open the database using phpMyadmin is that that particular troubled table status is "in use". I'm allowed to ssh into the server, and hopefully I can s

Re: Disasterous database corruption

2005-08-09 Thread Fajar Priyanto
On Wednesday 10 August 2005 06:50 am, Daniel Kasak wrote: > A hosting provider running 5.0.x? That's whacky. > When you say "my access to the shell is very limited", what does that > mean exactly? Can you ssh in and run the 'mysql' command-line client? If > you can, then do it, and you should be ab

Re: Disasterous database corruption

2005-08-09 Thread Daniel Kasak
Fajar Priyanto wrote: This is what I think hit me too, Daniel. Unfortunately, it's not on my own server (a hosting provider), so my access to the shell is very limited. My website is still running, but, I can't export the database using phpMyadmin anymore, because the troubled table is on th

Re: Disasterous database corruption

2005-08-09 Thread Daniel Kasak
Timothy Smith wrote: Hi, Daniel, First, here's a trick that *should* work for dumping out the data. Change directory to the MySQL data directory, and then use this little shell command: for d in mysql test; do (cd $d; tables=`/bin/ls -1 *.frm | sed -e s,\\.frm,,`; mysqldump $d $tables); done

Re: Disasterous database corruption

2005-08-09 Thread Fajar Priyanto
This is what I think hit me too, Daniel. Unfortunately, it's not on my own server (a hosting provider), so my access to the shell is very limited. My website is still running, but, I can't export the database using phpMyadmin anymore, because the troubled table is on the first list of tables. D