CIFS/NFS mounts on XCP-NG vm are unresponsive

1

Hello

I have the following setup:

  1. TrueNAS Core 13.0-U6.4 server that have SMB and NFS sharing the same folder (media files - video and audio) (IP 192.168.100.2)
  2. XCP-NG 8.3 machine on which I run vms.
  3. TPLink TL-SG108E switch (10/100/1000)
  4. pfSense 2.7.2
  5. TrueNAS and XCP-NG machines are on the same VLAN
  6. The NIC’s on the machines are 1GB ethernet

One of the vms is and ubuntu server 24.04 LTS that runs jellyfin media server and have the shared folder from TrueNAS mounted in /mnt/mediafolder as SMB share. Here is the fstab entry:

# SMB mounts from TrueNAS
//192.168.100.2/MediaFolder /mnt/mediafolder      cifs    user=jellyfin,password=password,uid=jellyfin,gid=jellyfin,ro,iocharset=utf8      0 0

The problem is that browsing on the mounted folder it is very slow, almost unresponsive (for example, doing cd /mnt/mediafolder/folder01 takes more than a minute to complete during which the cli “freezes”) and in the logs I got this errors:

CIFS: VFS: \192.168.100.2 has not responded in 180

Feb 16 11:20:17 mediaserver systemd[1217]: launchpadlib-cache-clean.service - Clean up old files in the Launchpadlib cache was skipped because of an unmet condition check (ConditionPathExists=/home/jellyfin/.l>
Feb 16 11:22:33 mediaserver kernel: netfs: FS-Cache loaded
Feb 16 11:22:33 mediaserver kernel: Key type cifs.spnego registered
Feb 16 11:22:33 mediaserver kernel: Key type cifs.idmap registered
Feb 16 11:22:33 mediaserver kernel: CIFS: No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3.1.1), from CIFS (SMB1). To use the less secure SMB1 dialect t>
Feb 16 11:22:33 mediaserver kernel: CIFS: enabling forceuid mount option implicitly because uid= option is specified
Feb 16 11:22:33 mediaserver kernel: CIFS: enabling forcegid mount option implicitly because gid= option is specified
Feb 16 11:22:33 mediaserver kernel: CIFS: Attempting to mount //192.168.100.2/SharedFolder
Feb 16 11:22:37 mediaserver PackageKit[8457]: daemon quit
Feb 16 11:22:37 mediaserver systemd[1]: packagekit.service: Deactivated successfully.
Feb 16 11:22:44 mediaserver systemd[1]: Reloading requested from client PID 13306 ('systemctl') (unit session-1.scope)...
Feb 16 11:22:44 mediaserver systemd[1]: Reloading...
Feb 16 11:22:44 mediaserver systemd[1]: Reloading finished in 234 ms.
Feb 16 11:25:01 mediaserver CRON[13347]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)
Feb 16 11:25:01 mediaserver CRON[13348]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 16 11:25:01 mediaserver CRON[13347]: pam_unix(cron:session): session closed for user root
Feb 16 11:26:14 mediaserver kernel: CIFS: VFS: \\192.168.100.2 has not responded in 180 seconds. Reconnecting...
Feb 16 11:29:17 mediaserver systemd[1]: Starting systemd-tmpfiles-clean.service - Cleanup of Temporary Directories...
Feb 16 11:29:18 mediaserver systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully.
Feb 16 11:29:18 mediaserver systemd[1]: Finished systemd-tmpfiles-clean.service - Cleanup of Temporary Directories.
Feb 16 11:29:20 mediaserver kernel: CIFS: VFS: \\192.168.100.2 has not responded in 180 seconds. Reconnecting...
Feb 16 11:30:07 mediaserver systemd[1]: Starting sysstat-collect.service - system activity accounting tool...

The ping has the following results:

64 bytes from 192.168.100.2: icmp_seq=1 ttl=64 time=0.529 ms
64 bytes from 192.168.100.2: icmp_seq=2 ttl=64 time=0.692 ms
64 bytes from 192.168.100.2: icmp_seq=3 ttl=64 time=0.730 ms
64 bytes from 192.168.100.2: icmp_seq=4 ttl=64 time=0.785 ms
64 bytes from 192.168.100.2: icmp_seq=5 ttl=64 time=0.697 ms
64 bytes from 192.168.100.2: icmp_seq=6 ttl=64 time=0.642 ms
64 bytes from 192.168.100.2: icmp_seq=7 ttl=64 time=0.700 ms

The curios thing is:

  1. I have a vm on TrueNAS with same settings and no problem with that (I want to decommission it and replace it with the XCP-NG one)
  2. I have a Fedora 41 vm on XCP-NG machine and no problem with the shared folder (is mounted as gvfs from Nautilus)
  3. I have no problems with the mount folder on the laptop through wifi

I tried also to mount it using NFS with the same results, here are the settings for NFS:
fstab entry:

# NFS mounts from TrueNAS
192.168.100.2:/mnt/Pool01/MediaFolder        /mnt/mediafolder      nfs     defaults,rw,bg,soft,nosuid,timeo=10,vers=4              0 0

nfsstat info:

/mnt/mediafolder from 192.168.100.2:/mnt/Pool01/MediaFolder
 Flags:	rw,nosuid,relatime,vers=4.2,rsize=131072,wsize=131072,namlen=255,soft,proto=tcp,timeo=10,retrans=2,sec=sys,clientaddr=192.168.100.24,local_lock=none,addr=192.168.100.2

How can I fix this? how to get more info from the logs?
Thanks

2

I would also look at the logs in TrueNAS to see if there is some reason or error for the disconnect. Are you using jumbo frames? Also worth noting that Core is in maintenance mode and reaching end of life.

3

Hi,

After a little more troubleshooting I fond out I was the cause :slight_smile:
Both TrueNAS and XCP-NG machines have 2 NIC’s: eth0 and eth1. I use eth0 (192.168.10.0/24) for “infrastructure LAN” and eth1 for VLAN’s.

The problem was that the mediaserver vm on XCP-NG had eth0 assigned :frowning:

Also worth noting that Core is in maintenance mode and reaching end of life.

I know, and planning to migrate to TrunNAS Scale.

Thanks for your time, and sorry for this rookie mistake.

1 Like