Comment 4 for bug 1594806

I also tried the ignore-db-dir=lost+found, however it didn't work.
The reason is that the postinst script of the package checks if the mysql datadir is empty by issuing "ls -A" on it. If it is not empty, it won't initialize the database and just skip to starting mysql.
The sanity script that is run before every mysql start will then also fail to initialize the database, because it creates the mysql directory in the datadir. But then mysqld --initialize complains that the datadir is not empty.
mysqld --initialize does honour the ignore-db-dir variable and therefor does not complain about the lost+found directory, but ignoring the mysql db dir does not seem to be a viable solution.

We're going to set the mountpoint to /var/lib instead of /var/lib/mysql as a workaround for this issue.