immich-app/immich
1
0
Fork 0
mirror of https://github.com/immich-app/immich.git synced 2026-02-05 08:41:28 +03:00
Code Issues 27 Packages Projects Releases 10 Wiki Activity

Storage template migration - unexpected behaviour #2648

New Issue
Closed
opened 2026-02-05 06:28:53 +03:00 by OVERLORD · 38 comments
OVERLORD commented 2026-02-05 06:28:53 +03:00
Owner
Copy Link

Originally created by @lmgithu on GitHub (Mar 22, 2024).

The bug

When I set a new template for the folder structure (switching from yyyy-mm-dd to yyyy-mm only) and run the storage template migration job, I see that 1) the job finished running 2) 80% of the folders now have a mix of yyyy-mm-dd and yyyy-mm folders with data in them).

I wanted to check why immich is not capable of transforming all folders and why there are leftovers? My other contern is whether this is breaking viewing the images and/or the database.

Desired outcome:

  • all folders on a file level should be in the new format ONLY

The OS that Immich Server is running on

Debian

Version of Immich Server

v1.98.2

Version of Immich Mobile App

v1.98.2

Platform with the issue

  • Server
  • Web
  • Mobile

Your docker-compose.yml content

standard

Your .env content

standard

Reproduction steps

1. set a new storage template
2. run the template migration job
3. not all folders are getting migrated, it is absolutely random

Additional information

No response

Originally created by @lmgithu on GitHub (Mar 22, 2024). ### The bug When I set a new template for the folder structure (switching from yyyy-mm-dd to yyyy-mm only) and run the storage template migration job, I see that 1) the job finished running 2) 80% of the folders now have a mix of yyyy-mm-dd and yyyy-mm folders with data in them). I wanted to check why immich is not capable of transforming all folders and why there are leftovers? My other contern is whether this is breaking viewing the images and/or the database. Desired outcome: - all folders on a file level should be in the new format ONLY ### The OS that Immich Server is running on Debian ### Version of Immich Server v1.98.2 ### Version of Immich Mobile App v1.98.2 ### Platform with the issue - [X] Server - [ ] Web - [ ] Mobile ### Your docker-compose.yml content ```YAML standard ``` ### Your .env content ```Shell standard ``` ### Reproduction steps ```bash 1. set a new storage template 2. run the template migration job 3. not all folders are getting migrated, it is absolutely random ``` ### Additional information _No response_
OVERLORD commented 2026-02-05 06:29:00 +03:00
Author
Owner
Copy Link

@lmgithu commented on GitHub (Mar 22, 2024):

some additional observations:

If i start another migration to migrate thumbnails for assets and faces to the latest folder structure, that job always runs on ALL my assets (100K+)... each time i see the huge number of assets that go down to zero but it seems it is not getting processed in reality as each time when i start the job it shows same high number.

@lmgithu commented on GitHub (Mar 22, 2024): some additional observations: If i start another migration to migrate thumbnails for assets and faces to the latest folder structure, that job always runs on ALL my assets (100K+)... each time i see the huge number of assets that go down to zero but it seems it is not getting processed in reality as each time when i start the job it shows same high number.
OVERLORD commented 2026-02-05 06:29:03 +03:00
Author
Owner
Copy Link

@alextran1502 commented on GitHub (Mar 22, 2024):

Can you help double-check the files in the older format yyyy-mm-dd to see if the path corresponds to the file's path that is shown in the UI?

image

@alextran1502 commented on GitHub (Mar 22, 2024): Can you help double-check the files in the older format `yyyy-mm-dd` to see if the path corresponds to the file's path that is shown in the UI? ![image](https://github.com/immich-app/immich/assets/27055614/33eec31b-85e9-4af2-b29e-e5320f0bfc35)
OVERLORD commented 2026-02-05 06:29:09 +03:00
Author
Owner
Copy Link

@lmgithu commented on GitHub (Mar 22, 2024):

I think the issue is now even bigger, I tried to check a file in that folder and one of them is there on the file system but NOT on the UI.. I don't see these images anymore :( In another case I do see as you do, it is on the UI as well and it still refers to the old folder (attached screenshot below)

