Skip to content
This repository has been archived by the owner on Jun 10, 2020. It is now read-only.

Lost+found directory inside /var/lib/mysql #10

Closed
richard-julien opened this issue Jun 5, 2017 · 2 comments
Closed

Lost+found directory inside /var/lib/mysql #10

richard-julien opened this issue Jun 5, 2017 · 2 comments
Assignees

Comments

@richard-julien
Copy link

I finally successfully deploy on GKE with SSD volume instead of glusterFS.
I'm able to connect but i noticed a schema named "#mysql50#lost+found and some logs

2017-06-05 20:49:17 140214132201728 [Note] mysqld: ready for connections.
Version: '10.1.20-MariaDB'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MariaDB Server
2017-06-05 20:49:21 140214130744064 [ERROR] Invalid (old?) table or database name 'lost+found'
2017-06-05 20:49:31 140214130744064 [ERROR] Invalid (old?) table or database name 'lost+found'
2017-06-05 20:49:41 140214130744064 [ERROR] Invalid (old?) table or database name 'lost+found'
2017-06-05 20:49:51 140214130744064 [ERROR] Invalid (old?) table or database name 'lost+found'

Any idea on this subject ?

Thanks.

@tongpu
Copy link
Member

tongpu commented Jun 6, 2017

These errors can be removed by adding ignore-db-dir=lost+found to the configuration. I'll update the container scripts accordingly.

@tongpu
Copy link
Member

tongpu commented Jun 6, 2017

@richard-julien The docker image on Docker Hub has been updated and the errors should be gone from the logs.

@tongpu tongpu closed this as completed Aug 15, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants