I accidently filled the / recently and it seems to have damaged my installation beyond repair. Anyway, the thought occurred to me that I could use the mythbackup script (via liveCD & chroot) to backup the useful data. Unfortunately mythbackup is failing with

Warning, table lists are not identical!

The backup is bad or already out of date!

My first thought was that the MySQL tables were corrupted, it later occurred to me that I had used the 0.20 upgrade and it might have a different table structure from 0.19 that mythbackup doesn't recognize?

I can't say it's the cause of the errors you are seeing, but the database in 0.19 is a different structure from 0.20. My guess is the backup script on the R5D1 CD won't help you in this case. If you have access to hard disk space while booted on the live CD, you could use mysqldump to create a backup of the database.

The backup uses mysqldump. It also checks the backup files against what is actually on disk and in the DB, there are no significant version dependencies. The older versions of the script (and in this context even R5D1 is "older") could get fooled if there was something else accessing the DB or modifying the filesystem at the same time.

If you can provide more specific errors, I can tell you if they're real or just a false alarm.

This is an excerpt near the end of the log:



This is followed by quite a few other similar listing of mysql tables, I've truncated it as its fairly long. Thinking about it, when I filled root I was upgrading MySQL to v5, perhaps the newer version of mysql(dump) is confusing backup?

Oh, hang on... the default mysqldump format changed somewhere along the way and we got a bunch of this in testing

Can you take a look at the mythconverg.sql or mythconverg.sql.gz or mythconverg.sql.bz2 file, (use "more X", or "gzip -dc X.gz | more", or "bzip2 -dc X.bz2 | more") and look at the first several insert statements. If there is only one record per insert (and one insert per record) then it's old style and those are probably real errors, if each insert statement contains data for multiple records, then it may be a false alarm.

The insert statements do seem to appear all in one line so they may be fine.

Ironically the reason I upgraded MySQL was to insert the new format of the dump. Doh

I'll PM you some updates to the scripts...