From: Jeff Layton <jlayton@redhat.com>
To: Christoph Lameter <cl@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, samba@lists.samba.org,
linux-cifs-client@lists.samba.org
Subject: Re: 2.6.31-rc8: CIFS with 5 seconds hiccups
Date: Thu, 10 Sep 2009 20:19:32 -0400 [thread overview]
Message-ID: <20090910201932.5b8356e2@tlielax.poochiereds.net> (raw)
In-Reply-To: <alpine.DEB.1.10.0909101721180.27669@V090114053VZO-1>
On Thu, 10 Sep 2009 17:27:53 -0400 (EDT)
Christoph Lameter <cl@linux-foundation.org> wrote:
> Right. 32 bit cannot mount the clameter directory for strange reasons. I
> have to go one level higher.
[...]
> One other issue that may be important: The mounting operation is very slow
> on 32 bit. Could it be that the handshake does not work out?
Ok, looks like the 64 bit client is using a different level of interest
than the 32 bit on the FIND_FIRST call. I suspect that that difference
may account for the difference in response time.
It's not completely clear to me why that would be. Maybe a windows bug
that causes a slowdown with that LOI?
In any case, I think we need to look closely at what's happening at
mount time. First, I'll need some other info:
1) output of "/sbin/mount.cifs -V" from both machines
2) mount options that you're using on both boxes
3) wire captures from mount attempts on both machines. Try to mount the
"clameter" dir on both boxes and do captures of each attempt. Maybe
this time use -s 0 with tcpdump so we get all of the traffic.
There may be crackable password hashes in the captures, so you may want
to send them to me privately and not cc the list.
Thanks,
--
Jeff Layton <jlayton@redhat.com>
next prev parent reply other threads:[~2009-09-11 0:20 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-04 16:27 Christoph Lameter
2009-09-05 11:10 ` Jeff Layton
2009-09-09 16:33 ` Christoph Lameter
2009-09-09 16:53 ` Jeff Layton
2009-09-09 17:07 ` Christoph Lameter
2009-09-09 17:20 ` Jeff Layton
2009-09-09 17:28 ` Christoph Lameter
2009-09-09 18:02 ` Jeff Layton
2009-09-09 21:27 ` Christoph Lameter
2009-09-10 0:55 ` Jeff Layton
2009-09-10 18:53 ` Christoph Lameter
2009-09-10 19:33 ` Jeff Layton
2009-09-10 19:42 ` Christoph Lameter
2009-09-10 20:57 ` Jeff Layton
2009-09-10 21:27 ` Christoph Lameter
2009-09-11 0:19 ` Jeff Layton [this message]
2009-09-14 20:10 ` Christoph Lameter
2009-09-15 22:34 ` Jeff Layton
2009-09-16 16:26 ` Christoph Lameter
2009-09-18 14:24 ` Jeff Layton
2009-09-14 20:16 ` (64 bit dump) " Christoph Lameter
2009-09-10 21:42 ` Christoph Lameter
2009-09-09 17:33 ` Christoph Lameter
2009-09-09 17:57 ` Jeff Layton
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=20090910201932.5b8356e2@tlielax.poochiereds.net \
--to=jlayton@redhat.com \
--cc=cl@linux-foundation.org \
--cc=linux-cifs-client@lists.samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=samba@lists.samba.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
all inboxes | Powered by JetHome®