[linux-cifs-client] Numerous "CIFS VFS: Send error" messages
in 2.6.25.3
Gautam Iyer
gi1242+samba at stanford.edu
Tue May 13 05:26:51 GMT 2008
On Mon, May 12, 2008 at 10:29:12PM -0500, Shirish Pargaonkar wrote:
>> I was using "mount -t smbfs" on Linux-2.6.23 for a long time with no
>> problems. When I recently upgraded to CIFS + Linux-2.6.25, I ran into a
>> few issues.
>>
>> My Samba server is a Vantec networked hard disk. I mount it via
>>
>> mount -t cifs //andurin/PUBLIC /tmp/andurin -o nounix,guest
>>
>> Now I can copy / move files just fine. But when I try and do something
>> fancy, I get numerous errors. Usually at this point my log file is
>> clutter with numerous CIFS VFS error messages. A few of the log lines
>> are:
>>
>> May 12 18:56:04 mordor CIFS VFS: Write2 ret -28, wrote 0
>> May 12 18:56:04 mordor CIFS VFS: No response to cmd 47 mid 67
>> May 12 18:56:04 mordor CIFS VFS: Write2 ret -11, wrote 0
>> May 12 18:56:04 mordor CIFS VFS: Write2 ret -11, wrote -511544036
>> May 12 18:56:04 mordor CIFS VFS: Write2 ret -28, wrote 0
>> May 12 18:56:04 mordor CIFS VFS: Write2 ret -11, wrote -511544036
>> May 12 18:56:04 mordor CIFS VFS: Write2 ret -28, wrote 0
>> May 12 18:56:04 mordor CIFS VFS: No response to cmd 47 mid 78
>>
> I am trying to work on this problem. Try increasing the send
> (sk_sndbuf) and receive (sk_rcvbuf) buffer sizes of socket from 200K
> and 140K respectively to 512K or 1M in fs/cifs/connect.c in function
> ipv4_connect.
Thanks for the quick response. I did this, and seem to get the same
messages in my syslog, and the same error message from fancy operations
(e.g. mke2fs). (I'm also assuming that modprobe -rv cifs, and then
modprobe -iv cifs was enough for this change to take effect).
> What is the output of command
> sysctl -a | grep tcp | grep mem
It was
net.ipv4.tcp_mem = 96672 128896 193344
net.ipv4.tcp_wmem = 4096 16384 4124672
net.ipv4.tcp_rmem = 4096 87380 4124672
Plus a few error messages about ipv6.
Let me know if there's anything else you want me to test, or if there is
anything else I can do to help fix this,
Thanks
GI
--
'Common' Proof Techniques:
5. Proof by Omission -- "The reader may easily supply the details"
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
Url : http://lists.samba.org/archive/linux-cifs-client/attachments/20080512/4c081cde/attachment.bin
More information about the linux-cifs-client
mailing list