From: Stuart Anderson <anderson@ligo.caltech.edu>
To: Spencer Shepler <Spencer.Shepler@Sun.COM>
Cc: nfs@lists.sourceforge.net
Subject: Re: NFSv4 uninitialized mtime
Date: Wed, 27 Jun 2007 20:44:55 -0700 [thread overview]
Message-ID: <20070628034455.GD18337@ligo.caltech.edu> (raw)
In-Reply-To: <CACFA76B-43D8-454C-B06A-AAA4EF38A033@Sun.COM>
On Wed, Jun 27, 2007 at 10:30:22PM -0500, Spencer Shepler wrote:
>
> On Jun 27, 2007, at 10:23 PM, Stuart Anderson wrote:
>
> >On Wed, Jun 27, 2007 at 10:09:23PM -0500, Spencer Shepler wrote:
> >>>Somewhat related is the reason that we are tring NFSV4 on Linux
> >>>clients is
> >>>that with NFSV3 ACL's do not work between Linux and Solaris if the
> >>>filesystem
> >>>on the Solaris server is ZFS, e.g., cp -p will generate interesting
> >>>error
> >>>messages. While I would rather stay with NFSV4 if possible, has
> >>>anyone
> >>>gotten this configuration to work with V3?
> >>
> >>It will not. ZFS does not support the "old" ACL definition; only
> >>NFSv4 support.
> >>
> >
> >Understood, so this is probably not a bug and just a feature, but why
> >does a Linux client try and then generate application level errors?
> >A Solaris client is willing to NFS mount vers=3 a ZFS filesystem
> >and then
> >run GNU cp -rp, for example, without complaint. Perhaps there is a
> >simple
> >method determine if ACL's are available/supported on a particular NFS
> >mount?
>
> Does it fail on the "get" or "set" of the ACL?
set
Here is an strace snippet from running cp -rp on a Linux NFSV3 client
of a Solaris 10 ZFS server:
getxattr("test1/oink", "system.posix_acl_access", "\x02\x00\x00\x00\x01\x00\x06\x00\xff\xff\xff\xff\x04\x00\x04\x00\xff\xff\xff\xff\x10\x00\x07\x00\xff\xff\xff\xff \x00\x04\x00\xff\xff\xff\xff", 132) = 36
setxattr("test2/oink", "system.posix_acl_access", "\x02\x00\x00\x00\x01\x00\x06\x00\xff\xff\xff\xff\x04\x00\x04\x00\xff\xff\xff\xff\x10\x00\x07\x00\xff\xff\xff\xff \x00\x04\x00\xff\xff\xff\xff", 36, 0) = -1 EINVAL (Invalid argument)
We used to have this same problem with Linux NFSV3 mounts from Solaris QFS servers
as well, but that was fixed in a recent update to QFS, so I am not really sure
who is "responsible" for bridging ACL's between the old/new schemes.
Thanks.
--
Stuart Anderson anderson@ligo.caltech.edu
http://www.ligo.caltech.edu/~anderson
-------------------------------------------------------------------------
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
next prev parent reply other threads:[~2007-06-28 3:45 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 [this message]
2007-06-28 3:59 ` Spencer Shepler
2007-06-28 13:32 ` J. Bruce Fields
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=20070628034455.GD18337@ligo.caltech.edu \
--to=anderson@ligo.caltech.edu \
--cc=Spencer.Shepler@Sun.COM \
--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;
as well as URLs for NNTP newsgroup(s).