All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Helge Hafting <helge.hafting-CND4fxrytsY@public.gmane.org>
Cc: Suresh Jayaraman <sjayaraman-l3A5Bk7waGM@public.gmane.org>,
	Linux Kernel Mailing List
	<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	linux-cifs <linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [2.6.39] CIFS write failures where 2.6.38 works
Date: Thu, 9 Jun 2011 18:28:45 -0400	[thread overview]
Message-ID: <20110609182845.1ebfc678@tlielax.poochiereds.net> (raw)
In-Reply-To: <4DE8F989.50208-CND4fxrytsY@public.gmane.org>

On Fri, 03 Jun 2011 17:11:05 +0200
Helge Hafting <helge.hafting-CND4fxrytsY@public.gmane.org> wrote:

> On 03. juni 2011 12:15, Suresh Jayaraman wrote:
> > [Cc linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

WARNING: multiple messages have this Message-ID (diff)
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
Date: Thu, 9 Jun 2011 18:28:45 -0400	[thread overview]
Message-ID: <20110609182845.1ebfc678@tlielax.poochiereds.net> (raw)
In-Reply-To: <4DE8F989.50208@hist.no>

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>

  parent reply	other threads:[~2011-06-09 22:28 UTC|newest]

Thread overview: 18+ 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
     [not found] ` <4DE6103E.6010100-CND4fxrytsY@public.gmane.org>
2011-06-03 10:15   ` Suresh Jayaraman
2011-06-03 10:15     ` Suresh Jayaraman
     [not found]     ` <4DE8B449.2000008-l3A5Bk7waGM@public.gmane.org>
2011-06-03 10:50       ` Jeff Layton
2011-06-03 10:50         ` Jeff Layton
2011-06-03 15:11     ` Helge Hafting
     [not found]       ` <4DE8F989.50208-CND4fxrytsY@public.gmane.org>
2011-06-04 12:35         ` Shirish Pargaonkar
2011-06-04 12:35           ` Shirish Pargaonkar
2011-06-09 22:28         ` Jeff Layton [this message]
2011-06-09 22:28           ` Jeff Layton
     [not found]           ` <20110609182845.1ebfc678-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2011-06-22 20:36             ` Jeff Layton
2011-06-22 20:36               ` Jeff Layton
     [not found]               ` <20110622163612.45744bc2-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2011-06-23 11:25                 ` Helge Hafting
2011-06-23 11:25                   ` Helge Hafting
2011-06-23 12:00                   ` Jeff Layton
     [not found]                   ` <4E0322B0.8030102-CND4fxrytsY@public.gmane.org>
2011-06-23 18:58                     ` 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=20110609182845.1ebfc678@tlielax.poochiereds.net \
    --to=jlayton-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=helge.hafting-CND4fxrytsY@public.gmane.org \
    --cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=sjayaraman-l3A5Bk7waGM@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.