From: Steve French <smfrench@gmail.com>
To: Gerhard Hintermayer <gerhard.hintermayer@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: mounting cifs filesystems not possible
Date: Thu, 23 Jul 2009 02:44:30 -0500 [thread overview]
Message-ID: <524f69650907230044u5ab44c59y91bc9b808f5fd6c3@mail.gmail.com> (raw)
In-Reply-To: <d8bd05e00907222324q26b8faa0i2d85f4d7e35d8198@mail.gmail.com>
On Thu, Jul 23, 2009 at 1:24 AM, Gerhard
Hintermayer<gerhard.hintermayer@gmail.com> wrote:
> See my original post to LKML at http://lkml.org/lkml/2009/7/15/217.
> You can see kernel version, and dmesg output (including cifsFYI set to
> 7) there.
> I did file a bug report to gentoo bug list and lkml. Shall I also do
> so for bugzilla.samba.org ? I think it's more kernel related.
>
> The DebugData of the share I'm trying to mount (fortunaltely I got a
> mount -t cifs -o user=aprol,password=*****,ip=10.5.12.105 //BRKVN05/AtlasPM /mnt/AtlasPM
The mount syntax you listed in your post is a little strange with the
mount options preceding rather than following the UNC name and device,
ie rather than the usual:
mount.cifs {//unc-name} {mount-point} [-o options]
It looks like the first 3/4 of mount succeeded (setting up a session,
and connecting to the share) to the point of doing the lookup of the
root directory of the share (which I don't see in your trace).
Typically there have been the following reasons for that to fail:
1) the user has no permission on the root of the share
or
2) the root of the share is a dfs referral to another server (this
should work now, but was probably not supported a few kernel releases
ago)
or
3) the server reports that the root directory is not a directory (ie
is a file for example)
It may be that an earlier mount failed perhaps oopsing in the vfs, and
that could have left an existing cifs session and tree connection
which made it seem like a later mount worked (since it found an
existing session) but that seems unlikely.
It would be helpful to see if the client did a network request (in
this case SMB transact2 Query Path Info) on the root directory of the
share, so if you have a wireshark trace that would be useful.
--
Thanks,
Steve
next prev parent reply other threads:[~2009-07-23 7:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-17 8:22 Gerhard Hintermayer
[not found] ` <20090722161312.8c2ab4b5.akpm@linux-foundation.org>
2009-07-23 5:26 ` Gerhard Hintermayer
2009-07-23 6:10 ` Steve French
2009-07-23 6:24 ` Gerhard Hintermayer
2009-07-23 7:44 ` Steve French [this message]
2009-07-23 8:08 ` Gerhard Hintermayer
2009-07-23 8:27 ` Steve French
-- strict thread matches above, loose matches on Subject: below --
2009-07-15 15:32 Gerhard Hintermayer
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=524f69650907230044u5ab44c59y91bc9b808f5fd6c3@mail.gmail.com \
--to=smfrench@gmail.com \
--cc=gerhard.hintermayer@gmail.com \
--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
all inboxes | Powered by JetHome®