Screenshot 2024-03-22 at 16 03 00

@lmgithu commented on GitHub (Mar 22, 2024): I think the issue is now even bigger, I tried to check a file in that folder and one of them is there on the file system but NOT on the UI.. I don't see these images anymore :( In another case I do see as you do, it is on the UI as well and it still refers to the old folder (attached screenshot below) ![Screenshot 2024-03-22 at 16 03 00](https://github.com/immich-app/immich/assets/164340256/cc6af321-bf53-4c9e-a70d-706ccc5f102c)
OVERLORD commented 2026-02-05 06:29:17 +03:00
Author
Owner
Copy Link

@lmgithu commented on GitHub (Mar 22, 2024):

If you need, I can share the logs and/or the file itself that it did not process. Let me know how I could help.

@lmgithu commented on GitHub (Mar 22, 2024): If you need, I can share the logs and/or the file itself that it did not process. Let me know how I could help.
OVERLORD commented 2026-02-05 06:29:24 +03:00
Author
Owner
Copy Link

@alextran1502 commented on GitHub (Mar 22, 2024):

NOT on the UI.

Can you use the search for file name to find that file to see if it returns in the search result. Please attach the screenshot of the file on the file system as well as the search result if you can

@alextran1502 commented on GitHub (Mar 22, 2024): > NOT on the UI. Can you use the search for file name to find that file to see if it returns in the search result. Please attach the screenshot of the file on the file system as well as the search result if you can
OVERLORD commented 2026-02-05 06:29:25 +03:00
Author
Owner
Copy Link

@alextran1502 commented on GitHub (Mar 22, 2024):

Also logs, on the server when you run the migration would be helpful, you can increase the log level to debug in the Server settings in the Administration page

@alextran1502 commented on GitHub (Mar 22, 2024): Also logs, on the server when you run the migration would be helpful, you can increase the log level to debug in the Server settings in the Administration page
OVERLORD commented 2026-02-05 06:29:30 +03:00
Author
Owner
Copy Link

@lmgithu commented on GitHub (Mar 22, 2024):

Will do and report back in an hour. How can I download/extract the log file?

@lmgithu commented on GitHub (Mar 22, 2024): Will do and report back in an hour. How can I download/extract the log file?
OVERLORD commented 2026-02-05 06:29:34 +03:00
Author
Owner
Copy Link

@alextran1502 commented on GitHub (Mar 22, 2024):

From the terminal, run docker logs immich_server or docker logs immich_microservices

@alextran1502 commented on GitHub (Mar 22, 2024): From the terminal, run `docker logs immich_server` or `docker logs immich_microservices`
OVERLORD commented 2026-02-05 06:29:39 +03:00
Author
Owner
Copy Link

@lmgithu commented on GitHub (Mar 22, 2024):

hi Alex,

Here are the results: searching for the image name on UI: no result. I can't take a screenshot as there is no results, it just shows my photo feed (I confirm it works for other image names). Screenshot of file system/location of the image: attached.
Screenshot 2024-03-22 at 19 30 00

Log:

