From: Helge Hafting <helge.hafting@hist.no>
To: Suresh Jayaraman <sjayaraman@suse.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-cifs <linux-cifs@vger.kernel.org>
Subject: Re: [2.6.39] CIFS write failures where 2.6.38 works
Date: Fri, 03 Jun 2011 17:11:05 +0200 [thread overview]
Message-ID: <4DE8F989.50208@hist.no> (raw)
In-Reply-To: <4DE8B449.2000008@suse.de>
On 03. juni 2011 12:15, Suresh Jayaraman wrote:
> [Cc linux-cifs@vger.kernel.org]
>
> On 06/01/2011 03:41 PM, Helge Hafting wrote:
>> 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.
>
> What is the security mechanism you are using? If you seeing the problem
> with ntlm, could you try using ntlmv2 and see whether the problem is
> reproducible?
In the beginning, I did not specify the mechanism. So, whatever the
default is.
The fstab entry was like this:
\\servername\resource /mountpoint cifs
domain=MYDOMAIN,credentials=/etc/fstabcred,rw,noauto,iocharset=utf8,uid=username,gid=group,sockopt=TCP_NODELAY,users,file_mode=0640,dir_mode=0750,relatime
0 0
I looked at cifs options, and tried to add "sign" and "sec=ntlmv2i". It
made no difference. Still failure with 2.6.39, and mounting with these
new options works fine with 2.6.38
Helge Hafting
next prev parent reply other threads:[~2011-06-03 15:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-01 10:11 [2.6.39] CIFS write failures where 2.6.38 works Helge Hafting
2011-06-03 10:15 ` Suresh Jayaraman
2011-06-03 10:50 ` Jeff Layton
2011-06-03 15:11 ` Helge Hafting [this message]
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=4DE8F989.50208@hist.no \
--to=helge.hafting@hist.no \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sjayaraman@suse.de \
/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