"lost+found" folder on volume cause unexpected behaviour

pipech

PROOP

3 months ago

In my case it create error log on mariadb.

2025-09-11  2:11:41 0 [Note] InnoDB: Buffer pool(s) load completed at 250911  2:11:41
2025-09-11  2:11:41 4 [ERROR] Invalid (old?) table or database name 'lost+found'
2025-09-11  2:11:41 4 [ERROR] Invalid (old?) table or database name 'lost+found'
2025-09-11  2:11:41 4 [ERROR] Invalid (old?) table or database name 'lost+found'

Solved

6 Replies

Railway

BOT

3 months ago

Hey there! We've found the following might help you get unblocked faster:

If you find the answer from one of these, please let us know by solving the thread!

brody

EMPLOYEE

3 months ago

Hello,

Please use the recommended template for MariaDB; it comes correctly configured so that the standard Linux lost+found directory is not an issue.

https://railway.com/deploy/Onvy0F

It also comes with authentication enabled.

Status changed to Awaiting User Response Railway • 3 months ago

pipech

PROOP

3 months ago

Oh that was fast, thank you!

Status changed to Awaiting Railway Response Railway • 3 months ago

Status changed to Solved pipech • 3 months ago

pipech

PROOP

3 months ago

May I ask what make the template not having an issues with lost+found, are there any command or variable I can add to make mine works?

Status changed to Awaiting Railway Response Railway • 3 months ago

brody

EMPLOYEE

3 months ago

It might be the fact that the template deploys MariaDB 12 and you were deploying MariaDB 10. They may have simply updated the database since version 10 to ignore the standard Linux folder.

I know that old versions of MySQL got caught up with the existence of a lost+found folder.

Status changed to Awaiting User Response Railway • 3 months ago

pipech

PROOP

3 months ago

Noted, thank you.

Status changed to Awaiting Railway Response Railway • 3 months ago

Status changed to Solved pipech • 3 months ago