Problems with a "lost+found"-Folder

Hello! I’m working on a new-to-me site that is currently running Kirby 3.

Our Kirby is now running in a docker container which is deployed on a kubernetes cluster. To persist our data, we have two PVCs for content and accounts. These are using (as I have been told) EXT4 as filesystem.

I’ve discovered two issues:

  • We now have a unlisted page “lost+found” in the backend.
  • The initial installation did not work, instead of sending me to panel/installation, I was immediatly redirected to panel/login because there was already that folder inside of site/accounts and it was interpreted as an existing user.

The folder seems to be generated by Linux and can’t be deleted, as far as I’ve been researching by now. Now I’m not sure if this is a problem on Kirbys side or if I have to talk to Ops again for a solution.

So for now I’m just looking for some input. If this is a kirby-problem I’m happy to write an issue on Github.

This would be something to talk to your hosting about as its a server config thing. I am suprised it is creating the lost and found directory inside the accounts folder though, as my understanding is there should only be one of these folders in the root of the ext4 volume.

Essentially its to do with operating system file recovery and system inegrity handled by the linux fschk command. As such this is not something under the control of Kirby and will need looking into by your host.

Thank you. I’m going to talk to the Ops-Guys again.