je82 Posted February 15, 2020 Share Posted February 15, 2020 (edited) I had a mount in fstab such as : \\1.1.1.3\Logs I removed this mount in fstab and did: umount /home/nasbackuplogs/ unmount was successful. then i check cat /proc/mounts there is no mount pointing to \\1.1.1.3\Logs Yet... My syslog is every second filling up with: Feb 15 15:39:19 NAS kernel: CIFS VFS: BAD_NETWORK_NAME: \\1.1.1.3\Logs Feb 15 15:39:22 NAS kernel: CIFS VFS: BAD_NETWORK_NAME: \\1.1.1.3\Logs Feb 15 15:39:24 NAS kernel: CIFS VFS: BAD_NETWORK_NAME: \\1.1.1.3\Logs Feb 15 15:39:26 NAS kernel: CIFS VFS: BAD_NETWORK_NAME: \\1.1.1.3\Logs Feb 15 15:39:28 NAS kernel: CIFS VFS: BAD_NETWORK_NAME: \\1.1.1.3\Logs Feb 15 15:39:30 NAS kernel: CIFS VFS: BAD_NETWORK_NAME: \\1.1.1.3\Logs Feb 15 15:39:32 NAS kernel: CIFS VFS: BAD_NETWORK_NAME: \\1.1.1.3\Logs Feb 15 15:39:34 NAS kernel: CIFS VFS: BAD_NETWORK_NAME: \\1.1.1.3\Logs Feb 15 15:39:36 NAS kernel: CIFS VFS: BAD_NETWORK_NAME: \\1.1.1.3\Logs Feb 15 15:39:38 NAS kernel: CIFS VFS: BAD_NETWORK_NAME: \\1.1.1.3\Logs Feb 15 15:39:40 NAS kernel: CIFS VFS: BAD_NETWORK_NAME: \\1.1.1.3\Logs Feb 15 15:39:42 NAS kernel: CIFS VFS: BAD_NETWORK_NAME: \\1.1.1.3\Logs Where do these come from? There's no mounted volume \\1.1.1.3\Logs, yet it keeps spamming this message. Any idea why this message would keep appearing? Edited February 15, 2020 by je82 Quote Link to comment
JorgeB Posted February 16, 2020 Share Posted February 16, 2020 If you haven't yet try rebooting. 1 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.