Slow scanning on jellyfin with rclone 6 days ETA

Im scanning in 1500 tv shows into jellyfin and its working out to do 10 shows an hour

so it eta will be around 6 days

I see alot of post about slow scanning on jellyfin but 6 days is alot and just wondering if this is an issue on my side, rclone or jellyfin issue and if any way to speed up?

i have the following settings on the library

rclone with the following commands (i also use my own client ID/API Key with gdrive)

rclone mount --daemon --daemon-timeout=5m --allow-non-empty --buffer-size=1G --use-mmap --dir-cache-time=84h --cache-info-age=168h --vfs-cache-mode=writes --vfs-read-chunk-size-limit off --vfs-cache-max-age=6h --vfs-read-chunk-size=512M --cache-dir /home/user/cache gdrive: /home/user/media/gdrive

and mergerfs with the following command

mergerfs -o rw,use_ino,func.getattr=newest,category.action=all,category.create=ff,cache.files=partial,dropcacheonclose=true /home/user/media/local\*:/home/user/media/gdrive /home/user/media_all

Rclone v1.53.0-DEV

Linux 5.4.31-gentoo-whatbox x86_64


Google drive


Was there a reason you deleted the template and choose not to use it? You are missing a few key things like version, debug log, etc.

apologize i wrote on my phone and didnt paste correctly
ive updated above
i haven't got a debug log as rclone is working im just trying to work out if there is an issue with my rclone command making things slow or jellyfin issue.
thanks Animosity022

you shouldn't use realtime monitoring. I think this feature isn't good for rclone mounts.

Ok I can turn it off but that wouldn't be slowing the scan would it? Does real time monitor take more hits to the api or something?

Real time monitoring pretty much does nothing on a fuse mount as it requires notification for a new file which doesn't happen on a rclone mount.

that include mergerfs not working with real time monitor for local files? so did my mount commands look correct? thanks

You'd have to test it and see if it works or not.

its working but its slow scanning to jellyfin. i was just wondering if this command would be slowing it down

You'd want to check out the new vfs-cache-mode full as that would work a bit better for you.

This is generally bad as it allows for over mounting and shouldn't be used.

You have a huge buffer size so scanning which normally opens and closes files a few times. I'd remove it.

This seems counter intuitive and is normally used on systems with low memory but you have a huge buffer size above so not sure here. If you aren't on a low memory system, you should remove it.

This makes huge range requests and isn't good for scanning.

In general, it's really beneficial to leave things on defaults unless you have a reason to change them or are more familiar with implications of changing them.

Thank animonsity022 really appreciate the help.
i will try out the following

rclone mount --vfs-cache-mode=full gdrive: /home/user/media/gdrive

and mergerfs ok to leave the same?

mergerfs -o rw,use_ino,func.getattr=newest,category.action=all,category.create=ff,cache.files=partial,dropcacheonclose=true /home/user/media/local\*:/home/user/media/gdrive /home/user/media_all

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.