similar to: DO NOT REPLY [Bug 6276] crtimes.patch does not preserve creation dates on Mac x86_64 only

https://bugzilla.samba.org/show_bug.cgi?id=6276 Summary: crtimes.patch does not preserve creation dates on Mac x86_64 only Product: rsync Version: 3.0.6 Platform: x86 OS/Version: Mac OS X Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org

I noticed that this topic appeared from time to time on the mailing list and that one patch exists (copy-devices.diff) from a previous thread which allowed rsync to operate with a source device file. The patch below, when combined with the 'copy-devices' patch, allows rsync to be operate between two device files. In our environment this is being used, along with LVM snapshots, to

Working with rsync 3.0.2, it appears that rsync isn't unlocking files before setting the file attributes when those files already exist. This generates error messages on subsequent such as: rsync: rsync_xal_set: lsetxattr("locked_file","test_xattr") failed: Operation not permitted (1) rsync: rsync_xal_clear:

https://bugzilla.samba.org/show_bug.cgi?id=5565 Summary: xattrs not set on locked files that already exist on target Product: rsync Version: 3.0.3 Platform: Other OS/Version: Mac OS X Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org

On a PPC machine running Mac OS X, I noticed that creation time is not preserved for files that are transferred (i.e. versus files that are not transferred, or files that have only attribute changes). I discovered two things that work together to cause this: 1) cmp_time (util.c) doesn't check for negative values provided in file1 or file2. If file2 is positive, and file1 is

I've been getting spurious unnecessary copying of files on OSX when using the crtimes patch and the --crtimes -H options (version 3.0.4). I can reliably demonstrate it (on OSX 10.5) by doing this several times (as root): rsync -v -N -axHAX --delete-during --fileflags --force-change /usr/ bin/ /tmp/foo/ I think I've tracked it down to the hard-link processing code in

Hi, first of all, sorry for taking so long. Unfortunately, some other tasks kept coming up. Anyway, attached is the version of the flags patch, that is based on the one I'm using with 2.6.9. It is against the rsync-3.0.0pre9 release. I've included the option name change from the repository, so the option is now called --fileflags. Improved from the previously distributed version is the

Similar to --omit-{dir,link}-times: --omit-device-times omit device files from --times --omit-special-times omit sockets and fifos from --times Also, fix corner case that allows --omit-dir-times to be ignored. See unchanged_attrs() and recv_generator()'s call to try_dests_non(). Marc. diff -aNpRruz -X /etc/diff.excludes rsync-3.2.7/generator.c devel-3.2.7/generator.c ---

https://bugzilla.samba.org/show_bug.cgi?id=13522 Bug ID: 13522 Summary: Patch fileflags.diff and crtimes.diff Product: rsync Version: 3.1.3 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: core Assignee: wayned at samba.org Reporter:

Why is do_mkstemp fchmod-ing the temporary file? I was not able to figure this out from the CVS logs or my searches in the mail archives. Currently, do_mkstemp does this (*): mkstemp temporary file (which leaves it with 0600) fchmod temporary file (final perm & 0700) And then later it gets renamed to the final name and permissions set to what they are supposed to be. (*)

Hiya, I can see it's a regular subject on this list. I, like others wanted to use rsync to synchronise two block devices (as it happens one lvm volume and one nbd device served by qemu-img on a remote host from a qcow2 disk image so that I can keep the old versions) As I couldn't find any report of it being done successfully, I'm just sharing my findings as it might benefit others.

I noticed that rsync itemizes "p" whenever it copies a new file and finds an alternate basis file whose permissions differ from those to be applied to the destination file, even when --perms and --executability are both off. To see this, run the following in an empty directory: mkdir src dest basis touch src/file basis/file chmod 600 src/file chmod 644 basis/file rsync -r -ii

Hi all, I recently ran into some problems with rsync. My plan is to renew some of our old administration concepts from early 90's, I already replaced rdist with rsync a few years ago. Because of the rdist legacy, the current method requires synchronizing files into 6 different locations, {/alt,/usr/alt}/{hostdep,sysdep,hutdep}, which in turn are prioritized by a tool that just symlinks

Hi List, I had a need recently to efficiently synchronise between some large LUNs (boot drive disks) at two different datacentres. Solutions like drbd and $proprietary_array_vendors_software were overkill - we only needed (wanted!) to periodically synchronise these LUNs whenever major changes were generated on the source. On the other hand however, re-sending the entire disk contents each time

Hi, I am using smbtorture test suites to run several raw tests on the samba share on my gluster volume. I see following errors : smbtorture -U user%passwd //server/torture-vol raw.sfileinfo smbtorture 4.1.13 Using seed 1415694107 time: 2014-11-11 03:21:47.380755 progress: 6 test: base time: 2014-11-11 03:21:47.381135 Failed to setup EAs create_time not setup correctly Failed to setup EAs

Hi All, I promise I won't bug you anymore about this but I did find that the compiled universal binary on rsync3.0.pre10 does preserve creation dates across platforms with the old osx-create-time.diff patch but not with the crtimes patch. If anyone has a clue about this I would be happy to fix it. Thanks again Rob D PS so close!

Hi, HPUX and some AIX releases have a bug in their implementation of mkstemp(). They do not open the resulting file with O_LARGEFILE. Copying a >2GB file files fails therefore. IRIX, Linux seems to be o.k. There is an efix for AIX available but seems not to be deployed everywhere. Cheers Olaf *** rsync-2.6.2/syscall.c.ORG_SC Fri Aug 13 13:17:27 2004 --- rsync-2.6.2/syscall.c

https://bugzilla.samba.org/show_bug.cgi?id=7685 Summary: rsync should not set the creation data on the root folder of an HFS+ volume Product: rsync Version: 3.0.7 Platform: x86 OS/Version: Mac OS X Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned at

Hi all I ran a workload that reads & writes within 10 files each file is 256M, ie, (10 * 256M = 2.5GB total Dataset Size). I have set the ARC max size to 1 GB on etc/system file In the worse case, let us assume that the whole dataset is hot, meaning my workingset size= 2.5GB My SSD flash size = 8GB and being used for L2ARC No slog is used in the pool My File system record size = 8K ,

https://bugzilla.samba.org/show_bug.cgi?id=5027 Summary: Perms in do_mkstemp are not always valid Product: rsync Version: 2.6.9 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: cmadams@hiwaay.net