[SOLVED] CIFS VFS errors about old shares (bad network name)

[juraedv]

Hello everyone,

i am encountering a lot of strange error messages in the journal about old (now not configured and not existing) cifs shares on my Synology (IP 10.0.1.20).

These shares are not configured in the GUI, they are not show in /etc/pve/storage.cfg and they are not listed when using findmnt.

This is the example output in journal:

Jan 11 15:00:05 proxmox1 kernel: CIFS: VFS: \\10.0.1.20\server-backups BAD_NETWORK_NAME: \\10.0.1.20\server-backups
Jan 11 15:00:05 proxmox1 kernel: CIFS: VFS: reconnect tcon failed rc = -2
Jan 11 15:00:05 proxmox1 kernel: CIFS: VFS: \\10.0.1.20\client-backups BAD_NETWORK_NAME: \\10.0.1.20\client-backups
Jan 11 15:00:05 proxmox1 kernel: CIFS: VFS: reconnect tcon failed rc = -2
Jan 11 15:00:05 proxmox1 kernel: CIFS: VFS: \\10.0.1.20\vmbackups BAD_NETWORK_NAME: \\10.0.1.20\vmbackups
Jan 11 15:00:05 proxmox1 kernel: CIFS: VFS: reconnect tcon failed rc = -2
Jan 11 15:00:07 proxmox1 kernel: CIFS: VFS: \\10.0.1.20\server-backups BAD_NETWORK_NAME: \\10.0.1.20\server-backups
Jan 11 15:00:07 proxmox1 kernel: CIFS: VFS: reconnect tcon failed rc = -2
Jan 11 15:00:07 proxmox1 kernel: CIFS: VFS: \\10.0.1.20\client-backups BAD_NETWORK_NAME: \\10.0.1.20\client-backups
Jan 11 15:00:07 proxmox1 kernel: CIFS: VFS: reconnect tcon failed rc = -2
Jan 11 15:00:07 proxmox1 kernel: CIFS: VFS: \\10.0.1.20\vmbackups BAD_NETWORK_NAME: \\10.0.1.20\vmbackups
Jan 11 15:00:07 proxmox1 kernel: CIFS: VFS: reconnect tcon failed rc = -2

Interestingly it the node tries to connect to an NFS Share on that Synology. During the initial setup of our infrastructure i had a NFS share on the Synology connected to the node. During that time we encountered a lot of connection errors until we figured out, that the network cable connecting the Synology was actually broken. But now the two nodes in my cluster are connected to two shares on that Synology which work just fine. (with different share names than the ones found in the errors in journal)

But also: Now there are no NFS Shares configured anywhere. And both nodes in my cluster got even rebooted since that time. So i am really wondering: From where does the node remember these old share's information?

Jan 11 15:00:09 proxmox1 kernel: nfs: server 10.0.1.20 not responding, timed out
Jan 11 15:00:15 proxmox1 systemd[1]: Stopping user@0.service - User Manager for UID 0...
Jan 11 15:00:15 proxmox1 systemd[206118]: Activating special unit exit.target...
Jan 11 15:00:15 proxmox1 systemd[206118]: Stopped target default.target - Main User Target.

Any ideas?

(I am actually caring about this (potential) problem, since i am investigating an issue hat happened this night: All VMs lost connection / maybe the Cluster got out of sync. It might be connected to the above shown Synology topic since we are backing up VMs onto that Synology over the same network as corosync is run...)

 

[Chris]

Hi,
please check that the network shares are not configured in the cat /etc/fstab and check for possible systemd mount units related to the network shares systemctl status '*.mount'.

 

[juraedv]

Thanks for you quick reply. I checked and there's no hint:

etc/fstab is practically empty.
systemctl status '*.mount' not hints. (shows a lot, also the new and fine working cifs-shares, but not the old ones.)

I scrolled back a bit in journal and i came across a huge sections of several hours of this:

Jan 12 04:40:53 proxmox2 kernel: CIFS: VFS: reconnect tcon failed rc = -2
Jan 12 04:41:06 proxmox2 kernel: CIFS: VFS: \\10.0.1.20\client-backups BAD_NETWORK_NAME: \\10.0.1.20\client-backups
Jan 12 04:41:06 proxmox2 kernel: CIFS: VFS: reconnect tcon failed rc = -2
Jan 12 04:41:06 proxmox2 kernel: CIFS: VFS: \\10.0.1.20\vmbackups BAD_NETWORK_NAME: \\10.0.1.20\vmbackups
Jan 12 04:41:06 proxmox2 kernel: CIFS: VFS: reconnect tcon failed rc = -2
Jan 12 04:41:08 proxmox2 kernel: CIFS: VFS: \\10.0.1.20\server-backups BAD_NETWORK_NAME: \\10.0.1.20\server-backups
Jan 12 04:41:08 proxmox2 kernel: CIFS: VFS: reconnect tcon failed rc = -2
Jan 12 04:41:08 proxmox2 kernel: CIFS: VFS: \\10.0.1.20\client-backups BAD_NETWORK_NAME: \\10.0.1.20\client-backups
Jan 12 04:41:08 proxmox2 kernel: CIFS: VFS: reconnect tcon failed rc = -2
Jan 12 04:41:08 proxmox2 kernel: CIFS: VFS: \\10.0.1.20\vmbackups BAD_NETWORK_NAME: \\10.0.1.20\vmbackups
Jan 12 04:41:08 proxmox2 kernel: CIFS: VFS: reconnect tcon failed rc = -2
(..)
Jan 12 04:41:09 proxmox2 kernel: nfs: server 10.0.1.20 not responding, timed out

It's a pattern of the CIFS: VFS error and every once in while the nfs error..

 

[juraedv]

My bad - i checked again: The messages don't appear after the last reboot. So i guess in the system there was some function that still tried (for weeks now!) to communicate with the once lost cifs / nfs connections. But after a reboot this doesn't seem to happen anymore.

I guess this can be marked as solved.