[mythtv-users] Upgrade to 2.6.17-gentoo-r2/ivtv-0.7.0/mythtv-0.19_p9163-r1 and having problems

[Mark Knecht]

On 7/16/06, glen martin <lists at locutory.org> wrote:
> Mark Knecht wrote:
> > First I'd like to make
> > sure the original databse is gone. Where is it kept?
> >
> On my gentoo systems the databases are under /var/lib/mysql, eg:
>
> ls /var/lib/mysql/
> boob-bin.000001  boob-bin.000005  boob-bin.000009  boob-bin.index  mysql
> boob-bin.000002  boob-bin.000006  boob-bin.000010  ib_logfile0
> mythconverg
> boob-bin.000003  boob-bin.000007  boob-bin.000011  ib_logfile1     test
> boob-bin.000004  boob-bin.000008  boob-bin.000012  ibdata1
>
> glen
>
> PS. Let's see how many spam filters I get caught in with my boob & toob
> machine names ... heh ;)

Mine didn't! ;-) (I don't run any!)

OK, so looking at the new /etc/mysql/my.cnf file I see the following:
(comments removed)

innodb_data_file_path = ibdata1:10M:autoextend:max:128M
innodb_log_file_size = 5M
innodb_log_buffer_size = 8M


While the old one (yes - at least I was smart enough to print that one
out first!) only had this:

innodb_data_file_path = ibdata1:10M:autoextend:max:128M
innodb_log_buffer_size = 8M

So I modified the middle line to be 8M and now I get further. From the
mysqld.err file I now see this when I try to start:

060716 14:41:04 [Note] /usr/sbin/mysqld: Shutdown complete

InnoDB: Resetting space id's in the doublewrite buffer
060716 14:58:15  InnoDB: Started; log sequence number 0 43892
InnoDB: You are upgrading to an InnoDB version which allows multiple
InnoDB: tablespaces. Wait that purge and insert buffer merge run to
InnoDB: completion...
InnoDB: Full purge and insert buffer merge completed.
InnoDB: You have now successfully upgraded to the multiple tablespaces
InnoDB: format. You should NOT DOWNGRADE to an earlier version of
InnoDB: InnoDB! But if you absolutely need to downgrade, see
InnoDB: http://dev.mysql.com/doc/mysql/en/Multiple_tablespaces.html
InnoDB: for instructions.
060716 14:58:17 [Warning] './mysql/host' had no or invalid character
set, and default character set is multi-byte, so character column
sizes may have changed
060716 14:58:17 [Warning] './mysql/user' had no or invalid character
set, and default character set is multi-byte, so character column
sizes may have changed
060716 14:58:17 [Warning] './mysql/db' had no or invalid character
set, and default character set is multi-byte, so character column
sizes may have changed
060716 14:58:17 [ERROR] Fatal error: mysql.user table is damaged or in
unsupported 3.20 format.
dragonfly mysql #

So, much further, but complaining about the table formats. Bummer!

Thanks!

- Mark