CIFS VFS: Close unmatched open - FreeNAS-11.1-U5 - Linux Clients - vers=2.1

[webdawg]

Code:

[553153.220747] CIFS VFS: Close unmatched open
[553153.221674] CIFS VFS: Close unmatched open
[554336.544740] CIFS VFS: Close unmatched open
[554336.545601] CIFS VFS: Close unmatched open
[556106.747880] CIFS VFS: Close unmatched open
[556106.748264] CIFS VFS: Close unmatched open
[558990.310215] CIFS VFS: Close unmatched open

I get a decent amount of the above. I was looking at: https://lore.kernel.org/patchwork/patch/809834/

But I still do not understand what they are talking about:

Code:

A signal can interrupt a SendReceive call which result in incoming
responses to the call being ignored. This is a problem for calls such as
open which results in the successful response being ignored. This
results in an open file resource on the server.

The patch looks into responses which were cancelled after being sent and
in case of successful open closes the open fids.

For this patch, the check is only done in SendReceive2()

I think I get what it is doing, but really why do I have any unmatched opens at all?

 

[anodos]

Where are you seeing those messages? Can you send me the full log file?

 

[webdawg]

Those messages are in the dmesg of the ubuntu client.

I can send you better log files. Anything specifically? Should I turn on debug?

 

[anodos]

Can you perform a tcpdump on the freenas side? tcpdump -i /dev/<your interface> -p -s 0 host <ip of your linux client> and port 445

Send me a debug (system->advanced->save debug) from the freenas server as well.

 

[webdawg]

I can still do all of this, but I switched the share to type windows and it fixed everything. From what I was seeing, it seems like during some operations software was having trouble renaming documents/files.

I can switch a share back and get logs, but what do you think?

 

[webdawg]

I am sorry. I had two threads open, and switching to a windows type share solve one of them. I still have this issue.

If I do that tcpdump, it could be hundreds of GB long. Do you know what I should filter/search for?

 

[anodos]

I am sorry. I had two threads open, and switching to windows solved it. I still have this issue.

If I do that tcpdump, it could be hundreds of GB long. Do you know what I should filter/search for?

I misread that you were able to produce on demand. We can start with a debug from the FreeNAS server. System->Advanced->Save Debug.