immich_server_1            | [Nest] 6  - 03/22/2024, 6:25:05 PM   DEBUG [JobService] Handling command: queue=storageTemplateMigration,force=false
immich_redis_1             | 15:C 22 Mar 2024 18:05:08.034 * RDB: 0 MB of memory used by copy-on-write
immich_redis_1             | 1:M 22 Mar 2024 18:05:08.107 * Background saving terminated with success
immich_redis_1             | 1:M 22 Mar 2024 18:10:09.036 * 100 changes in 300 seconds. Saving...
immich_redis_1             | 1:M 22 Mar 2024 18:10:09.037 * Background saving started by pid 16
immich_redis_1             | 16:C 22 Mar 2024 18:10:09.161 * DB saved on disk
immich_redis_1             | 16:C 22 Mar 2024 18:10:09.162 * RDB: 0 MB of memory used by copy-on-write
immich_redis_1             | 1:M 22 Mar 2024 18:10:09.239 * Background saving terminated with success
immich_redis_1             | 1:M 22 Mar 2024 18:15:10.025 * 100 changes in 300 seconds. Saving...
immich_redis_1             | 1:M 22 Mar 2024 18:15:10.025 * Background saving started by pid 17
immich_redis_1             | 17:C 22 Mar 2024 18:15:10.052 * DB saved on disk
immich_redis_1             | 17:C 22 Mar 2024 18:15:10.052 * RDB: 0 MB of memory used by copy-on-write
immich_redis_1             | 1:M 22 Mar 2024 18:15:10.126 * Background saving terminated with success
immich_redis_1             | 1:M 22 Mar 2024 18:20:11.071 * 100 changes in 300 seconds. Saving...
immich_redis_1             | 1:M 22 Mar 2024 18:20:11.072 * Background saving started by pid 18
immich_redis_1             | 18:C 22 Mar 2024 18:20:11.098 * DB saved on disk
immich_redis_1             | 18:C 22 Mar 2024 18:20:11.098 * RDB: 0 MB of memory used by copy-on-write
immich_redis_1             | 1:M 22 Mar 2024 18:20:11.172 * Background saving terminated with success
immich_redis_1             | 1:M 22 Mar 2024 18:25:12.096 * 100 changes in 300 seconds. Saving...
immich_redis_1             | 1:M 22 Mar 2024 18:25:12.096 * Background saving started by pid 19
immich_redis_1             | 19:C 22 Mar 2024 18:25:12.120 * DB saved on disk
immich_redis_1             | 19:C 22 Mar 2024 18:25:12.120 * RDB: 0 MB of memory used by copy-on-write
immich_redis_1             | 1:M 22 Mar 2024 18:25:12.196 * Background saving terminated with success
immich_machine-learning_1  | [03/22/24 18:25:17] DEBUG    Checking for inactivity...                         
immich_machine-learning_1  | [03/22/24 18:25:27] DEBUG    Checking for inactivity...                         
immich_machine-learning_1  | [03/22/24 18:25:37] DEBUG    Checking for inactivity...                         
immich_machine-learning_1  | [03/22/24 18:25:47] DEBUG    Checking for inactivity...                         
immich_machine-learning_1  | [03/22/24 18:25:57] DEBUG    Checking for inactivity...                         
immich_machine-learning_1  | [03/22/24 18:26:07] DEBUG    Checking for inactivity...                         
immich_machine-learning_1  | [03/22/24 18:26:17] DEBUG    Checking for inactivity...                         
immich_machine-learning_1  | [03/22/24 18:26:27] DEBUG    Checking for inactivity...                         
immich_machine-learning_1  | [03/22/24 18:26:37] DEBUG    Checking for inactivity...
@lmgithu commented on GitHub (Mar 22, 2024): hi Alex, Here are the results: searching for the image name on UI: no result. I can't take a screenshot as there is no results, it just shows my photo feed (I confirm it works for other image names). Screenshot of file system/location of the image: attached. <img width="540" alt="Screenshot 2024-03-22 at 19 30 00" src="https://github.com/immich-app/immich/assets/164340256/c89d1413-0044-4832-b9da-9b9487d231df"> Log: ``` immich_server_1 | [Nest] 6 - 03/22/2024, 6:25:05 PM DEBUG [JobService] Handling command: queue=storageTemplateMigration,force=false immich_redis_1 | 15:C 22 Mar 2024 18:05:08.034 * RDB: 0 MB of memory used by copy-on-write immich_redis_1 | 1:M 22 Mar 2024 18:05:08.107 * Background saving terminated with success immich_redis_1 | 1:M 22 Mar 2024 18:10:09.036 * 100 changes in 300 seconds. Saving... immich_redis_1 | 1:M 22 Mar 2024 18:10:09.037 * Background saving started by pid 16 immich_redis_1 | 16:C 22 Mar 2024 18:10:09.161 * DB saved on disk immich_redis_1 | 16:C 22 Mar 2024 18:10:09.162 * RDB: 0 MB of memory used by copy-on-write immich_redis_1 | 1:M 22 Mar 2024 18:10:09.239 * Background saving terminated with success immich_redis_1 | 1:M 22 Mar 2024 18:15:10.025 * 100 changes in 300 seconds. Saving... immich_redis_1 | 1:M 22 Mar 2024 18:15:10.025 * Background saving started by pid 17 immich_redis_1 | 17:C 22 Mar 2024 18:15:10.052 * DB saved on disk immich_redis_1 | 17:C 22 Mar 2024 18:15:10.052 * RDB: 0 MB of memory used by copy-on-write immich_redis_1 | 1:M 22 Mar 2024 18:15:10.126 * Background saving terminated with success immich_redis_1 | 1:M 22 Mar 2024 18:20:11.071 * 100 changes in 300 seconds. Saving... immich_redis_1 | 1:M 22 Mar 2024 18:20:11.072 * Background saving started by pid 18 immich_redis_1 | 18:C 22 Mar 2024 18:20:11.098 * DB saved on disk immich_redis_1 | 18:C 22 Mar 2024 18:20:11.098 * RDB: 0 MB of memory used by copy-on-write immich_redis_1 | 1:M 22 Mar 2024 18:20:11.172 * Background saving terminated with success immich_redis_1 | 1:M 22 Mar 2024 18:25:12.096 * 100 changes in 300 seconds. Saving... immich_redis_1 | 1:M 22 Mar 2024 18:25:12.096 * Background saving started by pid 19 immich_redis_1 | 19:C 22 Mar 2024 18:25:12.120 * DB saved on disk immich_redis_1 | 19:C 22 Mar 2024 18:25:12.120 * RDB: 0 MB of memory used by copy-on-write immich_redis_1 | 1:M 22 Mar 2024 18:25:12.196 * Background saving terminated with success immich_machine-learning_1 | [03/22/24 18:25:17] DEBUG Checking for inactivity... immich_machine-learning_1 | [03/22/24 18:25:27] DEBUG Checking for inactivity... immich_machine-learning_1 | [03/22/24 18:25:37] DEBUG Checking for inactivity... immich_machine-learning_1 | [03/22/24 18:25:47] DEBUG Checking for inactivity... immich_machine-learning_1 | [03/22/24 18:25:57] DEBUG Checking for inactivity... immich_machine-learning_1 | [03/22/24 18:26:07] DEBUG Checking for inactivity... immich_machine-learning_1 | [03/22/24 18:26:17] DEBUG Checking for inactivity... immich_machine-learning_1 | [03/22/24 18:26:27] DEBUG Checking for inactivity... immich_machine-learning_1 | [03/22/24 18:26:37] DEBUG Checking for inactivity... ```
OVERLORD commented 2026-02-05 06:29:43 +03:00
Author
Owner
Copy Link

