[MDEV-8572] corrupted table and stale .TMM file during optimize Created: 2015-08-05  Updated: 2015-08-06  Resolved: 2015-08-06

Status: Closed
Project: MariaDB Server
Component/s: Admin statements, Storage Engine - Aria, Storage Engine - MyISAM
Affects Version/s: 10.0.19
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Fustini Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Environment:

Linux CentOS release 6.4 (Final) on Rhev 3.3 Vm



 Description   

Hi,
we migrated all db server form mysql 5.1 to mariadb 10.0.19 and now we found randomly after optimize of all dbs weekly with command
mysqlcheck --auto-repair --flush -Ao
we find a corrupted myisam tables (before optimize we are sure that tables are ok because no log is present in optimize log that warn about problem on table) and a relative .tmm file.
We have to delete .tmm file and repair the table because if mysqlcheck pass skip this tables
Thank you very much



 Comments   
Comment by Elena Stepanova [ 2015-08-06 ]

Thanks.
Since Marc has already created a bug report about it (MDEV-8571), I'm adding your description as a comment there, so we could track everything in one place.

Generated at Thu Feb 08 07:28:09 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.