Folder becomes inaccessible after deleting a file inside it about mountpoint-s3 HOT 4 CLOSED

Hi @flivieri, thanks for raising the issue. Different linux distributions can package things in different ways and the release .rpm may not cover all of them. Workarounds include manually installing the binary or building from source.

In your case, though, it seems that Mountpoint was indeed installed. If you can mount successfully, the missing dependency is probably not an issue.

Could you provide more details on the errors you are seeing?

from mountpoint-s3.

Hello @passaro
Thanks for the explanation.

I thought my problem was related to the missing dependency.

What is happening: If I create a subfolder and access this new folder, everything is ok.
But, If I create a file inside/folder inside this new folder, and delete them after that, my folder becomes inaccessible.
Instead of "blank folder", seems like I'm inside a folder that no longer exists. I cannot list, create files, or type "cd .." to go back.

On S3, the folder no longer exists. At the moment I deleted the files inside the folder, the folder is also deleted by S3.
Example:

After that, I decide to delete the file inside the folder:

Is this a normal behavior?
Thank you.

from mountpoint-s3.

Yes, that is expected. Mountpoint maps key prefixes to directories, but if the last object with a key containing a prefix is deleted, it considers the directory to also have been deleted. From the Directory Operations section of the file system behavior documentation:

If Mountpoint later observes that there are no files existing for that directory in S3, Mountpoint will consider the directory to have been deleted.

from mountpoint-s3.

Hello @passaro
Sorry for bothering you and thanks for the explanation.
Best,

from mountpoint-s3.