From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Subject: Re: rsync from xfs to nfs+xfs and ACL problems
Date: Wed, 19 May 2010 13:04:37 +0200 [thread overview]
Message-ID: <201005191304.42314@zmi.at> (raw)
In-Reply-To: <20100518123304.GH2150@dastard>
[-- Attachment #1.1: Type: Text/Plain, Size: 1120 bytes --]
On Dienstag, 18. Mai 2010 Dave Chinner wrote:
> NFSv3 doesn't support ACLs, IIRC.
Thank you for the hint. I remounted with nfs4 now:
type nfs4 (rw,noatime,nodiratime,rsize=65536,wsize=65536,tcp,intr,acl)
And now I get this on "rsync -aPvHAX":
rsync: chown "somedir/Cen731n.afm" failed: Invalid argument (22)
rsync: chown "somedir/Teil2" failed: Invalid argument (22)
rsync: rsync_xal_set:
lsetxattr("somedir/Teil2/IMAGE.CCD","trusted.SGI_ACL_FILE") failed:
Operation not supported (95)
I changed again and defined an rsync module on the target, making a
direct rsync and no more shown errors. Still, what is causing the tons
of errors when rsyncing to nfs+xfs, no matter if nfs3 or nfs4? I looked
manually at some files and it seems everything was copied well, despite
the errors.
Could inode64 be a problem here?
--
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:02 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 [this message]
2010-05-19 11:20 ` Christoph Hellwig
2010-05-19 11:46 ` Michael Monnerie
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=201005191304.42314@zmi.at \
--to=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