similar to: rsync stalls at .sparsebundle directories on OS X‏‏

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

Hello! I've been trying 3.0.8 on OS X 10.6.7 today and have been getting some errors. The command I'm using is: /usr/local/bin/rsync -aNHAXx --protect-args --fileflags --force-change --progress /Users/davidallie/Documents/ /Volumes/david.allie/Documents/ The target Documents folder is on an iDisk mounted as david.allie . The errors are happening at the beginning and end. BEGINNING:

I'm just starting with rsync(). I grabbed the 3.0.7 source and built it on Mac OS X.6.5 (./configure and ./make reported no problems.) When I try running with -X or -A, I get the following error messages: rsync: unpack_smb_acl: sys_acl_get_info(): Unknown error: 0 (0) rsync: unpack_smb_acl: sys_acl_get_info(): Unknown error: 0 (0) A quick look at the buglist didn't reveal anything to

On MacOS X 10.4.11 PPC /usr/local/bin/rsync --version rsync version 3.0.0pre9 protocol version 30.PR16 Copyright (C) 1996-2007 by Andrew Tridgell, Wayne Davison, and others. Web site: http://rsync.samba.org/ Capabilities: 64-bit files, 32-bit inums, 32-bit timestamps, 64-bit long ints, socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace, append, ACLs, xattrs, iconv

Hi, Since upgrading to Snow Leopard, my backup script throws an error msg : rsync: unpack_smb_acl: sys_acl_get_info(): Unknown error: 0 (0) This happened both with 3.0.5 and 3.0.6 that I just installed. Can someone tell me what it means ? I have no clue on what/where to look for. Thanks Alain Content

First of all. Thank you rsync developers and maintainers for all of your work. It is awesome. I love rsync. I can't thank you enough. So this has been brought up before: https://lists.samba.org/archive/rsync/2010-April/024941.html We are getting this error: stderr: rsync: unpack_smb_acl: sys_acl_get_info(): Undefined error: 0 (0) due to ACL entries that can not be resolved by name at

Hi: I'm in the middle of recoverying from a tactical error copying around an Mac OS X 10.10.5 Time Machine backup (turns out Apple's instructions aren't great...), and I had rsync running for the past 6 hours repairing permissions/acls on 1.5 TB of data (not copying the data), and then it just died in the middle with: .L....og.... 2015-03-11-094807/platinum-bar2/usr/local/mysql

On 2020-01-31 12:30, Johan Hattne wrote: > Dear all; > > On the recent topic of Time Machine backups: when backing up a machine > running macOS Mojave to a Samba server on Debian Buster with > buster-samba410 packages from https://apt.van-belle.nl/debian, we see > our logs filling up with messages like > > ../../source3/modules/vfs_fruit.c:7001(fruit_tmsize_do_dirent)

https://bugzilla.samba.org/show_bug.cgi?id=10649 Summary: --acls does not honor --numeric-ids on OS X Product: rsync Version: 3.1.1 Platform: x86 OS/Version: Mac OS X Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: kcrawford.rsync at

On Sun, Jan 24, 2016 at 12:29 PM, < dbonde+forum+rsync.lists.samba.org at gmail.com> wrote: > On 2016-01-24 03:51, Kevin Korb wrote: > >> Are you rsyncing from one to the other? Both of them to somewhere >> else? One at a time to somewhere else? Why won't you just show your >> actual command line and an ls -li of the correct source and incorrect >>

dbonde+forum+rsync.lists.samba.org at gmail.com wrote: > It is exactly as I wrote. On a network volume (A) a "sparse disk image bundle" (B), i.e., a type of disk image used in OS X, is stored. B is then mounted locally (i.e., local to where rsync is run) on a computer (C) where it appears as one of many volumes. > > In other words, B is stored on A. A is then mounted (using

I have been trying for the past few months to set up my raspberry pi to do incremental backups using time machine over Samba since AFP is being deprecated. Also since the latest release of samba (4.8.0) came out with support for time machine I decided to compile it myself and give it a go. The drive is formatted in HFS plus. The main problem that I am having is that even though I can mount the

https://bugzilla.samba.org/show_bug.cgi?id=7809 Summary: I/O errors other than IOERR_GENERAL should not suppress deletion Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned at samba.org

Hi All, I have had reports of problems with the -R option on OSX 10.6.4. Just tested it myself and found this odd result: When I run this "dtruss -f path/to/rsync -aHAXNR --fileflags --force-change --protect-decmpfs --stats -v /Users/astrid/Documents/main.m /Users/astrid/Desktop/rrr it produces the expected results with the relative folder paths in place

Really nice write-up on the Samba-based Open Source project ! https://arstechnica.com/gadgets/2020/07/an-easy-mode-for-zfs-we-test-the-truenas-core-12-0-beta/ Congratulations to the FreeNAS/TrueNAS folks ! Jeremy.

TL;DR: Time Machine cannot create a *new* backup on my shared drive, but can add to an *existing* backup. I'm running macOS Catalina and my Time Machine backs up to a Debian 10 server with NetAtalk and Avahi. Since Mavericks macOS has preferred SMB, and given SMB is marginally faster I decided to switch to using SMB for the Time Machine shares. On a fresh AFP share I can start a new Time

https://bugzilla.samba.org/show_bug.cgi?id=7382 Summary: Fails to copy with ACL issue if src user is unknown (OSX 10.6 only) Product: rsync Version: 3.0.7 Platform: All OS/Version: Mac OS X Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned at samba.org

Hi, tl;dr - Samba 4.8.5 broke macOS's Time Machine support (at least for me), patching in the "follow-up patch" from https://bugzilla.samba.org/show_bug.cgi?id=13441 makes it work again. It would be great if it could be included in an official patch release soon. :) Just writing about the problem and solution here, in case someone else stumbles upon it. Couldn't find any

Just chiming in here, I haven’t read all the previous posts so may be repeating… Mike Bombich has a good piece on benchmarks for various source/destination scenarios with rsync. https://bombich.com/kb/ccc3/how-long-should-clone-or-backup-take Note that copying to sparsebundle on local media is as fast as to local disk. Sparsebundle is a mac filesystem whereas NAS is not so certain file

On Mac OS X 10.5.2 I run rsync to keep a couple of instances of my / usr/local tree in sync. With Apple's rsync I run (e.g.): sudo /usr/bin/rsync --rsync-path=/usr/bin/rsync -E --progress -avu -- delete --dry-run --exclude=TeXLive-working-copy/ --exclude=context- update/ --exclude=.Spotlight-V100/ --exclude=.fseventsd/ \ -e "ssh -i /Users/gerben/.ssh/id_rsync -l root" \