@alextran1502 commented on GitHub (Mar 22, 2024):

Just to make sure, can you drag-and-drop that file on the web to see if it successfully upload or it will say duplicated

@alextran1502 commented on GitHub (Mar 22, 2024): Just to make sure, can you drag-and-drop that file on the web to see if it successfully upload or it will say duplicated
OVERLORD commented 2026-02-05 06:29:46 +03:00
Author
Owner
Copy Link

@lmgithu commented on GitHub (Mar 22, 2024):

I tried, it said "skipped 1 duplicated asset"

@lmgithu commented on GitHub (Mar 22, 2024): I tried, it said "skipped 1 duplicated asset"
OVERLORD commented 2026-02-05 06:29:48 +03:00
Author
Owner
Copy Link

@alextran1502 commented on GitHub (Mar 22, 2024):

So it should be on the server, could it be in the archive view somehow?

@alextran1502 commented on GitHub (Mar 22, 2024): So it should be on the server, could it be in the archive view somehow?
OVERLORD commented 2026-02-05 06:29:53 +03:00
Author
Owner
Copy Link

@lmgithu commented on GitHub (Mar 22, 2024):

No, it is not there in the archive :(

@lmgithu commented on GitHub (Mar 22, 2024): No, it is not there in the archive :(
OVERLORD commented 2026-02-05 06:29:56 +03:00
Author
Owner
Copy Link

@alextran1502 commented on GitHub (Mar 22, 2024):

Can you confirm the visual of the image on that date,not just the file name?

@alextran1502 commented on GitHub (Mar 22, 2024): Can you confirm the visual of the image on that date,not just the file name?
OVERLORD commented 2026-02-05 06:30:00 +03:00
Author
Owner
Copy Link

@lmgithu commented on GitHub (Mar 22, 2024):

Yes I can, I can't see this image visually on the UI, despite it is on the file system.

@lmgithu commented on GitHub (Mar 22, 2024): Yes I can, I can't see this image visually on the UI, despite it is on the file system.
OVERLORD commented 2026-02-05 06:30:04 +03:00
Author
Owner
Copy Link

@alextran1502 commented on GitHub (Mar 22, 2024):

hmm strange, can you show me the search query you put in to search for the file name?

@alextran1502 commented on GitHub (Mar 22, 2024): hmm strange, can you show me the search query you put in to search for the file name?
OVERLORD commented 2026-02-05 06:30:07 +03:00
Author
Owner
Copy Link

@lmgithu commented on GitHub (Mar 22, 2024):

here you are:

Screenshot 2024-03-22 at 20 13 45

@lmgithu commented on GitHub (Mar 22, 2024): here you are: ![Screenshot 2024-03-22 at 20 13 45](https://github.com/immich-app/immich/assets/164340256/f6dd77cc-a73c-49ff-a9d6-e27f92240665)
OVERLORD commented 2026-02-05 06:30:10 +03:00
Author
Owner
Copy Link

@lmgithu commented on GitHub (Mar 22, 2024):

this works for any other filename btw and I can see the results

@lmgithu commented on GitHub (Mar 22, 2024): this works for any other filename btw and I can see the results
OVERLORD commented 2026-02-05 06:30:15 +03:00
Author
Owner
Copy Link

@alextran1502 commented on GitHub (Mar 22, 2024):

Try 5841? and did you tick on the archive button at the very bottom of the page?

@alextran1502 commented on GitHub (Mar 22, 2024): Try 5841? and did you tick on the archive button at the very bottom of the page?
OVERLORD commented 2026-02-05 06:30:17 +03:00
Author
Owner
Copy Link

@lmgithu commented on GitHub (Mar 22, 2024):

Do you know why certain folders/files were ignored? this is how my folders look like:

Screenshot 2024-03-22 at 20 16 07

Interestingly, until 2010 every folder looks OK... after that, it is fully random and mixed.

@lmgithu commented on GitHub (Mar 22, 2024): Do you know why certain folders/files were ignored? this is how my folders look like: ![Screenshot 2024-03-22 at 20 16 07](https://github.com/immich-app/immich/assets/164340256/9c6be797-163c-46c4-800f-9fbe63fc9e73) Interestingly, until 2010 every folder looks OK... after that, it is fully random and mixed.
OVERLORD commented 2026-02-05 06:30:21 +03:00
Author
Owner
Copy Link

@alextran1502 commented on GitHub (Mar 22, 2024):

I am not sure, we will have to look at this more in-depth. Thanks for the report

@alextran1502 commented on GitHub (Mar 22, 2024): I am not sure, we will have to look at this more in-depth. Thanks for the report
OVERLORD commented 2026-02-05 06:30:25 +03:00
Author
Owner
Copy Link

@lmgithu commented on GitHub (Mar 22, 2024):

Could I somehow force process folders again?

@lmgithu commented on GitHub (Mar 22, 2024): Could I somehow force process folders again?
OVERLORD commented 2026-02-05 06:30:28 +03:00
Author
Owner
Copy Link

@lmgithu commented on GitHub (Mar 22, 2024):

or at least "delete" these files somehow so i could reupload them?

@lmgithu commented on GitHub (Mar 22, 2024): or at least "delete" these files somehow so i could reupload them?
OVERLORD commented 2026-02-05 06:30:33 +03:00
Author
Owner
Copy Link

@alextran1502 commented on GitHub (Mar 22, 2024):

Can you check the Trash page to see if it is in it?

@alextran1502 commented on GitHub (Mar 22, 2024): Can you check the Trash page to see if it is in it?
OVERLORD commented 2026-02-05 06:30:36 +03:00
Author
Owner
Copy Link

@lmgithu commented on GitHub (Mar 22, 2024):

WIN, it was in the Trash! Sorry, this was such a noob issue. Now we "just" have the folder structure issue that it is fully random, I think there are no missing images. Do you have any guess what might be the issue and how to fix it?

@lmgithu commented on GitHub (Mar 22, 2024): WIN, it was in the Trash! Sorry, this was such a noob issue. Now we "just" have the folder structure issue that it is fully random, I think there are no missing images. Do you have any guess what might be the issue and how to fix it?
OVERLORD commented 2026-02-05 06:30:43 +03:00
Author
Owner
Copy Link

@alextran1502 commented on GitHub (Mar 22, 2024):

Do you have any guess what might be the issue and how to fix it?

The issue is that we don't move files that are already in the trash :P So it is working as expect

@alextran1502 commented on GitHub (Mar 22, 2024): > Do you have any guess what might be the issue and how to fix it? The issue is that we don't move files that are already in the trash :P So it is working as expect
OVERLORD commented 2026-02-05 06:30:50 +03:00
Author
Owner
Copy Link

@lmgithu commented on GitHub (Mar 22, 2024):

no, it was a SINGLE image... not all of them.

@lmgithu commented on GitHub (Mar 22, 2024): no, it was a SINGLE image... not all of them.
OVERLORD commented 2026-02-05 06:30:59 +03:00
Author
Owner
Copy Link

@lmgithu commented on GitHub (Mar 22, 2024):

99% of the files that were not moved are NOT in the Trash

@lmgithu commented on GitHub (Mar 22, 2024): 99% of the files that were not moved are NOT in the Trash
OVERLORD commented 2026-02-05 06:31:01 +03:00
Author
Owner
Copy Link

@alextran1502 commented on GitHub (Mar 22, 2024):

Then we will need to circle back and look at this!

@alextran1502 commented on GitHub (Mar 22, 2024): Then we will need to circle back and look at this!
OVERLORD commented 2026-02-05 06:31:02 +03:00
Author
Owner
Copy Link

@lmgithu commented on GitHub (Mar 22, 2024):

Thank you! Is there any way to "force" the migration again?

@lmgithu commented on GitHub (Mar 22, 2024): Thank you! Is there any way to "force" the migration again?
OVERLORD commented 2026-02-05 06:31:05 +03:00
Author
Owner
Copy Link

@lmgithu commented on GitHub (Mar 22, 2024):

e.g. if i switch back to yyyy-mm-dd again and switch again to yyyy-mm afterwards? or via CLI?

@lmgithu commented on GitHub (Mar 22, 2024): e.g. if i switch back to yyyy-mm-dd again and switch again to yyyy-mm afterwards? or via CLI?
OVERLORD commented 2026-02-05 06:31:10 +03:00
Author
Owner
Copy Link

@alextran1502 commented on GitHub (Mar 22, 2024):

Besides clicking on the template migration job, nothing else can be done.
Grab the server logs when you click on that button would be helpful as well

On Fri, Mar 22, 2024 at 2:37 PM lmgithu @.***> wrote:

Thank you! Is there any way to "force" the migration again?

—
Reply to this email directly, view it on GitHub
https://github.com/immich-app/immich/issues/8187#issuecomment-2015784865,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGONL7XHXBUFQKRR6RHAM3TYZSB75AVCNFSM6AAAAABFDCMSJSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJVG44DIOBWGU
.
You are receiving this because you commented.Message ID:
@.***>

--
Alex Tran

@alextran1502 commented on GitHub (Mar 22, 2024): Besides clicking on the template migration job, nothing else can be done. Grab the server logs when you click on that button would be helpful as well On Fri, Mar 22, 2024 at 2:37 PM lmgithu ***@***.***> wrote: > Thank you! Is there any way to "force" the migration again? > > — > Reply to this email directly, view it on GitHub > <https://github.com/immich-app/immich/issues/8187#issuecomment-2015784865>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AGONL7XHXBUFQKRR6RHAM3TYZSB75AVCNFSM6AAAAABFDCMSJSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJVG44DIOBWGU> > . > You are receiving this because you commented.Message ID: > ***@***.***> > -- Alex Tran
OVERLORD commented 2026-02-05 06:31:12 +03:00
Author
Owner
Copy Link

@danieldietzler commented on GitHub (Mar 23, 2024):

Just to make sure, are there assets in those leftover folders or are they all empty? In any case re-running the storage migration will attempt to fix potential issues, so that is certainly worth a shot!

@danieldietzler commented on GitHub (Mar 23, 2024): Just to make sure, are there assets in those leftover folders or are they all empty? In any case re-running the storage migration will attempt to fix potential issues, so that is certainly worth a shot!
OVERLORD commented 2026-02-05 06:31:13 +03:00
Author
Owner
Copy Link

@lmgithu commented on GitHub (Mar 23, 2024):

hi Daniel,

Unfortunately the folders are not empty, there are images in them. I run the migration job again for the original template format (yyyy-mm-dd) and it seems it reversed it to that properly, all yyyy-mm folders disappeared. So for that it seems to be working fine, but I don’t dare trying again for the yyyy-mm format again not to screw something. It would be great if somebody could check what might be the root cause so people could migrate properly.

If I can provide any further information, please let me know I will try to help.

@lmgithu commented on GitHub (Mar 23, 2024): hi Daniel, Unfortunately the folders are not empty, there are images in them. I run the migration job again for the original template format (yyyy-mm-dd) and it seems it reversed it to that properly, all yyyy-mm folders disappeared. So for that it seems to be working fine, but I don’t dare trying again for the yyyy-mm format again not to screw something. It would be great if somebody could check what might be the root cause so people could migrate properly. If I can provide any further information, please let me know I will try to help.
OVERLORD commented 2026-02-05 06:31:20 +03:00
Author
Owner
Copy Link

@danieldietzler commented on GitHub (Mar 23, 2024):

I am somewhat certain that running the migration on yyyy-mm again would have solved the issue as well, but of course I can't tell for sure. Many filesystem moves just happen to be flaky sometimes (most of the time actually lol).

@danieldietzler commented on GitHub (Mar 23, 2024): I am somewhat certain that running the migration on `yyyy-mm` again would have solved the issue as well, but of course I can't tell for sure. Many filesystem moves just happen to be flaky sometimes (most of the time actually lol).
OVERLORD commented 2026-02-05 06:31:23 +03:00
Author
Owner
Copy Link

@zackpollard commented on GitHub (Mar 23, 2024):

Hey! Would be great to get some more information on what's actually happening here. If you were willing to change the storage template structure again then it would be great if you could follow these steps and then provide us with the logs for your microservices instance.

1.) Change storage template to yyyy-mm format again, let the jobs finish.
2.) Check that the assets didn't all move correctly
3.) Try running the storage template migration job again manually
4.) Provide the full logs for the microservices container after this second job completes

