From: "Stefan Bauer" <sb@plzk.de>
To: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: posix acl to nfs4 acl mapping - status?
Date: Fri, 26 Sep 2014 17:08:15 +0200 [thread overview]
Message-ID: <zarafa.5425815f.6e31.1b72722237f64a60@srv1.localhost> (raw)
Hi,
I'm just a regular sysadmin and want to use NFS4 shares for backup purpose and keep existing posix acls from local filesystems during transfer.
It seems to not be supported:
root@s1:/# mount.nfs4 -o acl 192.168.0.254:/ /bla
root@s1:/# cp -Rvp omg /bla/
‘omg’ -> ‘/bla/omg’
cp: preserving permissions for ‘/bla/omg’: Operation not supported
What is the status on that? I'm aware of nfs4_getfacl but dont want to adjust permissions manually.
I also found https://tools.ietf.org/html/draft-ietf-nfsv4-acl-mapping-05 which describes a working algorithm for posix->nfs4 mapping but no evidence whether this is implemented and if so - how.
I'm using Debian testing with kernel 3.14.3.4 #5 SMP Thu May 8 16:31:22 CEST 2014 x86_64 GNU/Linux.
mount.nfs4: (linux nfs-utils 1.2.8)
Kind regards
Stefan
next reply other threads:[~2014-09-26 15:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-26 15:08 Stefan Bauer [this message]
2014-09-26 16:11 ` posix acl to nfs4 acl mapping - status? Frank Filz
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=zarafa.5425815f.6e31.1b72722237f64a60@srv1.localhost \
--to=sb@plzk.de \
--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