← Back to team overview

maria-discuss team mailing list archive

Re: Why MyISAM as default engine for system tables ?

 


Am 06.06.2018 um 16:21 schrieb Roberto Spadim:
> Last time i had a innodb problem i changed all innodb to one file per table

which don't help anything given the shared tablespace, that below is
from a crash in 2009 and all that "helpful" pages don't work at all
after you have deleted the #file weeks later since it had a old
timestamp and so looked as a orphaned tempfile

the only thing you gain with per-table is that you can shrink/optimize
the tables instead never reclaim space after 20 GB was deleted

and that is why i don't want the system-tables as innodb at all, they
typically don't crash because few to no write access and even if the
restore is a simple rsync from one of the rsnapshot-backups

2018-06-06 17:45:27 140034181385856 [ERROR] InnoDB: Operating system
error number 2 in a file operation.
2018-06-06 17:45:27 140034181385856 [ERROR] InnoDB: The error means the
system cannot find the path specified.
2018-06-06 17:45:27 140034181385856 [ERROR] InnoDB: If you are
installing InnoDB, remember that you must create directories yourself,
InnoDB does not create them.
2018-06-06 17:45:27 140034181385856 [ERROR] InnoDB: Cannot open datafile
for read-only: './dbmail/#sql2-704-271.ibd' OS error: 71
2018-06-06 17:45:27 140034181385856 [ERROR] InnoDB: Operating system
error number 2 in a file operation.
2018-06-06 17:45:27 140034181385856 [ERROR] InnoDB: The error means the
system cannot find the path specified.
2018-06-06 17:45:27 140034181385856 [ERROR] InnoDB: If you are
installing InnoDB, remember that you must create directories yourself,
InnoDB does not create them.
2018-06-06 17:45:27 140034181385856 [ERROR] InnoDB: Could not find a
valid tablespace file for `dbmail/#sql2-704-271`. Please refer to
http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html
for how to resolve the issue.
2018-06-06 17:45:27 140034181385856 [Warning] InnoDB: Ignoring
tablespace for `dbmail`.`#sql2-704-271` because it could not be opened.
2018-06-06 17:45:27 140034181385856 [Note] InnoDB: 128 out of 128
rollback segments are active.
2018-06-06 17:45:27 140034181385856 [Note] InnoDB: Creating shared
tablespace for temporary tables
2018-06-06 17:45:27 140034181385856 [Note] InnoDB: Setting file
'./ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2018-06-06 17:45:27 140034181385856 [Note] InnoDB: File './ibtmp1' size
is now 12 MB.
2018-06-06 17:45:27 140034181385856 [Note] InnoDB: Waiting for purge to
start
2018-06-06 17:45:27 140034181385856 [Note] InnoDB: 5.7.22 started; log
sequence number 2250847037053
2018-06-06 17:45:27 140033147254528 [Note] InnoDB: Loading buffer
pool(s) from /Volumes/dune/mysql_replication/ib_buffer_pool
2018-06-06 17:45:27 140033147254528 [Note] InnoDB: Cannot open
'/Volumes/dune/mysql_replication/ib_buffer_pool' for reading: No such
file or directory
2018-06-06 17:45:27 140034181385856 [Note] Server socket created on IP:
'0.0.0.0'.
2018-06-06 17:45:27 140034181385856 [Note] Reading of all Master_info
entries succeded


Follow ups

References