2025-05-17, 12:05 PM
(This post was last modified: 2025-05-17, 12:12 PM by Scrat134. Edited 1 time in total.)
Jellyfin v10.10.7
Synology Container Manager / Docker (No Mem Limits / Med CPU priority)
DSM 7.2.2, Intel Celeron J4125 2GHz, 18GB RAM
8TB HDD NAS Storage (RAID)
I have a question regarding Metadata Manager stability, or potentially maximum limitations.
I have several libraries within my Jellyfin setup. I use these to manage images and videos, utilising the "Home Videos and Photos" content type. Most of these libraries I consider to be of medium size, which is hardly a technical description I appreciate... Each library contains a number of subdirectories, and within these the image and video files are organised.
For the most libraries, when selecting these and updating the meta locking setting(s) within Administration > Metadata Manager. I select the library name in the left-hand menu, scroll down on the right-hand pane select the "Lock this item to prevent future changes" checkbox, and save, after a few moments the screen reloads and library itself, as well as the child/dependant directories housed within show up in the left-hand menu with a padlock beside their names, so I presume they're all locked as expected - happy days.
However, I have one library which is significantly larger than the others. This library when edited via Metadata Manager behaves differently. The library in question is around 3TB in size, containing around 350 subdirectories and 64k files - a mixture of images and videos.
When I click on the large library's name in Metadata Manager's left-hand menu, scroll down on the right-hand pane, select the "Lock this item to prevent future changes" and save, I get the blue-coloured loading pinwheel overlay, and essentially it seems to just 'hang' there.
Several hours later, looking at Resource Monitor within DSM on my Synology there is very little, if any, CPU etc activity taking place, so I suspect that there's just nothing happening. Eventually returning to the Metadata Manager page, which is still complete with the blue-coloured loading pinwheel overlay, I refresh the page (I'm using desktop web on Google Chrome v136.0.7103.114) and upon reloading of the Metadata Manager page, clicking the large library's name in the left-hand menu, the listing of child/dependant directories expands to show that some are now locked, while others remain unlocked.
The selection of locked vs unlocked child/dependant directories seems to be random, there is no obvious ordering to this.
I have repeated the above process several times, each time to no avail.
Essentially, I would just like to ensure that all are "locked" to prevent further metadata changes, but short of trawling through hundreds of subdirectories doing one at a time, I seem to be stuck.
Is there any known limitation to the size of library that Jellyfin (or Metadata Manager specifically) can handle?
Is there any way of enabling this (metadata locking) via any other means - terminal etc?
I thought it was worth reaching out, before I reorganise my library!
Cheers.
Synology Container Manager / Docker (No Mem Limits / Med CPU priority)
DSM 7.2.2, Intel Celeron J4125 2GHz, 18GB RAM
8TB HDD NAS Storage (RAID)
I have a question regarding Metadata Manager stability, or potentially maximum limitations.
I have several libraries within my Jellyfin setup. I use these to manage images and videos, utilising the "Home Videos and Photos" content type. Most of these libraries I consider to be of medium size, which is hardly a technical description I appreciate... Each library contains a number of subdirectories, and within these the image and video files are organised.
For the most libraries, when selecting these and updating the meta locking setting(s) within Administration > Metadata Manager. I select the library name in the left-hand menu, scroll down on the right-hand pane select the "Lock this item to prevent future changes" checkbox, and save, after a few moments the screen reloads and library itself, as well as the child/dependant directories housed within show up in the left-hand menu with a padlock beside their names, so I presume they're all locked as expected - happy days.
However, I have one library which is significantly larger than the others. This library when edited via Metadata Manager behaves differently. The library in question is around 3TB in size, containing around 350 subdirectories and 64k files - a mixture of images and videos.
When I click on the large library's name in Metadata Manager's left-hand menu, scroll down on the right-hand pane, select the "Lock this item to prevent future changes" and save, I get the blue-coloured loading pinwheel overlay, and essentially it seems to just 'hang' there.
Several hours later, looking at Resource Monitor within DSM on my Synology there is very little, if any, CPU etc activity taking place, so I suspect that there's just nothing happening. Eventually returning to the Metadata Manager page, which is still complete with the blue-coloured loading pinwheel overlay, I refresh the page (I'm using desktop web on Google Chrome v136.0.7103.114) and upon reloading of the Metadata Manager page, clicking the large library's name in the left-hand menu, the listing of child/dependant directories expands to show that some are now locked, while others remain unlocked.
The selection of locked vs unlocked child/dependant directories seems to be random, there is no obvious ordering to this.
I have repeated the above process several times, each time to no avail.
Essentially, I would just like to ensure that all are "locked" to prevent further metadata changes, but short of trawling through hundreds of subdirectories doing one at a time, I seem to be stuck.
Is there any known limitation to the size of library that Jellyfin (or Metadata Manager specifically) can handle?
Is there any way of enabling this (metadata locking) via any other means - terminal etc?
I thought it was worth reaching out, before I reorganise my library!
Cheers.