search for: crtimes

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...

...mes are obviously different. Of course, a file's crtime should never be negative, which leads me to #2. 2) set_file_attrs (rsync.c) doesn't initialize sx2.crtime (e.g. when the sxp argument is NULL). This leads to crtime values that are occasionally > 2^31, resulting in negative crtimes. The attached patch resolves these. Mike -------------- next part -------------- A non-text attachment was scrubbed... Name: crtimes_ppc.patch Type: application/octet-stream Size: 704 bytes Desc: not available Url : http://lists.samba.org/archive/rsync/attachments/20080929/27b16716/crtimes_ppc.o...

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: bugzilla.samba.org-prf at jf-luce.n...

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 AssignedT...

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 ,

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!

Wayne, I tried changing "unsigned long" to "uint32" as you suggested, but that doesn't work. The compiler adds padding to the struct to make the fields 64-bit aligned and it has the same problem. ?To convince the compiler that the timespec really should come immediately after the length, the struct can be packed with the pragma pack directive. ?I tested the following, and

Hello, I need to run rsync on a mac (OS X 10.6.5) with the --detect-renamed option available. I therefore started to compile rsync with the 3 relevant patches (in my opinion) : - fileflags.diff - crtimes.diff - detect-renamed.diff Here are my exact compile instructions : patch -p1 <patches/fileflags.diff patch -p1 <patches/crtimes.diff patch -p1 <patches/detect-renamed.diff ./prepare-source CFLAGS=-m32 CPPFLAGS=-m32 CCASFLAGS=-m32 ./configure CFLAGS=-m32 CPPFLAGS=-m32 CCASFLA...

https://bugzilla.samba.org/show_bug.cgi?id=12440 Bug ID: 12440 Summary: make "rsync -N" == "rsync --numeric-ids" ? Product: rsync Version: 3.1.2 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 Component: core Assignee: wayned at

Hi All, I just tried (on OS10.5.2) the new fileflags.diff patch patch -p1 <patches/fileflags.diff patch -p1 <patches/crtimes.diff (see result below- I fixed the rej's ) then ./configure make then tried it out but it isn't copying the creation dates now.... just wondering if I missed something .. Rob D robert-dutoits-powerbook-g4-15:rsync-3.0.0pre10 astrid$ patch -p1 <patches/crtimes.diff patching fil...

...a while to our data server (XServe) through SSH and pulls the files that need to be saved (I'm using the --link-dest option to limit the amount of files transferred, and to keep several backups). I've followed Mike Bombich's instructions to compile rsync 3.0.7 with patches (fileflags, crtimes, crtimes-64bit, crtimes-hfs+ and hfs_compression) on both machines. I'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 rs...

...onfirm that following all the various bits of advice yields a clean running rsync (as tested by backup bouncer). I am running MacOS X 10.4.11 on PPC. The following is a synopsis of my installation procedure (as gathered from the various emails in the archive) - note that I had trouble with crtimes.diff and went back to osx-create-time.diff. Please let me know if I have included anything spurious or missed something critical (though I am pleased that everything worked)... I downloaded the source (3.0.0 release) and the patches (as posted on the front page as of this morning). I then...

Hi All, I'm trying a remote backup for the first time. It is between two laptops, I installed rsync 3.0.7 on both compiled patch -p1 <patches/fileflags.diff patch -p1 <patches/crtimes.diff patch -p1 <patches/crtimes-64bit.diff patch -p1 <patches/crtimes-hfs+.dif f patch -p1 <patches/hfs_compression.diff ./configure make this all works perfectly for local backups, clones etc. Everything gets copied as is to the volume. I have tried without ssh keys, with keys, key...

...mp/HLTarget.dmg ############## This is yet another filesystem-specific patch, I doubt you would want to commit this in its current form. Ultimately I think we need a separate object within rsync that we can query for filesystem-specific behavior like this. This patch (from rsync 3.0.7+fileflags+crtimes) resolves the matter: ############## crtimes-hfs+.patch This patch prevents rsync from changing the creation date on the root of a volume. On HFS+, the root inode is always 2, as defined in hfs/hfs_format.h: kHFSRootFolderID = 2, /* Folder ID of the root folder */ So before cal...

...t I gave a look inside the patches Mr. Bombich suggested and I thought I could try first by using only the normal ones provided by rsync.samba.org, so I skipped curl -o patches/hfs_compression.diff http://www.bombich.com/software/opensource/rsync_3.0.7-hfs_compression_20100701.diff curl -o patches/crtimes-64bit.diff https://attachments.samba.org/attachment.cgi?id=5288 curl -o patches/crtimes-hfs+.diff https://attachments.samba.org/attachment.cgi?id=5966 and I used only patch -p1 <patches/fileflags.diff patch -p1 <patches/crtimes.diff plus the stock one instead of the custom one: patch -p1...

https://bugzilla.samba.org/show_bug.cgi?id=9103 Summary: ext4 creation timestamp Product: rsync Version: 3.1.0 Platform: x64 OS/Version: Linux Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: enda_k2 at yahoo.com QAContact:

From: Anand <anand.jain@oracle.com> This patch adds creation-time to the snapshot list display, which would help user to better manage the snapshots when number of snapshots grow substantially. This patch is developed and on top of the send/receive btrfs and btrfs-progs repo at git://github.com/ablock84/linux-btrfs.git (send-v2) git://github.com/ablock84/btrfs-progs.git (send-v2)

After a crash, in my zpool tree, some dataset report this we i do a ls -la: brwxrwxrwx 2 777 root 0, 0 Oct 18 2009 mail-cts also if i set zfs set mountpoint=legacy dataset and then i mount the dataset to other location before the directory tree was only : dataset - vdisk.raw The file was a backing device of a Xen VM, but i cannot access the directory structure of this dataset. However i

...his is how I built rsync: #!/bin/bash # VERSION=3.0.2 VERSION=3.0.3pre2 DIR="rsync-$VERSION" PATCH="rsync-patches-$VERSION" sudo rm -rf $DIR tar xvzf $DIR.tar.gz tar xvzf $PATCH.tar.gz cd $DIR patch -p1 < patches/fileflags.diff patch -p1 < patches/crtimes.diff ./prepare_source patch -p1 < patches/backup-dir-dels.diff ./configure make sudo make test cd .. This is how I run rsync: sudo /Users/ar/work/rsync/rsync-3.0.3pre2/rsync \ -vvv --stats --progress -aHAX --fileflags --force-change --crtimes \ --exclude .Trash \ /...

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