From: Andreas Gruenbacher <agruen@suse.de>
To: Andreas Dilger <adilger@clusterfs.com>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
Marius Aamodt Eriksen <marius@umich.edu>,
Jeff Sedlak <jsedlak@umich.edu>,
linux-fsdevel@vger.kernel.org, nfs@lists.sourceforge.net
Subject: Re: Problems with POSIX ACL <=> NFSv4 ACL mapping in mainline
Date: Mon, 26 Jun 2006 20:07:55 +0200 [thread overview]
Message-ID: <200606262007.56097.agruen@suse.de> (raw)
In-Reply-To: <20060626175213.GU5817@schatzie.adilger.int>
On Monday, 26 June 2006 19:52, Andreas Dilger wrote:
> On Jun 26, 2006 17:30 +0200, Andreas Gruenbacher wrote:
> > The result were errors when copying files with cp -p (which preserves
> > xattrs).
>
> Is that true of "cp" in general, or only SuSE "cp"?
It's our cp only right now.
> We get problems with
> Lustre when root is copying files, because SuSE cp is incorrectly trying to
> copy all of the EAs by default. If I have an EA that is specific to a
> file I don't necessarily want it to be copied.
There's a blacklist in libattr which we could add Lustre attributes to. A
blacklist somewhere in /etc would be even better though I guess.
> It would probably be preferrable that cp only copy EAs that it understands.
What to do with unknown attributes? Warn? Err out?
Andreas
next prev parent reply other threads:[~2006-06-26 18:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-23 15:45 Problems with POSIX ACL <=> NFSv4 ACL mapping in mainline Andreas Gruenbacher
2006-06-23 16:06 ` J. Bruce Fields
2006-06-26 15:30 ` Andreas Gruenbacher
2006-06-26 16:23 ` J. Bruce Fields
2006-06-26 17:52 ` Andreas Dilger
2006-06-26 18:07 ` Andreas Gruenbacher [this message]
2006-06-26 18:57 ` Andreas Dilger
2006-06-24 13:21 ` [NFS] " Christoph Hellwig
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=200606262007.56097.agruen@suse.de \
--to=agruen@suse.de \
--cc=adilger@clusterfs.com \
--cc=bfields@fieldses.org \
--cc=jsedlak@umich.edu \
--cc=linux-fsdevel@vger.kernel.org \
--cc=marius@umich.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;
as well as URLs for NNTP newsgroup(s).