NFS Speed

Help and Support Vero V
1

So I find that library scanning via NFS is much slower on my Vero V compared to my R Pi 5.

Is this normal?

Takes like 10 seconds at 0% before scanning then takes long time to finish.

2

Are you using WiFi or Ethernet?

Are you using an NFS mount or Kodi mount?

3

Ethernet and I created a NFS mount using the Kodi sources menu. Same as I done on the Pi.

4

Excuse my English skills but can you please explain this a bit more in detail? Thx.

5

So when I start a library scan it gets stuck on 0% progress for around 10 to 12 seconds and then it starts to scan my library slowly. Much slower then what I had using same cable and set up on my Rasberry Pi 5.

6

Are you talking about scraping new items or just scanning without any change in the database?

7

Same thing happens both times.

I use library watchdog which runs scans on changes but when I do scan manually same slowness.

The Pi did not slow down during new items being added either.

8

Excuse me for asking again: But what happens if NO NEW FILMS need to be added und you start a manual scan within the GUI?

It makes a significant difference whether we’re talking about an NFS issue or a scraper performance problem.

Perhaps to give you an idea from my setup: My active movie database (local at VeroV) currently contains 170 movies, and a manual scan of the movie files, without finding any new movies, takes about 2 seconds. The data is stored on a Synology NAS, connected via NFS from the media center, default version 4, and a buffer size of 128 KB.

9

As I said it still takes long time if there is no new films and I manually run a scan.

It gets stuck on 0% for 10 to 12 seconds and then slowly runs to 100% and finishes.

Also to note I am using local nfo files so not using external service to get info from.

10

And the NFS client within kodi is configured the same like on the RPi 5? Means same NFS version to use, same buffer size?

11

correct

12

No idea since I don’t use .nfo files at all.
Perhaps, you can provide a log set which sheds some light what’s going on. Let us know if you need instructions.

13

logs here:

https://paste.osmc.tv/kutagimesu

14

Thx, but debug logging was disabled.

What I did on my side: I created for all my movies .nfo files (using media export function, separate mode and nfo files only), deleted the movies source out of the library and re-scanned all movies (now using the .nfo files).

Now, a new scan (using ‘update library’) takes 3 seconds and I don’t see any of those messages your log is full of

...
2026-02-01 18:42:03.861 T:5057  warning <general>: Process directory 'nfs://192.168.1.200/mnt/user/Stuff/Movies/the returned 2014/' does not exist - skipping scan.
...
2026-02-01 18:45:39.497 T:5076     info <general>: UpdateDetailsForMovie: Starting updates for movie 8499
2026-02-01 18:45:39.506 T:5076     info <general>: UpdateDetailsForMovie: Finished updates for movie 8499
...

I even installed the add-on Library Watchdog … but no success. I do not see any of these messages in my logs. The big delta is ‘MySQL’ as shared library and the Arctic Fuse 2 skin, I’m not using (and I will not test).

So, if it is not a specific configuration issue, you should look into the RPi’s logs and see whether you find the same log entries there or in case they’re missing, that seems to be the origin of the monitored different runtime.

15

Any chance this can be made default? Very honestly, this is the way to go.
You have instructions for that, on what to do exactly?

16

Well, this is not a rocket science. Just follow these instructions

  1. doing an export (separate mode, either only the nfo files or all pictures as well) https://kodi.wiki/view/Import-export_library/Video
  2. Remove the source(s) of the movies at Videos → Files
  3. Setup again the source(s) at Videos → Files

While this final scan of the new video source(s) the .nfo files are used.

If you change something in an nfo, you need to remove that movie from the library and run an update library again. But … with MySQL the behaviour could be different. The issue of the TO suggests that a complete update of items then can happen using a MySQL library.

Addition: Here the export does not work with NFSv4 sources being setup within the mediacenter. ~You first have to setup a mountpoint using autofs, scrape und export using the root file system … and then remove the source and re-setup as NFS source in the mediacenter or better use the NFS autofs configuration from now.
It only works with NFSv3 setup in the kodi NFS client configuration at `Settings → Services → NFS Client’.

1 Like
17

I checked Pi and those messages are in the logs there Also about missing files. I also using same skin there.

18

@xenomorph I cannot reproduce your issue but I’m neither using MySQL nor your specific skin Arctic Fuse 2. Others are welcome to help and share ideas.

19

the skin should not make difference to how long it takes to scan library.

I tried default skin and same issue.

20

I meanwhile setup MariaDB on my Synology NAS, setup a VeroV using the mysql method to this db system, setup NFS file access to the movies, installed the addons Library Watchdog and Library Auto Update you’re using, created the nfo files … and here an ‘Update Library’ started in the mediacenter GUI only last 2-3 seconds for 170 movies even using the MariaDB and .nfo files. I also do not see any of these messages about missing folders or these UpdateDetailsForMovie.

Two things are not clear to me:

  1. In your log we see tons of entries like

    2026-02-01 18:42:00.107 T:5057 warning <general>: Process directory 'nfs://192.168.1.200/mnt/user/Stuff/Movies/3 from Hell (2019)/' does not exist - skipping scan.

but surrounded by

2026-02-01 18:31:30.492 T:5057     info <general>: VideoInfoScanner: Starting scan ..
...
2026-02-01 18:42:03.876 T:5057     info <general>: VideoInfoScanner: Finished scan. Scanning for video info took 633450 ms

This seems to be something like an invoked ‘Library Update’. Why this database is not clean and always contain orphan entries?

  1. There seems to be some manual user interaction starting before the UpdateDetailsForMovie actions, most possible you’re starting an addon from the addon browser:
2026-02-01 18:43:13.415 T:4664     info <general>: Loading skin file: AddonBrowser.xml, load type: KEEP_IN_MEMORY
2026-02-01 18:43:13.441 T:4664  warning <general>: Trying to add unsupported control type 7
2026-02-01 18:43:21.177 T:4664     info <general>: Loading skin file: DialogAddonInfo.xml, load type: KEEP_IN_MEMORY
2026-02-01 18:43:24.725 T:4664     info <general>: Loading skin file: DialogAddonSettings.xml, load type: KEEP_IN_MEMORY
2026-02-01 18:43:24.737 T:4664  warning <general>: Skin has invalid include: defs_dialog_colorbutton
2026-02-01 18:44:24.400 T:5076     info <general>: Skipped 3 duplicate messages..
2026-02-01 18:44:24.400 T:5076     info <general>: UpdateDetailsForMovie: Starting updates for movie 7219
2026-02-01 18:44:24.420 T:5076     info <general>: UpdateDetailsForMovie: Finished updates for movie 7219
2026-02-01 18:44:24.467 T:5076     info <general>: UpdateDetailsForMovie: Starting updates for movie 7257
2026-02-01 18:44:24.476 T:5076     info <general>: UpdateDetailsForMovie: Finished updates for movie 7257
2026-02-01 18:44:24.523 T:5076     info <general>: UpdateDetailsForMovie: Starting updates for movie 7345

So, what are you doing here?

This looks like a more complex environment at your site and you should explain more in detail what is your mysql db system, about how many movies we’re talking here, why this db always contains orphan entries of movies and TV shows and your interactions in the GUI.

With the current information I cannot understand the logs nor reproduce any similiar behaviour.