rsync - Apr 2010 - Mac OS X "rsync: unpack_smb_acl: sys_acl_get_info(): Unknown error: 0 (0)"

I am a developer on the LBackup project.

An LBackup user recently posted a question to the mailing list asking about the
following error.
> "rsync: unpack_smb_acl: sys_acl_get_info(): Unknown error: 0 (0)"
Link to thread : <http://www.mail-archive.com/lbackup-discussion at
lists.connect.homeunix.com/msg00040.html>

My understanding of this error is that when copying files via the network from a
source system to the local system there is no local user matching the source
user.

Is it possible to place a feature request to have the error reported by rsync
also list the path to the problematic file / directory.

I may be misunderstanding the error. Any confirmation on my understanding would
also be helpful.

Thank you.

----------------------------------
This email is protected by LBackup
http://www.lbackup.org

> Link to thread : <http://www.mail-archive.com/lbackup-discussion at
lists.connect.homeunix.com/msg00040.html>
Looks like the mailing list (maybe just the mail-archive) broke the link. 

Please find a link below that should work : 
http://tinyurl.com/lbackup-post-2010-April-10th

----------------------------------
This email is protected by LBackup
http://www.lbackup.org

I have further information regarding the version and the way rsync on these
systems was compiled. Installation and compilation was performed by using the
following instructions : <http://www.bombich.com/mactips/rsync.html>

I have reproduced this issue (no file path reported) with rsync 3.0.7.

Please note that these compilation instructions include two rsync patches being
applied :
  - fileflags
  - crtimes

However, I have reproduced this issue (no file path reported) with rsync 3.0.7
even when the patches are not applied.

If you do not pass rsync the "-A" flag then this problem is not
reported because it is not attempting to preserve ACLs.

If further information is required about this issue is required then please let
me know.

Any ideas, suggestions or assistance would be most welcomed. Is this (no file
path reported) a bug within rsync?



----------------------------------
This email is protected by LBackup
http://www.lbackup.org

Description of problem : 
------------------------

On a Mac OS X system when rsync attempts to preserve ACL's for a user who is
not on the system for a file system object, there is no report of which
directories/file(s) were unable to have the ACL's preserved.


Procedure to reproduce the problem :
------------------------------------

The procedure listed below should allow you to reproduce the problem on a Mac OS
X system with ACL support :

  (1) compile a version of rsync using the instructions at the URL below : 
      <http://www.lbackup.org/developer/rsync_hfs>
  (2) create a temporary user on your system called "test"
  (3) # mkdir /tmp/testing_rsync_acl_error_reporting
  (4) # cd /tmp/testing_rsync_acl_error_reporting
  (5) # touch file
  (6) # chmod +a "test allow write" file
  (7) remove the user called "test" created earlier from your system
  (8) # /path/to/rsync --acls file file_copy

You should see the following output quoted output provided you are running rsync
3.0.7 :
> rsync: unpack_smb_acl: sys_acl_get_info(): Unknown error: 0 (0)
> rsync error: some files/attrs were not transferred (see previous errors)
(code 23) at main.c(1042) [sender=3.0.7]

What happens next :
-------------------

If any one is aware of an approach to configure rsync to report the files it has
problems with preserving ACL information for, then please let me know.

If you believe that this is an rsync bug and are able to verify this then let me
know and I will happily log a bug.


Thank you to rsync developers and contributors :
------------------------------------------------

Regardless of this potential bug, rsync is doing a great job of preserving Mac
OS X meta-data. Although, I have seen other situations related to the link-dest
option where rsync fails to preserve Mac OS X meta-data. Overall, rsync is doing
a great job! I wish to thank everyone who has been involved with making this
possible. Thank you!

I have also noticed this error. In my particular scenario ACL preservation is
not essential, but what concerns me is that rsync appears to skip an entire
folder that has an invalid ACL. Therefore none of the actual data is backed up.
I would expect rsync to copy the folder structure & files but simply leave
(or copy what it thinks to be the invalid) ACL entries behind.

Oversimplifying things, or a bug?

Regards

Stuart



On 9 Apr 2010, at 00:12, Henri Shustak wrote:
> I am a developer on the LBackup project.
> 
> An LBackup user recently posted a question to the mailing list asking about
the following error.
> 
>> "rsync: unpack_smb_acl: sys_acl_get_info(): Unknown error: 0
(0)"
> 
> Link to thread : <http://www.mail-archive.com/lbackup-discussion at
lists.connect.homeunix.com/msg00040.html>
> 
> My understanding of this error is that when copying files via the network
from a source system to the local system there is no local user matching the
source user.
> 
> Is it possible to place a feature request to have the error reported by
rsync also list the path to the problematic file / directory.
> 
> I may be misunderstanding the error. Any confirmation on my understanding
would also be helpful.
> 
> Thank you.
>

On Fri, 2010-04-09 at 11:12 +1200, Henri Shustak wrote:
> An LBackup user recently posted a question to the mailing list asking about
the following error.
> 
> > "rsync: unpack_smb_acl: sys_acl_get_info(): Unknown error: 0
(0)"
> Is it possible to place a feature request to have the error reported
> by rsync also list the path to the problematic file / directory.
Yes, that would be a simple and helpful change.  I bet rsync has other
error messages that should be changed to show the filename as well.  I
will most likely post a patch in my repository
( https://mattmccutchen.net/rsync/rsync.git/ ).

-- 
Matt

>> An LBackup user recently posted a question to the mailing list asking
about the following error.
>> 
>>> "rsync: unpack_smb_acl: sys_acl_get_info(): Unknown error: 0
(0)"
> 
>> Is it possible to place a feature request to have the error reported
>> by rsync also list the path to the problematic file / directory.
> 
> Yes, that would be a simple and helpful change.  I bet rsync has other
> error messages that should be changed to show the filename as well.  I
> will most likely post a patch in my repository
> ( https://mattmccutchen.net/rsync/rsync.git/ ).
Okay. Thank you very much! 

:)

----------------------------------
This email is protected by LBackup
http://www.lbackup.org