All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: chucklever@gmail.com
Cc: Jari Aalto <jari.aalto-w6EBCRcXQ4deoWH0uzbU5w@public.gmane.org>,
	NFS HOWTO author <smithere@gmail.com>,
	"http://linux-nfs.org" <linux-nfs@vger.kernel.org>,
	chip@users.sourceforge.net, hjl@users.sourceforge.net,
	jbfields@users.sourceforge.net, jweber@users.sourceforge.net,
	marcmerlin@users.sourceforge.net,
	neilbrown@users.sourceforge.net,
	steved12345@users.sourceforge.net, trondmy@users.sourceforge.net
Subject: Re: Linux NFS-HOWTO - improvement to Troubleshooting permission denied
Date: Mon, 25 Aug 2008 11:55:03 -0400	[thread overview]
Message-ID: <20080825155503.GH30871@fieldses.org> (raw)
In-Reply-To: <76bd70e30808250841v4e73c576qc1e68c85d88bb989-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On Mon, Aug 25, 2008 at 11:41:02AM -0400, Chuck Lever wrote:
> Hi Jari-
> 
> On Mon, Aug 25, 2008 at 3:36 AM, Jari Aalto <jari.aalto-w6EBCRcXQ4deoWH0uzbU5w@public.gmane.org> wrote:
> >
> > Thank you for the NFS howto (last modified 2006). Please add further
> > diagnostics to section:
> >
> >        => "I do not have permission to access files on the mounted volume"
> >        http://nfs.sourceforge.net/nfs-howto/ar01s07.html#pemission_issues
> >
> > The error condition "Permission denied" also happens in certain NFS
> > (client/server) combinations and the workaround is to add additional
> > mount parameter at client:
> >
> >        sec=sys
> >
> > Please add this to the "#pemission_issues" (tag the word seems to have a
> > small typo).
> 
> This is a known bug in nfs-utils 1.1.3 when used with older client
> kernels that do not support text-based mounts.
> 
> Seems like an esoteric (ie not widespread) problem, but I could easily
> be wrong about that.

People should be able to upgrade nfs-utils without upgrading their
kernel!

The referenced debian bug report:

	http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=492970

claims the first bad commit is a server-side commit that itself seems to
claim to work around a problem?  ("For mountd, it does not advertise
AUTH_NULL anymore. This is necessary to avoid backward compatibility
issue. If AUTH_NULL appears in the list, either the new or the old
client will choose that over AUTH_SYS.")

Did we ever find the actual root cause?

--b.

  parent reply	other threads:[~2008-08-25 15:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-25  7:36 Linux NFS-HOWTO - improvement to Troubleshooting permission denied Jari Aalto
     [not found] ` <87skstbl7j.fsf-S166JWPS1wRq3zrG9Zoazw@public.gmane.org>
2008-08-25 15:41   ` Chuck Lever
     [not found]     ` <76bd70e30808250841v4e73c576qc1e68c85d88bb989-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-08-25 15:55       ` J. Bruce Fields [this message]
2008-08-25 16:55         ` Chuck Lever
2008-08-25 20:50       ` Jari Aalto

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=20080825155503.GH30871@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=chip@users.sourceforge.net \
    --cc=chucklever@gmail.com \
    --cc=hjl@users.sourceforge.net \
    --cc=jari.aalto-w6EBCRcXQ4deoWH0uzbU5w@public.gmane.org \
    --cc=jbfields@users.sourceforge.net \
    --cc=jweber@users.sourceforge.net \
    --cc=linux-nfs@vger.kernel.org \
    --cc=marcmerlin@users.sourceforge.net \
    --cc=neilbrown@users.sourceforge.net \
    --cc=smithere@gmail.com \
    --cc=steved12345@users.sourceforge.net \
    --cc=trondmy@users.sourceforge.net \
    /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.