Bug #42676 mysqld should ignore folders called "lost+found"
Submitted: 8 Feb 2009 2:42 Modified: 8 Feb 2009 10:30
Reporter: Noah E Email Updates:
Status: Duplicate Impact on me:
Category:MySQL Server Severity:S3 (Non-critical)
Version:5.1.31 OS:Linux (Redhat ES 4 X86_64)
Assigned to: CPU Architecture:Any

[8 Feb 2009 2:42] Noah E
Linux's ext3 file system always creates a lost+found folder on the root of every disk partition. I have MYSQL's data folder located on the root on its own partition.

When MYSQL starts, it always displays an non-fatal error in the logs:
[ERROR] lost+found is not a valid database or something like this

And then I seem to have this annoying phantom database now which keeps appearing (see below):

mysql> show databases;
| Database            |
| information_schema  |
| #mysql50#lost+found |
| mysql               |
| test                |
| tmp                 |

So basically, kind of like windows' "thumbs.db", mysql should be hardcoded to ignore "lost+found". (in my humble opinion)

Just a silly annoyance, but very simple to fix.

How to repeat:
MYSQL's data folder being located on the root of any ext3 mount.

Suggested fix:
Well I could delete the lost+found folder, but I'm not sure the file system will like that, and it will likely just recreate it at some point.
[8 Feb 2009 8:36] Daniel Fischer
This is a duplicate of bug#22615.
[8 Feb 2009 10:30] Noah E
Sorry :)