A developer can repeatedly fetch a new database without having ghost tables nor bloating the VMs disk space
I stopped being able to sync an old (non-Drutopia) from live to the local environment. The first step of trying to save a backup copy of the database failed:
./vendor/bin/drush sql-dump > /tmp/paranoia.sql Drush command terminated abnormally due to an unrecoverable error. [error] mysqldump: Got errno 32 on write
There wasn't much space left in the root / of the VM, just 500MB.
I ran ls | xargs du -sh
following the largest folder (6.4GB) until i reached the culprit, in /var/lib/mysql and weighing in at the full 6.4GB all by itself, that old devil we know so well, ibdata1.
This may
-
The local database is backed up. -
The local database is deleted (otherwise tables that exist on local, but not on live, are still there after sync) -
The local database is recreated and synced to -
All this happens without an evergrowing file anywhere in MySQL's vile innards. This is supposed to be fixed but i'm happy for Drutopia to switch to PostgreSQL if MySQL/MariaDB haven't really fixed this.