From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Cc: Christoph Hellwig <hch@infradead.org>
Subject: Re: rsync from xfs to nfs+xfs and ACL problems
Date: Wed, 19 May 2010 13:46:38 +0200 [thread overview]
Message-ID: <201005191346.38699@zmi.at> (raw)
In-Reply-To: <20100519112034.GA29064@infradead.org>
[-- Attachment #1.1: Type: Text/Plain, Size: 910 bytes --]
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?
--
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc
it-management Internet Services
http://proteger.at [gesprochen: Prot-e-schee]
Tel: 0660 / 415 65 31
// Wir haben im Moment zwei Häuser zu verkaufen:
// http://zmi.at/langegg/
// http://zmi.at/haus2009/
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-05-19 11:44 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 [this message]
2010-05-19 11:51 ` Christoph Hellwig
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=201005191346.38699@zmi.at \
--to=michael.monnerie@is.it-management.at \
--cc=hch@infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.