Docker/Fedora 41 - Too long path error (actually it's not)

[reset_ 6]

Hello! I got an error while emby tried to import library from media directories, logs attached. The error says that path is too long, but script i launched said, that the longest full path in that dir is not exceeds path size limit:

ULTRA_TOUCH/yt_archive/Любимые видео on  (us-east-1) [X] 
❯ find "$(pwd)" -type f | awk '{ print length}' | sort -n | tail -1

211

mount options:
/mnt/ULTRA_TOUCH ntfs-3g nosuid,nodev,nofail,x-gvfs-show,rw,uid=1000,gid=1000,umask=0022,iocharset=utf8,locale=ru_RU.utf8,big_writes,windows_names

I encountered this error by first time while running emby in docker container (compose file also attached). Tried to run it on fedora - got the same error.
Filenames are mostly consists of cyrillic (russian) symbols, so probably it's an encoding error

How do i fix that? Thanks!

docker-compose-emby.yml embyserver_cutted.txt

Edited April 6, 2025 by reset_
wrong path where script executed (but that path had this error as well)

[reset_ 6]

UPD: tried to load same directory under Windows 11, it worked. But i still need to import it on fedora or docker

[Q-Droid 989]

I wonder if this is about double-byte characters making the path string size bigger than the path character length.

 

 

[reset_ 6]

26 minutes ago, Q-Droid said:

I wonder if this is about double-byte characters making the path string size bigger than the path character length.

 

 

I'm not sure, because there was no "long path" error with the same path on windows 11. Seems like double-byte chars are not a problem in there

[Luke 42077]

Is there a sym link involved?

[reset_ 6]

1 minute ago, Luke said:

Is there a sym link involved?

In this case - no. But i tried to do it with symlinks as well, it didn't help

[Luke 42077]

OK then I wonder if the runtime is having some kind of problem with the path and is throwing an exception with the wrong message.

[reset_ 6]

25 minutes ago, Luke said:

OK then I wonder if the runtime is having some kind of problem with the path and is throwing an exception with the wrong message.

No, seems like runtime didn't have any other issues. All issues, that were in log file, were related with "too long path"

By the way, i've remembered of one more related issue, probably it helps. When i try to add a folder in library, if i explicitly write path to file, which has those too long paths, the folder won't be added to library (nothing will happen) and it also there will be a log, that path is too long

[reset_ 6]

On 4/6/2025 at 9:29 PM, Luke said:

OK then I wonder if the runtime is having some kind of problem with the path and is throwing an exception with the wrong message.

There's no quick fix for this, i guess?

[Luke 42077]

Right now i don't see anything that Emby is doing incorrectly. It's an error coming from the dotnet runtime when trying to get directory contents.

You could always try the beta channel as it has jumped from dotnet 6 to 8.

[reset_ 6]

21 minutes ago, Luke said:

Right now i don't see anything that Emby is doing incorrectly. It's an error coming from the dotnet runtime when trying to get directory contents.

You could always try the beta channel as it has jumped from dotnet 6 to 8.

Yeah, i've searched it up a little bit, and seems like there's no solution for that. In windows i didn't have such issue, because it's possible to toggle long path in there, unlike in linux. So i think i'm going to shrink my filenames... 
Sorry and thanks

[Luke 42077]

Please let us know how this goes. Thanks.

[reset_ 6]

1 hour ago, Luke said:

Please let us know how this goes. Thanks.

Truncating file names to at most 255 bytes helped. All file names, that needed to be truncated, contained russian or other characters, that take up 2 bytes 
Requesting for long paths feature in linux