Comments on: CIFS VFS No response for cmd n mid…

By: cnafa

cnafa — Mon, 19 Jul 2010 09:36:38 +0000

My function use cifs protocol to transfer file and it usually occur “CIFS VFS: Send error in read = -11
” error.
I searched the cifs reference and get a ways to resovle it.

http://pserver.samba.org/samba/ftp/cifs-cvs/linux-cifs-client-guide.pdf

”
Performance Considerations
Server speed, server disk speed and network speed can constrain the overall performance of a cifs
mount, but in some cases, client client configuration settings can be changed to increase performance:
1) size of file write (wsize). The Linux CIFS client usually sends 56K writes (14 pages) and is
limited to 56K maximum unless mounted forcedirectio.
2) size of file read (rsize). The Linux CIFS client usually sends 16K reads (4 pages). Since CIFS
large network buffers are about 16K in size by default, increasing the rsize would have little
effect unless the setting of module load parameter CIFSMaxBufSize (via insmod) also is
increased.
”

I just lower the block of data what i want to write.

you can use command “modinfo cifs” to get the cifs read or write buffer size and buffersize scope.

By: cnafa

cnafa — Mon, 19 Jul 2010 09:31:21 +0000

My function use cifs protocol to transfer file and it usually occur “CIFS VFS: Send error in read = -11
” error.
I searched the cifs reference and get a ways to resovle it.

http://pserver.samba.org/samba/ftp/cifs-cvs/linux-cifs-client-guide.pdf

I just lower the block of data what i want to write

By: korman

korman — Fri, 02 Jul 2010 14:03:34 +0000

I should add it was “Cold booted”

By: korman

korman — Fri, 02 Jul 2010 14:02:55 +0000

We just put into production a RHEL5 Linux / Oracle server which uses the CIFS client to injest a number of files located on a Win2k8 Server. At 8PM I found similar errors and SAR showed %system cpu at to 99% and staying there until the server had was rebooted 2 hours later. I am guessing this post might have saved my ass..

By: Bill Rebey

Bill Rebey — Fri, 30 Apr 2010 18:52:22 +0000

Thanks a million for posting this! This has been a real nightmare for me ever since upgrading to 9.10 from 9.04 (the problem didn’t seem to exist in 9.04).

By: Marco Verleun

Marco Verleun — Wed, 06 Jan 2010 22:11:00 +0000

It is possible to change this setting automatically when loading the CIFS module. modprobe has a nice feature to execute a script when loading a module. Check man 5 modprobe.conf

Add a line to /etc/modprobe.conf or a file in /etc/modprobe.d containing the following line, this is one single line:
install cifs /sbin/modprobe –ignore-install cifs; echo 0 > /proc/fs/cifs/OplockEnabled ;

By: Maurice

Maurice — Mon, 14 Sep 2009 23:14:45 +0000

Touchdown! I use a Nagios server to check the “goodness” of a number of files on Windows servers. Since moving from hard metal to a virtual server the network has been occasionally locking up within minutes of a reboot. I was blaming ntp until I googled the CIFS error message.

I can now get my life back!

By: bolt

bolt — Sat, 29 Aug 2009 07:06:40 +0000

I’m very sorry, but the above solution worked for me. If you’ve made sure the file exists in the first place and hasn’t been renamed or anything in your distro, then I’m afraid I can’t help you much more, as the above solution works for me.

By: dexter

dexter — Fri, 28 Aug 2009 14:59:42 +0000

The same thing like Monkey Prince.
Help.

By: Monkey Prince

Monkey Prince — Mon, 22 Jun 2009 21:45:22 +0000

I follow your instructions, but still have these errors
CIFS VFS: No response for cmd 50 mid 61463
CIFS VFS: No response for cmd 50 mid 61462
CIFS VFS: No response for cmd 50 mid 61461
CIFS VFS: No response to cmd 46 mid 61460
CIFS VFS: Send error in read = -11
CIFS VFS: No response for cmd 50 mid 61465
CIFS VFS: No response for cmd 50 mid 61466
CIFS VFS: No response for cmd 50 mid 61464
If I cat /proc/fs/cifs/OplockEnabled, it returns 0. Please help me