Album folders in UPLOAD_LOCATION
Hi, I have a bunch of folders named after albums in my UPLOAD_LOCATION directory. I think these were created by an older version of immich, because my newer albums do not have their own folder. I'm assuming these are not safe to delete, but is there a way to migrate them to the way my new albums are?
8 Replies
:wave: Hey @Blobtoe,
Thanks for reaching out to us. Please carefully read this message and follow the recommended actions. This will help us be more effective in our support effort and leave more time for building Immich :immich:.
References
- Container Logs:
docker compose logs docs
- Container Status: docker ps -a docs
- Reverse Proxy: https://immich.app/docs/administration/reverse-proxy
- Code Formatting https://support.discord.com/hc/en-us/articles/210298617-Markdown-Text-101-Chat-Formatting-Bold-Italic-Underline#h_01GY0DAKGXDEHE263BCAYEGFJA
Checklist
I have...
1. :blue_square: verified I'm on the latest release(note that mobile app releases may take some time).
2. :blue_square: read applicable release notes.
3. :blue_square: reviewed the FAQs for known issues.
4. :blue_square: reviewed Github for known issues.
5. :blue_square: tried accessing Immich via local ip (without a custom reverse proxy).
6. :blue_square: uploaded the relevant information (see below).
7. :blue_square: 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)
Information
In order to be able to effectively help you, we need you to provide clear information to show what the problem is. The exact details needed vary per case, but here is a list of things to consider:
- Your docker-compose.yml and .env files.
- Logs from all the containers and their status (see above).
- All the troubleshooting steps you've tried so far.
- Any recent changes you've made to Immich or your system.
- Details about your system (both software/OS and hardware).
- Details about your storage (filesystems, type of disks, output of commands like fdisk -l and df -h).
- The version of the Immich server, mobile app, and other relevant pieces.
- Any other information that you think might be relevant.
Please paste files and logs with proper code formatting, and especially avoid blurry screenshots.
Without the right information we can't work out what the problem is. Help us help you ;)
If this ticket can be closed you can use the /close command, and re-open it later if needed.You probably have the
filename template enabled, right?
If yes, you could just start the job for storage template migration
This should move all old files before the filename template was enabled, to the new "more human readable structure"
I re-ran the template migration job, and the folders are still present. As a test, I moved one of the folders to another directory, and immich was still able to serve me the full image (via download), so I'm 90% sure these files are safe to delete.
If I choose one of the images in these folders and go to it's api url, for example:
/api/assets/6454bd57-bbbb-4714-ba0a-523e698c8bf7, I can see the originalPath is inside the library directory, not the external album directoryBasically, my question is it safe to delete a duplicate if it is not
originalPath?the duplicate I am considering is located at
(/usr/src/app)/{album_name}/{different_filename}.jpgIt’s not typically safe to manually delete from the internal library. That shouldn’t ever be needed
Yeah, I'm starting to doubt immich generated these folder at all lol. This might have been when I was messing with custom backup solutions a couple years ago. oh man. I will take full responsibility and kindly ignore your advice and move these files to another location (for now). Nothing seems to have broken so far and the images are still available through immich
Thanks you for taking the time to look into this, but I think it's a self-inflicted mess