Date: Thu, 9 Jun 2011 18:28:45 -0400
From: Jeff Layton <jlayton@redhat.com>
To: Helge Hafting <helge.hafting@hist.no>
Cc: Suresh Jayaraman <sjayaraman@suse.de>,
        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
Message-ID: <20110609182845.1ebfc678@tlielax.poochiereds.net>
In-Reply-To: <4DE8F989.50208@hist.no>
References: <4DE6103E.6010100@hist.no>
	<4DE8B449.2000008@suse.de>
	<4DE8F989.50208@hist.no>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 2002
Lines: 51

On Fri, 03 Jun 2011 17:11:05 +0200
Helge Hafting <helge.hafting@hist.no> wrote:

> 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
> 

I think we need to understand what's happening on the wire. Are you
still able to reproduce this? If so, can you turn up debug logging and
reproduce this?. Instructions for how to do that are here:

    http://wiki.samba.org/index.php/LinuxCIFS_troubleshooting#Enabling_Debugging

Also, it looks like someone opened a bug at kernel.org too:

    https://bugzilla.kernel.org/show_bug.cgi?id=36952

...so if you can attach the resulting log there, that would be great.

Thanks,
-- 
Jeff Layton <jlayton@redhat.com>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/