The following capture for a run of ls after running close-smbsession on
windows and clearing the caches on the linux client running the upstream
kernel.
1 0.000000 client → server SMB2 410 Create Request File: dir;GetInfo Request FILE_INFO/SMB2_FILE_ALL_INFO;Close Request
2 0.004586 server → client SMB2 274 Create Response, Error: STATUS_USER_SESSION_DELETED;GetInfo Response, Error: STATUS_INVALID_PARAMETER;Close Response, Error: STATUS_INVALID_PARAMETER
9 0.024997 client → server SMB2 290 Negotiate Protocol Request
10 0.033179 server → client SMB2 566 Negotiate Protocol Response
12 0.033578 client → server SMB2 178 Session Setup Request, NTLMSSP_NEGOTIATE
13 0.041297 server → client SMB2 368 Session Setup Response, Error: STATUS_MORE_PROCESSING_REQUIRED, NTLMSSP_CHALLENGE
15 0.041792 client → server SMB2 434 Session Setup Request, NTLMSSP_AUTH, User: \user
16 0.047307 server → client SMB2 130 Session Setup Response
18 0.047832 client → server SMB2 174 Tree Connect Request Tree: \\server\root
19 0.057075 server → client SMB2 138 Tree Connect Response
20 0.057586 client → server SMB2 172 Tree Connect Request Tree: \\server\IPC$
21 0.062169 server → client SMB2 138 Tree Connect Response
22 0.062273 client → server SMB2 410 Create Request File: dir;GetInfo Request FILE_INFO/SMB2_FILE_ALL_INFO;Close Request
23 0.069050 server → client SMB2 570 Create Response File: dir;GetInfo Response;Close Response
24 0.069943 client → server SMB2 316 Create Request File: dir;Find Request SMB2_FIND_ID_FULL_DIRECTORY_INFO Pattern: *
25 0.079125 server → client SMB2 3842 Create Response File: dir;Find Response SMB2_FIND_ID_FULL_DIRECTORY_INFO Pattern: *
27 0.081926 client → server SMB2 156 Find Request File: dir SMB2_FIND_ID_FULL_DIRECTORY_INFO Pattern: *
28 0.093209 server → client SMB2 130 Find Response, Error: STATUS_NO_MORE_FILES SMB2_FIND_ID_FULL_DIRECTORY_INFO Pattern: *
29 0.093743 client → server SMB2 146 Close Request File: dir
30 0.099034 server → client SMB2 182 Close Response
Similar pattern for stat.
Best,
Thiago
