How to rescan database storage index?

[OneFiveFour]

Hi, I fucked up and deleted/moved a few files directly in my storage folder instead via the WebUI. Now I learned that this is not good as the metadata in the database is not updated automatically. Luckily, I don't have much stored yet on my self-hosted instance. So my question is, if there is a way to let OpenCloud rebuild the database from the files as they are now within the storage folder?
I am using docker compose btw.
So worst case scenario would be to backup the current status of the storage folder, create a completley new container and re-upload everything - this time using the WebUI only.

[micbar]

There is no database. The storage is the source of truth for the posixfs and decomposedFS.

If you are using the decomposedS3 driver, blobs are in the s3 server and the metadata is on the decomposedFS.

[micbar]

But it requires the POSIX storage driver.

DecomposedFS or DecomposedS3 cannot work.__

[iamavolk]

PosixFS driver seems to be the default for 4.0.0 and this is what is set up in my case, right. Yet the issue it still there. Does anything besides STORAGE_USERS_POSIX_WATCH_FS need to be set manually? Something like STORAGE_USERS_POSIX_WATCHER=inotify?

[iamavolk]

It seems like /var/lib/opencloud/storage/users/users/<existing user UUID>/<file ID, presumably> is hardcoded somewhere.

The issue is when a file is modified externally, there's an xattr.get - related posixFS driver request that errors with the aforementioned path (with the message "failed to assimilate item")
So, the driver tries to find the file, fails (because the path doesn't exist) with the web UI sending 500 reply as a consequence.

The actual path is /mnt/storage/opencloud/opencloud-data/storage/users/users/<UUID>/

[micbar]

@aduffeck or @dragonchaser may help you

[iamavolk]

I'll retract what I've just written. Opencloud runs in a container in my case so it makes sense that something is off, and if a host user modifies the file things will most likely just break. If modified from within the container, it appears that everything is consistent.

upd: I think the problem is inode replacement. Nothing to do with opencloud proper.