From: Helge Hafting <helge.hafting@hist.no>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [2.6.39] CIFS write failures where 2.6.38 works
Date: Wed, 01 Jun 2011 12:11:10 +0200 [thread overview]
Message-ID: <4DE6103E.6010100@hist.no> (raw)
At work I use cifs for accessing a windows server. This has worked fine
for a long time, up to and including Debian's 2.6.38-2.
I just installed Debians's 2.6.39-1, and had to give up on it.
Mounting CIFS works, and I can see the files. But if I
try to make a new file (with cp), I get a long delay.
In this time, anything accessing CIFS will pause, including "ls".
CIFS eventually becomes unstuck, and I will find that my "ls" succeeded,
but the file copy did not. The file was created, but
with 0 size.
Trying to copy the file again results in another stall, and so on.
When I mount CIFS, I get this message:
CIFS VFS: Unexpected SMB signature
This happens with 2.6.38 as well as 2.6.39.
When writes fail in 2.6.39, I also get:
CIFS VFS: Send error in Close = -512
Followed by:
CIFS VFS: Server servername has not responded in 300 seconds.
Reconnecting...
I have also seen
CIFS VFS: Send error in Close = -512
and
CIFS VFS: Send error in read = -13
Helge Hafting
next reply other threads:[~2011-06-01 10:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-01 10:11 Helge Hafting [this message]
2011-06-03 10:15 ` [2.6.39] CIFS write failures where 2.6.38 works Suresh Jayaraman
2011-06-03 10:50 ` Jeff Layton
2011-06-03 15:11 ` Helge Hafting
2011-06-04 12:35 ` Shirish Pargaonkar
2011-06-09 22:28 ` Jeff Layton
2011-06-22 20:36 ` Jeff Layton
2011-06-23 11:25 ` Helge Hafting
2011-06-23 12:00 ` Jeff Layton
2011-06-23 18:58 ` Jeff Layton
2011-06-08 19:34 ` Maciej Rutecki
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=4DE6103E.6010100@hist.no \
--to=helge.hafting@hist.no \
--cc=linux-kernel@vger.kernel.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