As it happens, the two servers are bound together and it's on the primary server that the backup takes place on that the problems occur. It usually happens when transferring files from another system or when a user has been deleted and there for there is an incorrect ACL entry for the file.
I would be quite happy to turn off ACL preservation, but I will do that upgrade when it makes it into at least a beta stage as these are production servers so, if it aint broke, don't fix it. Thanks for the reply, it sounds like a solution is afoot. Regards, Michael On 9/04/2010, at 11:25 AM, henri wrote: >> I am seeing far too often this error in lbackup. >> >> "rsync: unpack_smb_acl: sys_acl_get_info(): Unknown error: 0 (0)" >> >> Some research discovers that it is due to a permissions / ACL error when >> R-Sync tries to set the permissions on the file. > > I am guessing your are backing up between two systems via the network. Please > correct me if required. > > If you do not need to preserve the ACL permissions then a simple option is to > upgrade to the latest alpha build of LBackup (please note that this link is > not permanent) : > <http://www.lucidsystems.org/download/utilities/LBackup_v0.9.8r4-alpha6.dmg> > > This alpha release (will be part of the next beta release) and includes an > option to disable ACL preservation on Darwin systems via the configuration > file. > > Once you have updated you may add the following quoted lines to your > configuration file to disable the ACL preservation : > >> # Disable ACL preservation, only availible on darwin with custom rsync >> (YES/NO) >> disable_acl_preservation="YES" # (If enabled ACL's will not be preserved in >> the backup) > > Another possibility is to bind the machine performing the backups with the > same directory as the systems which are being backed up. > > I have posted a message to the rsync mailing list regarding the reporting of > files : <http://www.mail-archive.com/rs...@lists.samba.org/msg25658.html> > >> The problem is finding the offending file. I was wondering if this error >> could be rectified altogether, or at the very least, could LBackup log the >> offending file/s so I don't have to go searching for a needle in a hay >> stack. It happened to me recently on a server and I couldn't find the files >> causing the issue, so I ended up spending 3 or 4 hours redoing the >> permissions and then watching lbakcup do a full backup of the system to make >> sure it works. > > If you want to be able to track down the errors more quickly in the future > then I am hopeful that someone on the rsync mailing list will be able to > assist. I will let you know what as soon as there is a responses from the > rsync mailing list. > > If anyone has any suggestions regarding the ACL issue then please let me > know. Input with regards comments or possible solutions are certainly welcome. > > Thank you for your message. I will post back to this list once I have more > information. > > ---------------------------------- > This email is protected by LBackup > http://www.lbackup.org > > > _______________________________________________ > lbackup-discussion mailing list > http://www.lbackup.org > > Change options or unsubscribe : > http://lbackup.org/mailing_lists > _______________________________________________ lbackup-discussion mailing list http://www.lbackup.org Change options or unsubscribe : http://lbackup.org/mailing_lists
