Offlined Files not being removed.

[rustic estuary]

I'm running Immich 1.116.2 and recently repathed some of my volume mounts to have a single mount higher up the directory structure instead of multiple lower level mounts (mounting MEDIA instead of MEDIA>Events, MEDIA>Trips etc.)

After a full rescan, all of my images from both the new pathing and old pathing are showing up, meaning I have a double up of everything, except all of the old ones are obviously showing as offline, yet they aren't showing up in trash unless I manually delete them. They also still show up in Folder view under the previous structure, as well as in my Tags. I've re-run the Library Job twice to no avail.

[quaint ridge]

:wave: Hey @rustic estuary,

Thanks for reaching out to us. Please follow the recommended actions below; this will help us be more effective in our support effort and leave more time for building Immich .

References

• Container Logs: docker compose logs docs
• Container Status: docker compose ps docs
• Reverse Proxy: https://immich.app/docs/administration/reverse-proxy

Checklist

1. :ballot_box_with_check: I have verified I'm on the latest release(note that mobile app releases may take some time).
2. :ballot_box_with_check: I have read applicable release notes.
3. :ballot_box_with_check: I have reviewed the FAQs for known issues.
4. :ballot_box_with_check: I have reviewed Github for known issues.
5. :ballot_box_with_check: I have tried accessing Immich via local ip (without a custom reverse proxy).
6. :ballot_box_with_check: I have uploaded the relevant logs, docker compose, and .env files, making sure to use code formatting.
7. :ballot_box_with_check: I have tried an incognito window, disabled extensions, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable

(an item can be marked as "complete" by reacting with the appropriate number)

If this ticket can be closed you can use the /close command, and re-open it later if needed.

[simple sky]

cc @wet dragon

[rustic estuary]

My apologies, there appears to already be an issue open on Github by someone else. Sounds like you guys are working very hard already!