Also if you are able to provide an example image that fails to move, that would be great.
Could you also share what filesystem you're using to store the asset files?

Cheers!

@zackpollard commented on GitHub (Mar 23, 2024): Hey! Would be great to get some more information on what's actually happening here. If you were willing to change the storage template structure again then it would be great if you could follow these steps and then provide us with the logs for your microservices instance. 1.) Change storage template to yyyy-mm format again, let the jobs finish. 2.) Check that the assets didn't all move correctly 3.) Try running the storage template migration job again manually 4.) Provide the full logs for the microservices container after this second job completes Also if you are able to provide an example image that fails to move, that would be great. Could you also share what filesystem you're using to store the asset files? Cheers!
OVERLORD commented 2026-02-05 06:31:27 +03:00
Author
Owner
Copy Link

@danieldietzler commented on GitHub (Apr 2, 2024):

@lmgithu ?

@danieldietzler commented on GitHub (Apr 2, 2024): @lmgithu ?
OVERLORD commented 2026-02-05 06:31:33 +03:00
Author
Owner
Copy Link

@jrasm91 commented on GitHub (Sep 7, 2024):

We've significantly improved the resiliency of this feature.

@jrasm91 commented on GitHub (Sep 7, 2024): We've significantly improved the resiliency of this feature.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
accessibility
changelog:enhancement
changelog:security
changelog:skip
changelog:translation
cli
date-time
documentation
external-library
format
good first issue
needs-answer
nice to have
sharing
tech-debt
📱mobile
🖥️web
🗄️server
🧠machine-learning
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: immich-app/immich#2648
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?