All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linda Walsh <xfs@tlinx.org>
To: Michael Monnerie <michael.monnerie@is.it-management.at>,
	"xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: rsync from xfs to nfs+xfs and ACL problems
Date: Thu, 20 May 2010 15:05:03 -0700	[thread overview]
Message-ID: <4BF5B20F.1020400@tlinx.org> (raw)
In-Reply-To: <20100518123304.GH2150@dastard>

If the NFS system doesn't handle ACL's,
you might try using "star" which can handle ACL's and extended file attributes storing them in
an extended tar-format archive.

It has a "-copy" feature that I've used successfully to copy extended file attributes:
(cd sourcedir; star -acl -xattr -no-fsync . /destdir/.)&

and ACL's  from one XFS file system to another, so I'm reasonably sure it's 
archive format (see its manpage for correct options) would also store them.



Dave Chinner wrote:
> On Tue, May 18, 2010 at 01:50:15PM +0200, Michael Monnerie wrote:
>> Hello, I'm trying to rsync from an xfs with ACLs set to another server 
>> which has an xfs filesystem. I mounted the nfs using 
>>
>> Does it mean I can't sync ACLs? How could I do it? I need a full backup 
>> including ACLs, as I want to move all data and then restore.
> 
> NFSv3 doesn't support ACLs, IIRC.
> 
> Cheers,
> 
> Dave.

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  parent reply	other threads:[~2010-05-20 23: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
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 [this message]
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=4BF5B20F.1020400@tlinx.org \
    --to=xfs@tlinx.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 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.