Try putting the data directory on a small partition and let it get filled 100%
with a single update that does not get fully committed due to disk full, then
turn the power off to the computer so there is no attempt for a nice shutdown.
You should also get a corruption in the master binary logs, if
At 05:22 PM 11/6/2007, you wrote:
Hi David,
Thanks for your reply. This helped greatly.
Yeah, I supposed I could just randomly flip bits in the MySQL files
and that would do the trick.
The program I'm writing does first attempt to repair the tables with
MySQL's utilities if they're MyISAM but
Hi David,
Thanks for your reply. This helped greatly.
Yeah, I supposed I could just randomly flip bits in the MySQL files
and that would do the trick.
The program I'm writing does first attempt to repair the tables with
MySQL's utilities if they're MyISAM but InnoDB tables don't support
repair a
On 11/6/07, mos <[EMAIL PROTECTED]> wrote:
>
> At 02:18 PM 11/6/2007, Richard Edward Horner wrote:
> >Hi,
> >
> >I'm working on a program that will run in the event that tables are
> >crashed or corrupt. Can anyone recommend a good method for crashing my
> >tables or corrupting them so I have some
At 02:18 PM 11/6/2007, Richard Edward Horner wrote:
Hi,
I'm working on a program that will run in the event that tables are
crashed or corrupt. Can anyone recommend a good method for crashing my
tables or corrupting them so I have some test cases? I'm mostly
interested in MyISAM and InnoDB table
Hi,
I'm working on a program that will run in the event that tables are
crashed or corrupt. Can anyone recommend a good method for crashing my
tables or corrupting them so I have some test cases? I'm mostly
interested in MyISAM and InnoDB table types.
I was thinking I would just start an infinite
