Linux NFS development
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Spencer Shepler <Spencer.Shepler@Sun.COM>
Cc: Stuart Anderson <anderson@ligo.caltech.edu>, nfs@lists.sourceforge.net
Subject: Re: NFSv4 uninitialized mtime
Date: Thu, 28 Jun 2007 09:32:12 -0400	[thread overview]
Message-ID: <20070628133212.GA26588@fieldses.org> (raw)
In-Reply-To: <2DD93BC2-E5C2-45C5-A054-D0580004E3AC@Sun.COM>

On Wed, Jun 27, 2007 at 10:59:10PM -0500, Spencer Shepler wrote:
> The Solaris NFSv3 server will, upon "get acl", map the underlying
> ZFS ACL format to the NFSv3/ACL format.  However, on setting of
> an acl, an error is returned (NOSUP).  The decision was made that
> because of the imperfect mapping on acl set in this path that
> an error would be returned.

Mapping back from an NFSv3 to an NFSv4 ACL should be pretty easy,
shouldn't it?  Especially if it's an ACL that was just fetched from
the server--so it shouldn't be particularly exotic.

> I believe the Solaris client would map the ENOTSUP back to the
> application as is and that may help the application adapt
> its behavior (avoid erroring out if that isn't desired).

But, yes, maybe cp could be smarter.

--b.

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2007-06-28 13:32 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-27 23:31 NFSv4 uninitialized mtime Stuart Anderson
2007-06-27 23:43 ` Trond Myklebust
2007-06-28  0:49   ` Stuart Anderson
2007-06-28  0:59     ` Stuart Anderson
2007-06-28  1:15       ` Jeff Layton
2007-06-28  2:53         ` Stuart Anderson
2007-06-28  3:09           ` Spencer Shepler
2007-06-28  3:23             ` Stuart Anderson
2007-06-28  3:30               ` Spencer Shepler
2007-06-28  3:44                 ` Stuart Anderson
2007-06-28  3:59                   ` Spencer Shepler
2007-06-28 13:32                     ` J. Bruce Fields [this message]
2007-06-28 10:41           ` Jeff Layton
2007-06-28 12:01             ` Jeff Layton
2007-06-28 13:19               ` Trond Myklebust
2007-06-28 13:29                 ` Jeff Layton
     [not found] <nfs-valinux.20070628064127.a769bc53.jlayton@redhat.com>
     [not found] ` <46857F06.102@ligo.caltech.edu>
     [not found]   ` <20070629181234.b70f6f7f.jlayton@redhat.com>
2007-06-29 22:31     ` Erik A. Espinoza
2007-06-30  2:35       ` Jeff Layton
2007-06-30  3:09         ` Erik A. Espinoza
2007-06-30 11:19           ` Jeff Layton

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=20070628133212.GA26588@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=Spencer.Shepler@Sun.COM \
    --cc=anderson@ligo.caltech.edu \
    --cc=nfs@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox