----- Original Message -----
> From: "Brent Clark" <brentgclarklist@stripped>
> Mar 26 14:43:54 xyz-web02 mysqld: 120326 14:43:54 [ERROR]
> /usr/sbin/mysqld: Table './db/comm_opens' is marked as crashed and should be
That needs a 'repair table' command; probably because the snapshot was taken while the
tables were open.
> Mar 26 14:43:54 xyz-web02 mysqld: 120326 14:43:54 [Warning] Checking table:
> Mar 26 14:43:54 xyz-web02 mysqld: 120326 14:43:54 [ERROR] 1 client is using or hasn't
> closed the table properly
Pretty harmless; a client indeed didn't close the table properly - you snapshotted it
while open :-) Again, repair table.
You may want to issue "flush tables with read lock" just before you take the snapshot.
Must keep that session open during the snapshot (it'll temporarily put the database in
read-only mode), when the snapshot is complete issue "unlock tables" and close the
Mind that, while "probably good enough", that doesn't 100% silence the database - InnoDB
in particular has background processes that just keep going even though you flushed and
locked all tables. Short of third-party solutions, shutdown is the only surefire way to
take fully consistent backups of a MySQL instance.
Bier met grenadyn
Is als mosterd by den wyn
Sy die't drinkt, is eene kwezel
Hy die't drinkt, is ras een ezel