Unusual mysql frm and idb files -
i have innodb_file_per_table option enabled have .frm , .ibd file each table. what's unusual there files appear temporary tables on filesystem:
/db/mysql$ ls <snip> #sql2-25fe-5.frm #sql2-25fe-5.ibd #sql2-55f4-73.frm #sql2-55f4-73.ibd #sql-55f6_13b626.ibd #sql-6abe_e3.ibd </snip>
one of them rather large i'd rid of them if it's safe. tried dropping them regular , temporary tables didn't work either way.
drop table `#sql2-25fe-5`; drop temporary table `#sql2-25fe-5`;
any ideas? thanks
just clear out:
dumping , reloading tables freed space wanted (an innobackupex backup & restore did not work). believe these permanent temporary tables result of 1 of 2 bugs have been fixed in mysql:
innodb: if server crashed @ precise moment during alter table operation rebuilt clustered index innodb table, original table inaccessible afterward. example of such operation alter table ... add primary key fix preserves original table if server halts during operation. might still need rename .ibd file manually restore original table contents: in mysql 5.6 , higher, rename #sql-ib$new_table_id.ibd table_name.ibd within database directory; prior mysql 5.6, temporary file rename table_name#1 or #2. (bug #14669848)
https://dev.mysql.com/doc/relnotes/mysql/5.5/en/news-5-5-30.html
or
innodb: update statements in error occurred, possible temporary file opened during update not closed. (bug #15978766)
https://dev.mysql.com/doc/relnotes/mysql/5.5/en/news-5-5-32.html
Comments
Post a Comment