linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick Goetz <pgoetz@math.utexas.edu>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: linux-nfs@vger.kernel.org
Subject: Re: kerberized NFSv4 client reporting operation not permitted when mounting with sec=sys
Date: Mon, 6 Jul 2020 14:57:52 -0500	[thread overview]
Message-ID: <4fe2af1f-917e-c1e4-f5e6-05eb0c121511@math.utexas.edu> (raw)
In-Reply-To: <20200706171804.GA31789@fieldses.org>

On 7/6/20 12:18 PM, J. Bruce Fields wrote:
> 
> Note, by the way, that fsid=0 thing was required for nfsv4 exports years
> ago, but no longer is.  It's usually better not to bother with that.
> 


Are we ever going to get some solid up-to-date NFSv4/pNFS documentation? 
  I'm sufficiently frustrated to write it myself, but am not 100% sure 
where to start.



  reply	other threads:[~2020-07-06 20:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-22  9:22 kerberized NFSv4 client reporting operation not permitted when mounting with sec=sys Felix Rubio
2020-01-22 18:30 ` Benjamin Coddington
2020-01-23  9:03   ` Felix Rubio
2020-01-24 14:45     ` Benjamin Coddington
2020-01-24 16:49       ` Felix Rubio
2020-02-04 19:14         ` Benjamin Coddington
2020-02-05 11:09           ` Felix Rubio
     [not found]       ` <b0bcd3e608d6fbc05c0751380f6a0e7b@kngnt.org>
     [not found]         ` <7B337925-F225-4DD7-A8CF-ECBBE1AC7082@redhat.com>
2020-07-02 13:41           ` Felix Rubio
2020-07-02 16:52             ` Dai Ngo
2020-07-02 17:52               ` Felix Rubio
2020-07-06 17:18                 ` J. Bruce Fields
2020-07-06 19:57                   ` Patrick Goetz [this message]
2020-07-06 20:27                     ` J. Bruce Fields
2020-07-07 15:10                       ` Patrick Goetz
2020-07-07 15:51                         ` J. Bruce Fields

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=4fe2af1f-917e-c1e4-f5e6-05eb0c121511@math.utexas.edu \
    --to=pgoetz@math.utexas.edu \
    --cc=bfields@fieldses.org \
    --cc=linux-nfs@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;
as well as URLs for NNTP newsgroup(s).