search for: get_xattr_names

...cOSX Leopard Server 10.5.1 and am doing an rsync of the whole system like this: /bin/rsync302 -axX / /Volumes/appserv02/2008-14/ --exclude=/Network --exclude=/net --exclude=/home It works OK, but returns with a failure error code, and the following errors relating to files with sockets. rsync: get_xattr_names: llistxattr("private/etc/racoon/racoon.sock",1024) failed: Operation not permitted (1) rsync: get_xattr_names: llistxattr("private/etc/racoon/vpncontrol.sock",1024) failed: Operation not permitted (1) rsync: get_xattr_names: llistxattr("private/tmp/ARD_ABJMMRT",1024)...

...39;m running the script as root with the following options (which are supposed to do the work) : -aNHAXx --fileflags --force-change --protect-decmpfs --numeric-ids The script works pretty fine except for one thing. When rsync builds the file list, I get hundred of errors such as : rsync: get_xattr_names: llistxattr("some/path/here",1024) failed: No such file or directory (2) Please notice that these errors don't appear if I'm not using the --link-dest option or if the linked-dest-directory doesn't exist (first backup). Also, "some/path/here" does exist on both side...

Somebody knows if it's possible to compile rsync (version 3 would be great, but can be 2.6.x) under Mac OS X 10.3.9 with extended attributes? Under OS 10.3.9 the Apple shipped rsync have not yet the -E argument option. RsyncX have a double free bug that is annoying. "Q" rsync 2.6.6 with extended attributes binary only works on 10.4 and above. I have tried to compile rsync

...ing and running "bbouncer" from <http://www.n8gray.org/blog/2007/04/27/introducing-backup-bouncer/> ./bbouncer create-vol mysource ./bbouncer create-vol mybackup sudo rm -rf /Volumes/mybackup/* rsync -aHAX --fileflags /Volumes/mysource/ /Volumes/mybackup/ reports --- rsync: get_xattr_names: llistxattr("90-fifo/some-fifo",1024) failed: Operation not permitted (1) rsync: get_xattr_names: llistxattr("95-devices/devvn0",1024) failed: Operation not permitted (1) rsync: get_xattr_names: llistxattr("95-devices/devzero",1024) failed: Operation not permitted (1)...

...g or little should be copied or > transferred, so I can go home quickly. > > I am currently using 3.0.6+fileflags+crtimes, with the following > command: > sudo rsync -aNHAXx --fileflags --force-change --modify-window=1 SRC > DST > > I get errors of the type: > rsync: get_xattr_names: > llistxattr("masking/figures/._intro_err_2tissue_worst_best_add1.pdf", > 1024) > failed: Operation not permitted (1) > > These errors occur, I think, trying to access files that store xattr > on the FAT32 drive. They occur even in a trial run (-n). What is > intere...

Normally I would use the --link-dest option to do this but I can't since I'm rsyncing from a Mac to a Samba share on a Linux box and hard links don't work. What I want to do is create a 10 day rotating incremental backup. I used the first script example on the rsync examples page as a template. The only thing I changed was the destination to be a local directory and paths for

...clude-from backup_excludes.txt $* $SOURCE $DESTINATION Source: Iomega NAS sharing via NFS Destination: USB drive with HFS filesystem, directly attached When I try to run rsync on the iMac, with the NFS mount as the source and the USB mount as the destination I get errors of this form: rsync: get_xattr_names: llistxattr("Cochineal/Images/iPhoto Library/ Data/2006/Roll 56/._DSC_5186a.jpg",1024) failed: Operation not permitted (1) for every file. No ._ files are copied - is this because the destination is an HFS filesystem and therefore supports resource forks? Then what is the error?...

.../attachment.cgi?id=9350 testcase When running rsync --xattrs --link-dest with --dry-run, a warning is printed if the current directory does not match the source directory. Inspection with strace showed that the current directory is not changed when using --dry-run. An example message: rsync: get_xattr_names: llistxattr(""/tmp/test-rsync-bug/2/a/file"",1024) failed: No such file or directory (2) See attached shell script. -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bu...

...erred, and when no or few changes occur, nothing or little should be copied or transferred, so I can go home quickly. I am currently using 3.0.6+fileflags+crtimes, with the following command: sudo rsync -aNHAXx --fileflags --force-change --modify-window=1 SRC DST I get errors of the type: rsync: get_xattr_names: llistxattr("masking/figures/._intro_err_2tissue_worst_best_add1.pdf",1024) failed: Operation not permitted (1) These errors occur, I think, trying to access files that store xattr on the FAT32 drive. They occur even in a trial run (-n). What is interesting is that if I run rsync several...

...Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned at samba.org ReportedBy: stlman at poczta.fm QAContact: rsync-qa at samba.org When I run rsync -X (see below) remote rsync reports (xattrs.c:159): rsync: get_xattr_names: llistxattr("etc",1024) failed: No such file or directory (2) the command I enter to start rsync is: /usr/bin/rsync -aXn --stats --delete --iconv=iso8859-2,utf-8 --link-dest=../1 --password-file /root/rsync/rsync.backup.cred --filter='. /root/rsync/system.exclude' / backup at 10...

...(3.0.1, from macports). the script has been working fine generally for quite some time. however, recently as part of a project, i created a named pipe in a backup target dir on my laptop. when i made my weekly sanity check of the backup script's log, i discovered the following error: rsync: get_xattr_names: llistxattr("tmp/sf_daemon/fifo",1024) failed: Operation not permitted (1) rsync error: some files could not be transferred (code 23) at main.c(1497) [generator=3.0.1] in some cases (where very large numbers of files in the same target hierarchy were involved), this error also appears to...

Hello group, I have an OSX 10.3.9 Server that I'm trying to back up with rsync 3.0.2. Since I didn't have any luck with the 10.3.9 patch and I do have 10.4 clients, I decided to try running the backup over AFP (Apple's file sharing protocol). I found a way to mount the AFP volume with root permissions and rsync 3.0.2 works very nicely using this on the 10.4 clients, preserving

Hi Jason, Here's rsync10.3xattr_supportv0.6.diff. You can find fileflags.diff and crtimes.diff (that are not from me, but I strongly recommend you to install) here: http://samba.anu.edu.au/ftp/rsync/src/rsync-patches-3.0.5.tar.gz As you could see in the mail from the mail-list, this version have a bug with filenames containing slashes ("/"). They are converted to colons

I've just released rsync 3.0.0pre7, the latest pre-release version of the upcoming 3.0.0 release. This release contains fixed exclude checks for a "use chroot = no" daemon that has excludes listed in the config file. This is a partial fix for the 2nd advisory that was released recently. See the rsync security web page for the updated details and a patch for 2.6.9:

I've just released rsync 3.0.0pre7, the latest pre-release version of the upcoming 3.0.0 release. This release contains fixed exclude checks for a "use chroot = no" daemon that has excludes listed in the config file. This is a partial fix for the 2nd advisory that was released recently. See the rsync security web page for the updated details and a patch for 2.6.9: