Add/Del Folder in One Library Triggers Scans of All Libraries

[SideCar 4]

This is more of an annoyance than a bug but it really should be corrected:

Any changes to the folder list of a library - either additions or deletions - rightfully triggers a scan. However, the resulting scan includes ALL libraries, not just the one that got the changes. This results in a frustrating amount of time wasted scanning libraries that don't need it. Only the library that was changed should have a scan triggered.

This behavior also effectively overrides the 'Enable real time monitoring' setting for all libraries as even libraries which have real-time monitoring disabled (because I DON'T want them scanned) are included in the scan triggered by a folder change.

Again, this is just an annoyance as it doesn't result in any data loss or other catastrophic consequence. It would just be really nice if only the library with changes got scanned so you don't have to sit around and wait 30 minutes for 180Tb of hard drive to get needlessly churned through.

Thanks.

[Luke 42078]

Hi, can you please provide a specific example?

How to Report a Problem

Thanks.

[Happy2Play 9780]

But you are making changes to the library.  So I would assume the integrity of the remaining folder should be checked. 

Have never seen an issue for already imported existing unchanged items on any scan.

[SideCar 4]

@Luke and @Happy2Play

I'm not sure how better to explain this but I'll try.

1. Suppose I have 36 libraries.

2. I add or delete a folder to/from 1 library.

3. Emby will now scan ALL 36 libraries, even the ones that weren't changed.

Yes, it does indeed need to scan the library that was changed. No, it doesn't need to scan the other 35 that weren't changed. Scanning the other 35 libraries just spins up sleeping drives and wastes time, electricity, and wear-and-tear on the spindles for no benefit.

In addition, there are some libraries that I don't want scanned until I manually initiate it. I keep the 'Enable real time monitoring' option turned off for these libraries. The current behavior scans those libraries even though I don't want it to happen and even though no changes were made to them.

As I said, it's not a bug. It's just pointless, wasteful behavior that also overrides user preferences. It's not a big deal but it can easily be changed to make the program more predictable, less wasteful, and more user-responsive.

Does that help?

Thanks. 

[Happy2Play 9780]

So the full scan that is triggered by any Library setup changes ie Librarymonitor stopping on every library to scan for what you changed.

[SideCar 4]

@Happy2Play

Can you please clarify? Was that a question or a statement?

[Happy2Play 9780]

Well I would expect this behavior as you are modifying Library setup.  But everyone wants something different so I would call this a Feature Request personally.

[Luke 42078]

Hi , yes there’s room for improvement there. Thanks.

[Grammatron 2]

@Luke

I just ran across this same issue that @SideCarreported where after I added 1 new folder to my existing TV library, Emby kicked of a full library scan of all libraries including TV after the new folder was added. Thinking I triggered something to cause the full scan to run, I found this thread while troubleshooting.

What I'm seeing now is that after almost 24 hours, the TV library is still being scanned making any content not re-scanned unavailable to watch. Once the library re-scan completes (other libraries or media in TV), that content becomes available to watch and its previous status remembered (watched, not watched, resume.).

After a full day of still scanning I started checking and tailing logs to try and better track the re-scan status and I found a lot of entries like this for each show being scanned in the TV library:

 

2023-04-18 08:04:53.293 Info App: Moving fingerprint file from /var/packages/EmbyServer/var/cache/temp/5a1385e330c249a9b6a6f6890cc2a106 to /volume1/EmbyConfig/metadata/library/43/4399e13cc211301a0aa9eceda84f28a6/title_10_636645320490000000.fp
2023-04-18 08:04:53.295 Info FfmpegManager: ProcessRun 'CreateTitleFingerprint' Execute: /var/packages/EmbyServer/target/bin/ffmpeg  -t 00:10:00.000 -i file:"/volume1/TV/Sons.of.Anarchy/Season.01/Sons.of.Anarchy.S01E10.Better.Half.mp4" -ac 1 -acodec pcm_s16le -ar 16000 -vn -sn -f chromaprint -fp_format raw "/var/packages/EmbyServer/var/cache/temp/176c6dde868a4c5d9b08cfe17720776c"
2023-04-18 08:04:56.266 Info FfmpegManager: ProcessRun 'CreateTitleFingerprint' Process exited with code 0 - Succeeded
2023-04-18 08:04:56.266 Info App: CreateTitleFingerprint completed for /volume1/TV/Sons.of.Anarchy/Season.01/Sons.of.Anarchy.S01E10.Better.Half.mp4 to /var/packages/EmbyServer/var/cache/temp/176c6dde868a4c5d9b08cfe17720776c

 

I searched the forums but couldn't find what's triggering the fingerprint move and create title fingerprint for each file.

What's causing the re-scan to touch each file and drag out the re-scan after only adding a new folder to the library and can this action be stopped or suppressed to speed up the re-scan since no files or metadata have changed?

Thanks