public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Jon Forrest <jlforrest-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: linux-nfs@vger.kernel.org
Cc: nfsv4@linux-nfs.org
Subject: (ANSWER) Question About nfs3 vs. nfs4 Semantics On Sun 7310 Server
Date: Wed, 04 Nov 2009 14:40:21 -0800	[thread overview]
Message-ID: <hcsvs6$dbl$1@ger.gmane.org> (raw)

The other day I posted the description below of a problem
I was having when I was mounting from a Sun 7310
server using NFSv3 and NFSv4 from a CentOS 5.3
client.

It turned out that the solution was trivial - all
I needed to do was to use the "noacl" option
in my NFSv3 mount command. I still think that the
client shouldn't have complained about not
being able to preserve file protections since
it was actually to do so.

I'm still not sure if I should try NFSv4 but that's
another issue.

Cordially,

-- 
Jon Forrest
Research Computing Support
College of Chemistry
173 Tan Hall
University of California Berkeley
Berkeley, CA
94720-1460
510-643-1032

1    [nfs3]# touch x
2    [nfs3]# cp -p x y
3    cp: preserving permissions for `y': Operation not supported
4    cp: preserving ACL for `y': Operation not supported
5    [nfs3]# ls -l
6    total 1
7    -rw-r--r--+ 1 root root 0 Nov  3 14:46 x
8    -rw-r--r--+ 1 root root 0 Nov  3 14:46 y
9    [nfs3]# cd /tmp/x/home/jlforrest/nfs4
10   [nfs4]# touch x
11   [nfs4]# cp -p x y
12   [nfs4]# ls -l
13   total 1
14   -rw-rw-r-- 1 nobody nobody 0 Nov  3 14:48 x
15   -rw-rw-r-- 1 nobody nobody 0 Nov  3 14:48 y



             reply	other threads:[~2009-11-04 22:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-04 22:40 Jon Forrest [this message]
2009-11-05 19:55 ` (ANSWER) Question About nfs3 vs. nfs4 Semantics On Sun 7310 Server J. Bruce Fields
2009-11-05 21:32   ` Jon Forrest

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='hcsvs6$dbl$1@ger.gmane.org' \
    --to=jlforrest-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=nfsv4@linux-nfs.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