February 8, 20242 yr Feb 8 06:42:32 Power kernel: CIFS: VFS: \\192.168.1.133\Archive Close unmatched open for MID:112775 Feb 8 06:43:03 Power kernel: CIFS: VFS: \\192.168.1.133\Archive Close unmatched open for MID:118712 Feb 8 06:43:34 Power kernel: CIFS: VFS: \\192.168.1.133\Archive Close unmatched open for MID:124657 Feb 8 06:44:06 Power kernel: CIFS: VFS: \\192.168.1.133\Archive Close unmatched open for MID:134627 Feb 8 06:44:37 Power kernel: CIFS: VFS: \\192.168.1.133\Archive Close unmatched open for MID:145948 Feb 8 06:45:08 Power kernel: CIFS: VFS: \\192.168.1.133\Archive Close unmatched open for MID:152069 Feb 8 06:45:39 Power kernel: CIFS: VFS: \\192.168.1.133\Archive Close unmatched open for MID:158177 Feb 8 06:46:10 Power kernel: CIFS: VFS: \\192.168.1.133\Archive Close unmatched open for MID:164270 Feb 8 06:46:42 Power kernel: CIFS: VFS: \\192.168.1.133\Archive Close unmatched open for MID:172058 Feb 8 06:47:13 Power kernel: CIFS: VFS: \\192.168.1.133\Archive Close unmatched open for MID:210771 Feb 8 06:47:44 Power kernel: CIFS: VFS: \\192.168.1.133\Archive Close unmatched open for MID:220030 Feb 8 06:48:15 Power kernel: CIFS: VFS: \\192.168.1.133\Archive Close unmatched open for MID:232804 Feb 8 06:48:46 Power kernel: CIFS: VFS: \\192.168.1.133\Archive Close unmatched open for MID:311752 Feb 8 06:49:18 Power kernel: CIFS: VFS: \\192.168.1.133\Archive Close unmatched open for MID:334574 Feb 8 06:49:49 Power kernel: CIFS: VFS: \\192.168.1.133\Archive Close interrupted close I keep getting this error I have 2 other servers connected same way and this doesn't come up any idea?
February 18, 20242 yr I had the same issue. Do you use the plugin "Dynamix Cache Dir" and the plugin "Unassigned Devices"? For me the errors stopped when I disabled the plugin "Dynamix Cache Dir". Seems that this plugin tries to cache the SMB-Share.
February 18, 20242 yr 1 hour ago, barit said: Seems that this plugin tries to cache the SMB-Share. Yes, it caches all mounts unless you set it up not to. You should only have cache_dirs set to include array and pool shares you want to be cached so it will ignore everything else.
February 18, 20242 yr Solution 1 hour ago, dlandon said: You should only have cache_dirs set to include array and pool shares you want to be cached so it will ignore everything else. Yes, that worked for me. Before that I had excluded the dirs that I didn't want to be cached. But I couldn't deselect the /mnt/remotes share. Now I set all shares which shall be cached and the errors are gone.
February 18, 20242 yr 3 hours ago, barit said: Yes, that worked for me. Before that I had excluded the dirs that I didn't want to be cached. But I couldn't deselect the /mnt/remotes share. Now I set all shares which shall be cached and the errors are gone. The exclude really doesn't work because UD devices come and go and there is no way to 'exclude' them. I'm working on having cache_dirs changed so it only allows include shares, and not exclude shares. Glad it got sorted out for you.
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.