From: Gerald L. Clark (gerald_clarksuppliersystems.com)
Date: Tue May 27 2008 - 11:32:33 CDT

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Ben Lavender wrote:
> Hi all,
>
> Anyone ever seen a situation like this? Running myisamchk on a set of
> corrupted tables is hosing the entire file system on which the
> database is mounted.
>
>
> [rootbackend1 db_name]# touch test
> [rootbackend1 db_name]# myisamchk -r *.MYI
> - recovering (with sort) MyISAM-table 'accesslog.MYI'
> Data records: 2023
> myisamchk: error: Can't create new tempfile: 'accesslog.TMD'
> MyISAM-table 'accesslog.MYI' is not fixed because of errors
> Try fixing it by using the --safe-recover (-o), the --force (-f)
> option or by not using the --quick (-q) flag
>
> ---------
>
> - recovering (with sort) MyISAM-table 'access.MYI'
> Data records: 0
> - Fixing index 1
>
> ---------
>
> - recovering (with sort) MyISAM-table 'aggregator2_feed.MYI'
> Data records: 0
> - Fixing index 1
> - Fixing index 2
>
> ---------
>
> - recovering (with sort) MyISAM-table 'aggregator2_item.MYI'
> Data records: 0
> - Fixing index 1
> - Fixing index 2
> - Fixing index 3
> - Fixing index 4
>
> ---------
>
> - recovering (with sort) MyISAM-table 'aggregator_category_feed.MYI'
> Data records: 1
> myisamchk: error: Can't create new tempfile: 'aggregator_category_feed.TMD'
> MyISAM-table 'aggregator_category_feed.MYI' is not fixed because of errors
> Try fixing it by using the --safe-recover (-o), the --force (-f)
> option or by not using the --quick (-q) flag
>
> ---------
>
> - recovering (with sort) MyISAM-table 'aggregator_category_item.MYI'
> Data records: 1380
> - Fixing index 1
> myisamchk: Error writing file 'aggregator_category_item.TMD' (Errcode: 30)
> myisamchk: error: 30 when fixing table
> myisamchk: error: 30 when updating keyfile
> MyISAM-table 'aggregator_category_item.MYI' is not fixed because of errors
> Try fixing it by using the --safe-recover (-o), the --force (-f)
> option or by not using the --quick (-q) flag
>
> ---------
>
> myisamchk: error: 30 when opening MyISAM-table 'aggregator_category.MYI'
>
> ---------
>
> myisamchk: error: 30 when opening MyISAM-table 'aggregator_enclosure.MYI'
>
> ---------
>
> < snip a lot more error: 30's...>
>
> ---------
>
> myisamchk: error: 30 when opening MyISAM-table 'zipcodes.MYI'
> [rootbackend1 db_name]# touch test
> touch: cannot touch `test': Read-only file system
>
> For whatever reason, running myisamchk makes the filesystem become
> read-only. The only thing I can do is shut down Mysql, unmount the
> file system, remount it, and restart Mysql. I'm currently walking on
> eggshells, and the site that I'm trying to correct here is offline.
>
> Mysql is 5.0.22, normal CentOS 5 package.
>
> This file system was originally running on DRBD, but I've taken that
> out of the loop at this point, so this is just mounting a straight LVM
> partition. The file system is ext3. Myisamchk -o does the same
> thing.
>
> Any ideas for this?
>
Run fsck on the filesystem. It is probably marked as crashed.

--
Gerald L. Clark
Sr. V.P. Development
Supplier Systems Corporation
Unix since 1982
Linux since 1992

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]