xfs
[Top] [All Lists]

Re: rsync from xfs to nfs+xfs and ACL problems

To: xfs@xxxxxxxxxxx
Subject: Re: rsync from xfs to nfs+xfs and ACL problems
From: Michael Monnerie <michael.monnerie@xxxxxxxxxxxxxxxxxxx>
Date: Wed, 19 May 2010 13:04:37 +0200
Cc: Dave Chinner <david@xxxxxxxxxxxxx>
In-reply-to: <20100518123304.GH2150@dastard>
Organization: it-management http://it-management.at
References: <201005181350.15308@xxxxxx> <20100518123304.GH2150@dastard>
User-agent: KMail/1.12.4 (Linux/2.6.31.12-0.2-desktop; KDE/4.3.5; x86_64; ; )
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: signature.asc
Description: This is a digitally signed message part.

<Prev in Thread] Current Thread [Next in Thread>