Jellyfin Forum
Library Scan - Printable Version

+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+---- Forum: Media Scanning & Identification (https://forum.jellyfin.org/f-media-scanning-identification)
+---- Thread: Library Scan (/t-library-scan)

Pages: 1 2


RE: Library Scan - Jedich - 2025-04-01

(2025-04-01, 05:14 PM)TheDreadPirate Wrote: Additionally, you should disable the startup job called "Cleanup collections and playlists".  Dashboard > Scheduled Tasks > Cleanup collections and playlists.  Remove the startup trigger.

Done. Thanks


(2025-04-01, 05:14 PM)TheDreadPirate Wrote: If you have real time monitoring enabled, you should disable it.
None i have extra activated. Or you're meaning one of the Options within JellyFin?

Thats my Shedules.
[Image: 1.png]


RE: Library Scan - TheDreadPirate - 2025-04-01

Real time monitoring is a setting in each library.


RE: Library Scan - Jedich - 2025-04-02

Yes, thats activated by default and should be active. Like its said: Changes to files are processed immediately on supported file systems. (google translated)

Question is when all works fine at the first time, why its not anymore? I didnt do nothing in the Setup only added Jellystat. And btw JellyStat has also an active monitoring i think. I shutdown JellyStat, but its still the same.

Also the Log says again:
System.IO.IOException: The configured user limit (8192) on the number of inotify watches has been reached, or the operating system failed to allocate a required resource.
But to other Libraries: [INF] [89] Emby.Server.Implementations.IO.LibraryMonitor: Watching directory "/media1/..."

Is there any option i can set the number of inotify higher?
and what about the allocating a required resource? what is that mean?


RE: Library Scan - TheDreadPirate - 2025-04-02

When you are using network storage, real time monitoring should be DISABLED. With NFS, it straight up doesn't work AFAIK. With SMB the default inotify limits are insufficient for a typical Jellyfin library.

You can increase the limit of inotify watches, but I don't recommend it.

https://www.suse.com/support/kb/doc/?id=000020048

If you need more frequent scans, decreasing the interval of the library scan task is my recommendation. The default is every 12 hours.


RE: Library Scan - Jedich - 2025-04-02

so in short:
Real Time Monitoring of each Library should be disabled.
The only thing that scan the Library then is the Shedule thats set to 12hours, bc of a large Library.

Why not incrase the Limit of inotify watches? Had bad Experience with that? or heard something bad about it?

Some of my Libraries are still watched:
[2025-03-31 20:41:13.355 +00:00] [INF] [128] Emby.Server.Implementations.IO.LibraryMonitor: Watching directory "/media1/...1"
[2025-03-31 20:41:13.355 +00:00] [INF] [148] Emby.Server.Implementations.IO.LibraryMonitor: Watching directory "/media1/...2"

Some not, so increasing the inotify could be the solution, but i dunno why this isnt recommended.


RE: Library Scan - TheDreadPirate - 2025-04-02

Each inotify watcher uses a fixed amount of memory. Increasing the number of inotify watchers increases memory usage on the server hosting the network share. Depending on how large your library is, that could mean hundreds of MBs or GBs more memory usage to have enough inotify watchers for your library. Not sure if there is any CPU overhead associated with that.

The default 12 hour schedule for the library scan job is just an arbitrary interval. Most library updates should only take a few minutes to complete, but can take longer if you add a lot of new content at once or you enabled chapter image extraction and trickplay creation on library scan.

It is up to you to determine what is an appropriate interval both for your needs and for your system's capabilities.


RE: Library Scan - Jedich - 2025-04-02

Memory and CPU are both fine and most of the time sleepin. Even if then only CPU goes a bit high, but not really that i would get afraid of.

Normally i dont want to setup any files for increasing some things like that. i like it whens it works from scratch with setting up only JF Settings, not outside JF stuff like inotify.

Yeah i got a big library.
So i try this Setup now and see if this maybe works:
- All Libraries has a disabled real time monitoring
- Only 2 Shedules for Media Scan are activ: 1) Daily at 00:00 and 2) Every 15min with a Limit of 1 hour.

15min may be to often, but thats just so see if this works /scan the Library.


RE: Library Scan - TheDreadPirate - 2025-04-02

inotify is not something you add. It is built into Linux and is the mechanism that Jellyfin uses for real time monitoring. I see you have a Synology NAS, which I'm assuming has all your content. Because of their OS is pretty locked down, even though it is Linux, I'm not sure you could even increase the number of inotify watchers.


RE: Library Scan - Jedich - 2025-04-02

(2025-04-02, 06:41 PM)TheDreadPirate Wrote: inotify is not something you add.  It is built into Linux and is the mechanism that Jellyfin uses for real time monitoring.
 
yeah i got it. what i was trying to say was i'm not a fan of setting up any other options outside JF. I play with JF and try to get it well as i had plex before. At Plex there was no need to change anything within my NAS regarding to the Scan Issue. tbh yes, even Plex didnt scan my Library when i put some new Stuff into it, but the Shedule works without any issue, and that was okay for me.
I would be happy if this would work with JF at least.

(2025-04-02, 06:41 PM)TheDreadPirate Wrote: I see you have a Synology NAS, which I'm assuming has all your content.
 
Right, all my Contents are on my NAS.

(2025-04-02, 06:41 PM)TheDreadPirate Wrote: Because of their OS is pretty locked down, even though it is Linux, I'm not sure you could even increase the number of inotify watchers.
 
Maybe, i dont know and these would be my last option if JF cant scan my Library properly with the Shedule i set.

btw English is not my native language, sorry if there's any misunderstood.