i dropped the database and recreated it before I ran the restore process so technically there shouldn't be anything in the db.
I looked on the MySQL website and they had a notice saying that people have had similar problems to me when they run mysql on the 2.2.14 kernel due to an i/o bug in the kernel (http://www.mysql.com/downloads/mysql-max-3.23.html) ... the server i'm running mysql on is runing the 2.2.16 kernel so i dont know is the bug still exists in this kernel but the note on the MySQL site also recommends upgrading to at least the 2.2.21 kernel. I suspect that when mysqldump was creating the backup of the databases the i/o bug in the kernel was causing mysqldump to write garbage thus presenting this problem. I've had to point all applications to a different physical server which is running the 2.4.8 kernel and so far things are good... thanks for your help. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Malcolm V Sent: Saturday, 13 July 2002 12:59 PM To: Sydney Linux Users Group Mailing List Subject: Re: [SLUG] MySQL problems On Sat, 2002-07-13 at 04:50, Chris Barnes wrote: > i use mysql --user=whoever --password=whatever --host=whereever < > dabase_backup.txt > all is well so it seems but its actually not...i keep getting the error > "Error 1062 at line 3: Duplicate entry '1' for key 1 > > so i use the --force argument with the command i issued above but it reports > the same thing.. > No idea why myisamchk isn't working (not that I have ever used it), the error you are getting about duplicate entries is because you are try to load the data back into a table that has a unique key, and you can't have two entries with the same key value. If you are sure your backup is good, just delete * from table_name then try to reload it. -- SLUG - Sydney Linux User's Group - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug -- SLUG - Sydney Linux User's Group - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
