From: Andreas Dilger <adilger@clusterfs.com>
To: Andreas Gruenbacher <agruen@suse.de>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
linux-fsdevel@vger.kernel.org, Jeff Sedlak <jsedlak@umich.edu>,
nfs@lists.sourceforge.net,
Marius Aamodt Eriksen <marius@umich.edu>
Subject: Re: Problems with POSIX ACL <=> NFSv4 ACL mapping in mainline
Date: Mon, 26 Jun 2006 11:52:13 -0600 [thread overview]
Message-ID: <20060626175213.GU5817@schatzie.adilger.int> (raw)
In-Reply-To: <200606261730.09827.agruen@suse.de>
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"? 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.
It would probably be preferrable that cp only copy EAs that it understands.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2006-06-26 17:52 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 [this message]
2006-06-26 18:07 ` Andreas Gruenbacher
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=20060626175213.GU5817@schatzie.adilger.int \
--to=adilger@clusterfs.com \
--cc=agruen@suse.de \
--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).