Re: rsync to "apply" xattrs-only from other object?

RolandK via rsync <[email protected]> Mon, 27 Apr 2026 00:47:22 +0200
Newsgroups gmane.network.rsync.general
Message-ID <[email protected]>
This is a multi-part message in MIME format.
--===============5505481764542304172==
Content-Type: multipart/alternative;
 boundary="------------zf2FqHXKFUr0PQ7frEAYHUpT"

This is a multi-part message in MIME format.
--------------zf2FqHXKFUr0PQ7frEAYHUpT
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable

do we really need rsync for this?

root@debian:/# setfattr -n user.attr1 -v value1 ./dir/testfile
root@debian:/# getfattr -R -d ./dir/testfile >attrs.dump
root@debian:/# cat attrs.dump
# file: dir/testfile
user.attr1=3D"value1"

root@debian:/# xattr -c ./dir/testfile
root@debian:/# getfattr -R -d ./dir/testfile
root@debian:/#
root@debian:/# setfattr --restore attrs.dump
root@debian:/# getfattr -R -d ./dir/testfile
# file: dir/testfile
user.attr1=3D"value1"

regards



Am 26.04.26 um 22:34 schrieb Peter B. via rsync:
> Hi everyone :)
>
> I'd need to re-apply extended filesystem key-value metadata attributes=
=20
> (xattrs on ZFS) from one file/folder to another.
>
> But it's mandatory that the target "payload" (=3Dbinary file contents)=
=20
> stay untouched.
> Just transfer (add/merge/overwrite) the xattrs?
>
> Using xattrs professionally for medium-to-large scale heritage and=20
> science collections, and using rsync for /everything/ regarding=20
> data-transfer. Thank you all so much!
>
> Would it be possible to hire one for adding that to rsync, merging=20
> into upstream?
> What are your thoughts on this?
>
>
> Thanks in advance!
> Peter
>

--------------zf2FqHXKFUr0PQ7frEAYHUpT
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>do we really need rsync for this?<br>
      <br>
      root@debian:/# setfattr -n user.attr1 -v value1 ./dir/testfile<br>
      root@debian:/# getfattr -R -d ./dir/testfile &gt;attrs.dump<br>
      root@debian:/# cat attrs.dump<br>
      # file: dir/testfile<br>
      user.attr1="value1"<br>
      <br>
      root@debian:/# xattr -c ./dir/testfile<br>
      root@debian:/# getfattr -R -d ./dir/testfile<br>
      root@debian:/#<br>
      root@debian:/# setfattr --restore attrs.dump<br>
      root@debian:/# getfattr -R -d ./dir/testfile<br>
      # file: dir/testfile<br>
      user.attr1="value1"<br>
      <br>
      regards<br>
      <br>
      <br>
      <br>
    </p>
    <div class="moz-cite-prefix">Am 26.04.26 um 22:34 schrieb Peter B.
      via rsync:<br>
    </div>
    <blockquote type="cite"
      cite="mid:[email protected]">Hi
      everyone :)
      <br>
      <br>
      I'd need to re-apply extended filesystem key-value metadata
      attributes (xattrs on ZFS) from one file/folder to another.
      <br>
      <br>
      But it's mandatory that the target "payload" (=binary file
      contents) stay untouched.
      <br>
      Just transfer (add/merge/overwrite) the xattrs?
      <br>
      <br>
      Using xattrs professionally for medium-to-large scale heritage and
      science collections, and using rsync for /everything/ regarding
      data-transfer. Thank you all so much!
      <br>
      <br>
      Would it be possible to hire one for adding that to rsync, merging
      into upstream?
      <br>
      What are your thoughts on this?
      <br>
      <br>
      <br>
      Thanks in advance!
      <br>
      Peter
      <br>
      <br>
    </blockquote>
  </body>
</html>

--------------zf2FqHXKFUr0PQ7frEAYHUpT--


--===============5505481764542304172==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

--===============5505481764542304172==--