corrupt innodb database

corrupt innodb database

am 02.08.2011 00:06:49 von supr_star

--0-25225918-1312236409=:55266
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

I'm not sure if this is the correct way to post, my apologies if it's not..=
=A0 Anyway, I have a zabbix system on a mysql database where the ibdata1 f=
ile grew to 93GB and filled up the disk. =A0Restarting mysql results in:=0A=
=0A/etc/init.d/mysql: ERROR: The partition with /var/lib/mysql is too full!=
=0AThis db is on its own partition, so I can't delete logs or anythin=
g else to clear up space. =A0So I moved=A0ib_logfile0 and=A0ib_logfile1 to =
/tmp to clear 10 megs, and restart. =A0mysql started but everything is out =
of sync now. =A0ERROR 1033 (HY000): Incorrect information in file: './zabbi=
x/users.frm' and similar for any tables I try to desc, select, etc. I =
put  =0A[mysqld]=0Ainnodb_force_recovery =3D 4 and tried every num=
ber from 1-8 in /etc/mysql/my.cnf. =A0I just took this job and there is no =
backup of this database. =A0Any command I issue in mysql results in: E=
RROR 1033 (HY000): Incorrect information in file: './zabbix/users.frm'=0A=
=0Afor any table in zabbix. mysql> repair table users;=0A+------------=
--+--------+----------+------------------------------------- ---------------=
-+=0A| Table =A0 =A0 =A0 =A0| Op =A0 =A0 | Msg_type | Msg_text =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
|=0A+--------------+--------+----------+-------------------- ---------------=
------------------+=0A| zabbix.users | repair | Error =A0 =A0| Incorrect in=
formation in file: './zabbix/users.frm' |=0A| zabbix.users | repair | error=
=A0 =A0| Corrupt =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 |=0A+--------------+--------+----------+---=
--------------------------------------------------+=0A2 rows in set (0.01 s=
ec) mysql> Is this 'game over' or can this data be recovered in a=
ny way? Thanks,
--0-25225918-1312236409=:55266--

Re: corrupt innodb database

am 02.08.2011 00:18:59 von a.smith

Quoting supr_star :

> This db is on its own partition, so I can't delete logs or anything
> else to clear up space.  So I moved ib_logfile0 and ib_logfile1

This is a really bad idea as will break all ur InnoDB databases. Do
you have space elsewhere on other partitions on the server? If yes
move the data file directories there and make a soft link from the old
DB data directory to the new location (ln -s). Then try and restart
MySQL and hopefully you haven't done permanent damage with the steps
you tried so far,

cheers Andy.




--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=gcdmg-mysql-2@m.gmane.org

Re: corrupt innodb database

am 02.08.2011 00:22:15 von a.smith

PS and put back the two log files you moved.
PPS if you don't have any space currently to do what I suggested then
at least softlink the log files from /tmp to their original locations.

Quoting a.smith@ukgrid.net:

> Quoting supr_star :
>
>> This db is on its own partition, so I can't delete logs or anything
>> else to clear up space.  So I moved ib_logfile0 and ib_logfile1
>
> This is a really bad idea as will break all ur InnoDB databases. Do
> you have space elsewhere on other partitions on the server? If yes
> move the data file directories there and make a soft link from the
> old DB data directory to the new location (ln -s). Then try and
> restart MySQL and hopefully you haven't done permanent damage with
> the steps you tried so far,
>
> cheers Andy.
>
>
>






--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=gcdmg-mysql-2@m.gmane.org