Join GitHub today
Lazy shared storage heII: ghost mounts #26001
Found through #25977
404 not found for PROPFIND, folder "sub" can be created.
Cannot create folder "sub" as "user1".
9.1.1RC1 / stable9.1
The problem here is that due to lazy initialization, the mount system thinks that the mount is there until it gets initialized later. Then it turns out it's not supposed to be there but is still registered. So creating a folder with the same name fails.
With a local change I'm able to make the PROPFIND return 404.
Ideally the mount manager should have a way to query mount validity.
Now a quick but awful hack would be to check all file operations that would target a ghost mount, and add an additional check there.
Idea: let's see if I can pre-filter the shared mounts in the mount provider.