[linux-cifs-client] (no subject)

[Marko Käning]

Hi Jeff,

thanks for your response!

> cmd 46 is 0x2E:
> 
> #define SMB_COM_READ_ANDX             0x2E
> 
> ...so the client was issuing a read call to the server. It didn't
> respond for a bit, so it returned -11 (-EAGAIN) twice. Eventually, it
> looks like the server returned -EBADF (-9), which means that the
> filehandle was no good.
I see.

> What kernel are you running?
My client machine runs:

 Linux client 2.6.22.18-0.2-default #1 SMP 2008-06-09 13:53:20 +0200 i686 
 i686 i386 GNU/Linux

 with Samba 3.0.26a 

and the remote server:

 Linux server 2.6.16.53-0.8-smp #1 SMP Fri Aug 31 13:07:27 UTC 2007
 x86_64 x86_64 x86_64 GNU/Linux

 with Samba 3.0.22

Had similar messages last night, this time also with cmds 50 and 162:
---
Unusual System Events
=-=-=-=-=-=-=-=-=-=-=
Jul 17 22:00:19 flmpc35 kernel:  CIFS VFS: No response for cmd 50 mid 
11988
Jul 17 22:00:19 flmpc35 kernel:  CIFS VFS: No response to cmd 46 mid 11989
Jul 17 22:00:19 flmpc35 kernel:  CIFS VFS: Send error in read = -11
Jul 17 22:00:19 flmpc35 kernel:  CIFS VFS: No response for cmd 50 mid 
11987
Jul 17 22:00:19 flmpc35 kernel:  CIFS VFS: No response for cmd 162 mid 
11986
Jul 17 22:00:19 flmpc35 kernel:  CIFS VFS: No response for cmd 50 mid 
11985
Jul 17 22:00:19 flmpc35 kernel:  CIFS VFS: No response to cmd 4 mid 11984
Jul 17 22:00:19 flmpc35 kernel:  CIFS VFS: Send error in Close = -11
Jul 17 22:00:19 flmpc35 kernel:  CIFS VFS: Send error in read = -9
Jul 17 22:00:19 flmpc35 kernel:  CIFS VFS: Send error in read = -9
---
i.e.

 #define SMB_COM_TRANSACTION2     0x32

and 

 #define SMB_COM_NT_CREATE_ANDX   0xA2

So, what can we learn from that?

Regards,
Marko