-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Storage migration complains about non-existent sidecars #6704
Comments
cc @simulot, I think this may have been an immich-go bug in the past, right? |
On further research, I have 5 images (out of ~50k) that seem to have an unmigrated sidecar file from upload/upload. My upload/ folder does not contain any files, just empty folders. It's not clear to me that an issue in immich-go would lead to this kind of database error - whatever the source of the missing XMP files, shouldn't Immich check for the existence of said file before loading it into the DB?
It seems to appear that both of these issues would be fixed (sort of) by draft PR #6293 - this would not fix the missing data, but it would fix the reference to non-existent files. |
immich-go used to create XMP files from google photo import. As far as I know this is fixed since ... long. (i need to dig into commits) But in this case, I think that the immich server just check the existence of an XMP files |
I believe we handle deleted xmp files now. |
The bug
Non-existent sidecar files are referenced in the database.
The OS that Immich Server is running on
Docker on Debian 12
Version of Immich Server
v1.93.3
Version of Immich Mobile App
n/a
Platform with the issue
Your docker-compose.yml content
n/a
Your .env content
Reproduction steps
Additional information
The immich-microservices logfiles will contain lines like:
I can confirm based on backups that this file did not have an XMP associated with it. When reviewing storage-template.service.ts , it looks like it might try to move a sidecar regardless of if it exists or not - not really sure.
Postgres reports:
These images were uploaded using immich-go, so it's possible that it somehow create a false XMP path? I'm unsure how that all works.
The text was updated successfully, but these errors were encountered: