rsync - Nov 2010 - DO NOT REPLY [Bug 7799] New: rsync don't full syncronise xattr

https://bugzilla.samba.org/show_bug.cgi?id=7799

           Summary: rsync don't full syncronise xattr
           Product: rsync
           Version: 2.6.8
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: core
        AssignedTo: wayned at samba.org
        ReportedBy: ivan.solomin at gmail.com
         QAContact: rsync-qa at samba.org


I try to sync netware.metadata extended attributes (described in
http://developer.novell.com/documentation/xattr/attr_enu/data/bktitle.html)
NSS store trustee information in structure zNW_trustee_s. It contains trustee
ID and trustee rights(maximum 2043 trustees).
rsync synchronise only new or changed trustees records. If i delete some
trustee record from source, rsync doesn't delete it on target location.

Also checked in rsync 3.0.5.


-- 
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.

https://bugzilla.samba.org/show_bug.cgi?id=7799


matt at mattmccutchen.net changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|rsync don't full syncronise |Deletion of NetWare
trustees
                   |xattr                       |is not propagated
            Version|2.6.8                       |3.0.5




------- Comment #1 from matt at mattmccutchen.net  2010-11-21 18:44 CST -------
Copying of NetWare metadata per se is not currently a supported feature of
rsync.  Rsync simply copies the extended attributes exposed via the getxattr
interface.  If that does not have the effect of copying the NetWare metadata,
that could be considered a flaw in the design of the netware.metadata xattr.

Alternatively, if someone can identify what rsync could do specially in order
to copy the NetWare metadata correctly, you could request it as an enhancement.
 From the documentation you linked, I get the impression that the data passed
to setxattr(netware.metadata) is not literally the entire value to be set, but
some form of request that indicates what parts of the xattr should be modified
(arguably an abuse of the setxattr interface, but perhaps the most convenient
approach).  The zMOD_ALL_TRUSTEES flag sounds like it might be what is needed,
but that's just a guess; its meaning is not documented.


-- 
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.

https://bugzilla.samba.org/show_bug.cgi?id=7799





------- Comment #2 from ivan.solomin at gmail.com  2010-11-21 22:45 CST -------
The extended attributes it not function of products Novell. Novell uses
standard interfaces for access granting to the features. I have resulted
structure of the metadata for an example that doesn't synchronize rsync. For
example, it is possible to tell on another:
Before the first synchronization we have a set from 3 expanded attributes.
Before the second synchronization we will remove 1 attribute from an initial
file, and after synchronization we will receive on target again 3 expanded
attributes. I consider that error to be in the logician of algorithm of
synchronization xattr rsync. I will try to understand algorithm if I will
receive result I will place it here.


-- 
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.

https://bugzilla.samba.org/show_bug.cgi?id=7799





------- Comment #3 from matt at mattmccutchen.net  2010-11-21 23:12 CST -------
(In reply to comment #2)
> The extended attributes it not function of products Novell. Novell uses
> standard interfaces for access granting to the features. I have resulted
> structure of the metadata for an example that doesn't synchronize
rsync.
Sorry, I don't understand what you are saying here.
> For
> example, it is possible to tell on another:
> Before the first synchronization we have a set from 3 expanded attributes.
> Before the second synchronization we will remove 1 attribute from an
initial
> file, and after synchronization we will receive on target again 3 expanded
> attributes. I consider that error to be in the logician of algorithm of
> synchronization xattr rsync.
There may be an rsync bug, or it may be that rsync is making the correct system
calls but the NetWare implementation gives an unexpected result.  We would need
a system call trace (strace on Linux, I don't know the NetWare equivalent)
to
find out.


-- 
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.

https://bugzilla.samba.org/show_bug.cgi?id=7799





------- Comment #4 from ivan.solomin at gmail.com  2010-11-22 00:06 CST -------
I use rsync on SUSE Linux Enterprise server with NSS file system(not on
NetWare). If I start strace with rsync at synchronization it will help?


-- 
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.

https://bugzilla.samba.org/show_bug.cgi?id=7799





------- Comment #5 from matt at mattmccutchen.net  2010-11-22 08:30 CST -------
(In reply to comment #4)
> If I start strace with rsync at synchronization it will help?
Yes.  Please do it for the simplest case you can find in which the outcome is
incorrect and attach the output to this bug.  If the run is remote, be sure to
run strace on both sides (see http://rsync.samba.org/issues.html for how to do
that).


-- 
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.

https://bugzilla.samba.org/show_bug.cgi?id=7799





------- Comment #6 from ivan.solomin at gmail.com  2010-11-23 03:36 CST -------
Created an attachment (id=6080)
 --> (https://bugzilla.samba.org/attachment.cgi?id=6080&action=view)
First synchronization - 1 trustee are been processed


-- 
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.

https://bugzilla.samba.org/show_bug.cgi?id=7799





------- Comment #7 from ivan.solomin at gmail.com  2010-11-23 03:38 CST -------
Created an attachment (id=6081)
 --> (https://bugzilla.samba.org/attachment.cgi?id=6081&action=view)
Second synchronization

I delete 1 trustee from source. On target file trustee are not deleted.


-- 
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.