public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Wu Fengguang <fengguang.wu@intel.com>
To: Chuck Lever <Chuck.Lever@oracle.com>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
	NFS list <linux-nfs@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: mount.nfs: access denied by server
Date: Sat, 22 Aug 2009 09:48:19 +0800	[thread overview]
Message-ID: <20090822014819.GA7798@localhost> (raw)
In-Reply-To: <8C4C4FD5-733E-4327-8618-8C400FAE72C1@oracle.com>

On Sat, Aug 22, 2009 at 01:50:52AM +0800, Chuck Lever wrote:
> 
> On Aug 20, 2009, at 10:36 PM, Trond Myklebust wrote:
> 
> > On Fri, 2009-08-21 at 09:27 +0800, Wu Fengguang wrote:
> >> On Thu, Aug 20, 2009 at 09:02:29PM +0800, Trond Myklebust wrote:
> >>> On Thu, 2009-08-20 at 15:13 +0800, Wu Fengguang wrote:
> >>>> Hi,
> >>>>
> >>>> After upgrading NFS client kernel to latest linux-next, NFS mount
> >>>> failed:
> >>>>
> >>>>        # mount -t nfs pxe:/cc /cc
> >>>>        mount.nfs: access denied by server while mounting pxe:/cc
> >>>>
> >>>>        # uname -a
> >>>>        Linux hp 2.6.31-rc6-next-20090818 #61 SMP Thu Aug 20  
> >>>> 14:46:10 CST 2009 x86_64 GNU/Linux
> >>>>
> >>>> However server log says OK:
> >>>>
> >>>>        Aug 20 15:02:09 wu-t61 mountd[4599]: authenticated mount  
> >>>> request from 192.168.11.6:973 for /cc (/cc)
> >>>>        Aug 20 15:02:09 wu-t61 mountd[4599]: authenticated unmount  
> >>>> request from 192.168.11.6:974 for /cc (/cc)
> >>>>
> >>>> However-2: nfsroot can be mounted at boot time. Server kernel has  
> >>>> always been 2.6.30.
> >>>>
> >>>> Any ideas?
> >>>>
> >>>> Thanks,
> >>>> Fengguang
> >>>
> >>> Can you try again after enabling mount debugging on the NFS client?
> >>>
> >>> echo 512 > /proc/sys/sunrpc/nfs_debug
> >>
> >> I used 1024 and found the mount failed here in nfs_walk_authlist():
> >>
> >>        dfprintk(MOUNT, "NFS: server does not support requested auth  
> >> flavor\ n");
> >>        nfs_umount(request);
> >
> > Thanks Fengguang!
> >
> > Chuck, this looks like one of yours. Could it be that you are hitting
> > the same Linux knfsd bug that Tom Haynes saw with a Solaris client?
> > AFAICR, the problem was that existing nfs servers do not set a default
> > auth flavour, and so you just have to try with auth_sys and see if it
> > succeeds...
> 
> With 1024 set, the mount client's XDR routines should have listed the  
> server's flavors, if any, in the system log.  Should be something like  
> "NFS: received 0 auth flavors" if the server didn't return any.  Can  
> you confirm that?

Yes. The full logs are:


Aug 21 09:54:38 hp kernel: [   74.671552] NFS: nfs mount opts='nolock,addr=192.168.11.2'
Aug 21 09:54:38 hp kernel: [   74.677150] NFS:   parsing nfs mount option 'nolock'
Aug 21 09:54:38 hp kernel: [   74.682204] NFS:   parsing nfs mount option 'addr=192.168.11.2'
Aug 21 09:54:38 hp kernel: [   74.688234] NFS: MNTPATH: '/cc'
Aug 21 09:54:38 hp kernel: [   74.691468] NFS: sending MNT request for pxe:/cc
Aug 21 09:54:38 hp kernel: [   74.704458] NFS: received 0 auth flavors
Aug 21 09:54:38 hp kernel: [   74.708587] NFS: MNT request succeeded
Aug 21 09:54:38 hp kernel: [   74.712435] NFS: server does not support requested auth flavor
Aug 21 09:54:38 hp kernel: [   74.718358] NFS: sending UMNT request for pxe:/cc


> I'll try to post a fix later today.

Thanks!

Fengguang

      reply	other threads:[~2009-08-22  1:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-20  7:13 mount.nfs: access denied by server Wu Fengguang
2009-08-20  7:19 ` Wu Fengguang
2009-08-20 13:02 ` Trond Myklebust
2009-08-21  1:27   ` Wu Fengguang
2009-08-21  2:36     ` Trond Myklebust
2009-08-21 17:50       ` Chuck Lever
2009-08-22  1:48         ` Wu Fengguang [this message]

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=20090822014819.GA7798@localhost \
    --to=fengguang.wu@intel.com \
    --cc=Chuck.Lever@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trond.myklebust@fys.uio.no \
    /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