There is a bug where the embedyserver failed to scan the resource library due to a long path

[dux_fang 0]

My Emby server is installed on a QNAP device, and the path for Emby installation itself is already quite long, such as: /share/CACHEDEV1_DATA/Public/. When establishing video file paths within this directory, it becomes inevitable that the path directories become very deep, such as storage directories established according to TV series categories, TV series eras, TV series names, TV series season names, and so on.
When I used emby to scan the resource library, I found that some directories were not scanned. After searching through the logs for a long time, I discovered that it was caused by an error during scanning. The logs are attached.

2026-02-06 18:55:09.631 Error LibraryMonitor: Error in Directory watcher for: /share/CACHEDEV1_DATA/Public/CloudDrive/115(15221893505)/电视剧1
	*** Error Report ***
	Version: 4.9.3.0
	Command line: /share/CACHEDEV1_DATA/.qpkg/EmbyServer/system/EmbyServer.dll -programdata /share/CACHEDEV1_DATA/.qpkg/EmbyServer/programdata -ffdetect /share/CACHEDEV1_DATA/.qpkg/EmbyServer/bin/ffdetect -ffmpeg /share/CACHEDEV1_DATA/.qpkg/EmbyServer/bin/ffmpeg -ffprobe /share/CACHEDEV1_DATA/.qpkg/EmbyServer/bin/ffprobe -pidfile /var/run/emby-server.pid -defaultdirectory /share/CACHEDEV1_DATA/Public -updatepackage emby-server-qnap_{version}_x86_64.qpkg -noautorunwebapp
	Operating system: Linux version 5.10.60-qnap (root@mini-builder-10) (x86_64-QNAP-linux-gnu-gcc (toolchain config: [gcc-4.9.2 binutils-2.25 glibc-2.21]) 4.9.2, GNU ld (G
	OS/Process: x64/x64
	Framework: .NET 8.0.22
	Runtime: share/CACHEDEV1_DATA/.qpkg/EmbyServer/system/System.Private.CoreLib.dll
	Processor count: 4
	Data path: /share/CACHEDEV1_DATA/.qpkg/EmbyServer/programdata
	Application path: /share/CACHEDEV1_DATA/.qpkg/EmbyServer/system
	System.IO.PathTooLongException: System.IO.PathTooLongException: The path '/share/CACHEDEV1_DATA/Public/CloudDrive/115(15221893505)/电视剧1/动作/王牌部队_(2021)' is too long, or a component of the specified path is too long.
	   at System.IO.Enumeration.FileSystemEnumerator`1.MoveNext()
	   at System.IO.FileSystemWatcher.RunningInstance.AddDirectoryWatchUnlocked(WatchedDirectory parent, String directoryName)
	Source: System.Private.CoreLib
	TargetSite: Boolean MoveNext()

However, some directory names are longer than the ones that have errors, yet they are correct. I don't understand the difference and where the problem lies?
The upper part of the log contains the directory where the error occurred, while the lower part lists the normal log names for reference.

embyserver.txt

[Luke 42077]

Hi there, please attach the complete Emby server log from when the problem occurred:

How to Report a Problem

Thanks!