Just to clarify, we¹ve not seen this problem with all environments. We¹ve only had this issue with this specific environment with this specific database with this set of data files in /var/lib/mysql. If we rebuild the database with mysqldump then the issue goes away. If this was the only environment we had to do this in, we might do just that, but we¹ve still got our staging and prod environments to deploy this change to. Our primary concern is that we cannot rebuild the databases in staging and prod using mysqldump and we can¹t predict if this problem will occur there since it doesn¹t seem predictable. On 7/2/15, 00:17, "