From: Andrew Martin <amartin-AQeFf1F/bRxBDgjK7y7TUQ@public.gmane.org>
To: linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: "CIFS VFS: SMB response too short (9 bytes)" when copying data from CIFS mount
Date: Mon, 28 Sep 2015 17:39:29 -0500 (CDT) [thread overview]
Message-ID: <1731839987.81462.1443479968995.JavaMail.zimbra@xes-inc.com> (raw)
In-Reply-To: <1936200018.81178.1443479619664.JavaMail.zimbra-AQeFf1F/bRxBDgjK7y7TUQ@public.gmane.org>
Hello,
I have tested this setup on Ubuntu 14.04 using 3.13.0-32-generic and
3.19.0-28-generic with the same results (cifs-utils 6.0 in both cases). I have a
CIFS mountpoint set up on the server with the following options:
ro,relatime,vers=1.0,cache=strict,username=myusername,domain=EXAMPLE,uid=0,noforceuid,gid=0,noforcegid,addr=192.168.1.4,unix,posixpaths,serverino,acl,rsize=1048576,wsize=65536,actimeo=1 0 0
I am then using rsync to sync data from the mountpoint to a local directory.
Shortly after starting rsync, I see dmesg fill up with this message repeated
hundreds of times:
CIFS VFS: SMB response too short (9 bytes)
At this point, if I watch the df output I see that no new data is being synced
locally. If I strace the rsync process, this sometimes makes rsync continue
syncing data for a minute or two, but eventually it stops again. Note that I
encountered this same issue a few months ago using perl:
http://permalink.gmane.org/gmane.linux.kernel.cifs/10640
What can I do to debug this? Is there a bug in the CIFS kernel driver?
Thanks,
Andrew Martin
next parent reply other threads:[~2015-09-28 22:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1936200018.81178.1443479619664.JavaMail.zimbra@xes-inc.com>
[not found] ` <1936200018.81178.1443479619664.JavaMail.zimbra-AQeFf1F/bRxBDgjK7y7TUQ@public.gmane.org>
2015-09-28 22:39 ` Andrew Martin [this message]
[not found] ` <1731839987.81462.1443479968995.JavaMail.zimbra-AQeFf1F/bRxBDgjK7y7TUQ@public.gmane.org>
2015-09-28 23:32 ` "CIFS VFS: SMB response too short (9 bytes)" when copying data from CIFS mount Steve French
[not found] ` <CAH2r5mvsZJ3Nn45Fqjhc8nd-PZZ_KYJxsPg19v7DCpkuMb1OLg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-09-29 16:04 ` Andrew Martin
[not found] ` <1744736878.52548.1443542655076.JavaMail.zimbra-AQeFf1F/bRxBDgjK7y7TUQ@public.gmane.org>
2015-09-29 16:21 ` Steve French
[not found] ` <CAH2r5ms0bbkhy_D4tRXqwN2nH5vyBH9Q0OrCTV7cm93=P3fgRw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-09-30 22:03 ` Andrew Martin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1731839987.81462.1443479968995.JavaMail.zimbra@xes-inc.com \
--to=amartin-aqeff1f/brxbdgjk7y7tuq@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox