[linux-cifs-client] CIFS VFS: No response for cmd 50

[Jeremy Allison]

On Tue, Apr 10, 2007 at 02:07:29PM +0200, Alexander Meyer wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hi,
> 
> i'm a network administrator in a company with about 50 employees of
> which about 15 are using linux workstations and mount their
> home-directories via cifs-vfs from a samba server. They have been using
> nfs before but i changed that to cifs for security reasons. While with
> nfs there were no problems reported i now get regular complaints about
> hanging filesystem operations on the mounted shares. Here is a snipplet
> of what shows up in the kernel log of the clients:
> 
> - -snip-
> [17187966.584000]  CIFS VFS: No response for cmd 50 mid 97
> [17187996.584000]  CIFS VFS: No response for cmd 50 mid 101
> [17188026.584000]  CIFS VFS: No response for cmd 50 mid 105
> [17188056.584000]  CIFS VFS: No response for cmd 50 mid 109
> [17188086.584000]  CIFS VFS: No response for cmd 50 mid 113
> [17188116.596000]  CIFS VFS: No response for cmd 50 mid 117
> [17188146.584000]  CIFS VFS: No response for cmd 50 mid 121
> - -snap-
> 
> The kernel-versions involved are these:
> 
> 
> 2.6.12 (1 client)
> 2.6.17 (6 clients)
> 
> Google doesn't know too much about this, there are occasional reports of
> similar problems but so far i haven't found any answers to it. I'm in a
> somewhat desperate situation here, my users are getting angry but i
> don't want to switch back to nfs.

cmd 50 is an SMBtrans2 call. Can you get ethereal/wireshark capture
traces from a system in this state ?

Jeremy.