All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jari Aalto <jari.aalto-w6EBCRcXQ4deoWH0uzbU5w@public.gmane.org>
To: smithere@gmail.com (NFS HOWTO author)
Cc: linux-nfs@vger.kernel.org (http://linux-nfs.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: Linux NFS-HOWTO - improvement to Troubleshooting permission denied
Date: Mon, 25 Aug 2008 10:36:00 +0300	[thread overview]
Message-ID: <87skstbl7j.fsf@jondo.cante.net> (raw)


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).

See reported incidents:

        http://thread.gmane.org/gmane.linux.debian.user/333162
        http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=492970

Jari

----
CC: team http://sourceforge.net/projects/nfs

You're all in CC, as I did not know who is responsible for updating the
NFS-HOWTO at sourceforge.

             reply	other threads:[~2008-08-25  7:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-25  7:36 Jari Aalto [this message]
     [not found] ` <87skstbl7j.fsf-S166JWPS1wRq3zrG9Zoazw@public.gmane.org>
2008-08-25 15:41   ` Linux NFS-HOWTO - improvement to Troubleshooting permission denied Chuck Lever
     [not found]     ` <76bd70e30808250841v4e73c576qc1e68c85d88bb989-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-08-25 15:55       ` J. Bruce Fields
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=87skstbl7j.fsf@jondo.cante.net \
    --to=jari.aalto-w6ebcrcxq4deowh0uzbu5w@public.gmane.org \
    --cc=chip@users.sourceforge.net \
    --cc=hjl@users.sourceforge.net \
    --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.