From: "Stefan Bauer" <sb@plzk.de>
To: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: AW: posix acl to nfs4 acl mapping - status?
Date: Fri, 26 Sep 2014 23:37:45 +0200 [thread overview]
Message-ID: <zarafa.5425dca9.74f9.5487c582799de56d@srv1.localhost> (raw)
-----Ursprüngliche Nachricht-----
Von: Frank Filz <ffilzlnx@mindspring.com>
> I believe the implementation follows this document. I do know that several
> years ago, we had some significant ACL testing using AIX clients that exposed
> many issues in the translation.
>
> Unfortunately, the translation is always doomed to be imperfect, and is
> probably not suitable for backup-purposes. Any POSIX ACL that includes a mask
> will certainly be changed to lose that mask (with the CURRENT effect of the
> mask being applied permanently).
Even though the implementation might not be complete and flags would get lost, i would assume to get at least a different error message than Operation not supported during copy.
I already found a solution for my backup-problem (saving acls in an additional file).
Thanks.
Stefan
reply other threads:[~2014-09-26 21:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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.5425dca9.74f9.5487c582799de56d@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