From: Christoph Hellwig <hch@infradead.org>
To: Michael Monnerie <michael.monnerie@is.it-management.at>
Cc: Christoph Hellwig <hch@infradead.org>, xfs@oss.sgi.com
Subject: Re: rsync from xfs to nfs+xfs and ACL problems
Date: Wed, 19 May 2010 07:51:51 -0400 [thread overview]
Message-ID: <20100519115151.GA19104@infradead.org> (raw)
In-Reply-To: <201005191346.38699@zmi.at>
On Wed, May 19, 2010 at 01:46:38PM +0200, Michael Monnerie wrote:
> On Mittwoch, 19. Mai 2010 Christoph Hellwig wrote:
> > XFS stores ACLs different than other Linux filesystems because it's
> > on-disk compatible to IRIX. While the other filesystems store the
> > ACL in the same format that is used for the user interface XFS
> > stores it in a separate trusted extended attribute. rsync should
> > and
> > traditionally has ignored those attributes, but it seems something in
> > rsync changed recently so that it tries to copy these attributes in
> > the trusted.* namespace, which fails on NFS.
>
> Thank you. Does that mean I can simply ignore that errors, and that
> everything is OK even over NFS?
Thinks should be okay - rsync probably has copied the ACLs via the
normal system namespace. You can verify this by doing a getfacl
on a nfs file that should havfe ACLs.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-05-19 11:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-18 11:50 rsync from xfs to nfs+xfs and ACL problems Michael Monnerie
2010-05-18 12:33 ` Dave Chinner
2010-05-19 11:04 ` Michael Monnerie
2010-05-19 11:20 ` Christoph Hellwig
2010-05-19 11:46 ` Michael Monnerie
2010-05-19 11:51 ` Christoph Hellwig [this message]
2010-05-20 22:05 ` Linda Walsh
2010-05-18 16:52 ` Emmanuel Florac
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=20100519115151.GA19104@infradead.org \
--to=hch@infradead.org \
--cc=michael.monnerie@is.it-management.at \
--cc=xfs@oss.sgi.com \
/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