Comments on: Introducing Backup-Bouncer http://www.n8gray.org/blog/2007/04/27/introducing-backup-bouncer/ distraction in action Fri, 08 Oct 2010 05:30:24 -0700 http://wordpress.org/?v=2.8.6 hourly 1 By: blue http://www.n8gray.org/blog/2007/04/27/introducing-backup-bouncer/comment-page-2/#comment-35991 blue Wed, 08 Sep 2010 11:06:07 +0000 http://www.n8gray.org/blog/2007/04/27/introducing-backup-bouncer/#comment-35991 Mike does great work. I asked him the question and he looked into it and posted the answer very quickly. Saved a lot of bother for us. Thanks Mike. Mike does great work. I asked him the question and he looked into it and posted the answer very quickly. Saved a lot of bother for us. Thanks Mike.

]]> By: JS http://www.n8gray.org/blog/2007/04/27/introducing-backup-bouncer/comment-page-2/#comment-35989 JS Wed, 08 Sep 2010 10:46:08 +0000 http://www.n8gray.org/blog/2007/04/27/introducing-backup-bouncer/#comment-35989 For the sake of completeness, as this was a hard-one test success, here is the script used to produce the (above) results <pre> #!/bin/bash scriptdir="`dirname $0`" cd "$scriptdir" export PATH="`pwd`/util:/Developer/Tools:$PATH:." set -x make ./bbouncer create-vol Src ./bbouncer create-vol Dst ./bbouncer create /Volumes/Src /usr/local/bin/rsync -v -aNHAX --protect-args --fileflags --force-change --rsync-path=/usr/local/bin/rsync /Volumes/Src/ /Volumes/Dst ./bbouncer verify -d /Volumes/Src /Volumes/Dst </pre> Let's hope with that settled, we can continue doing 'real work' with 'good backups' again :-) Cheers. For the sake of completeness, as this was a hard-one test success, here is the script used to produce the (above) results


#!/bin/bash
scriptdir="`dirname $0`"
cd "$scriptdir"
export PATH="`pwd`/util:/Developer/Tools:$PATH:."
set -x

make
./bbouncer create-vol Src
./bbouncer create-vol Dst
./bbouncer create /Volumes/Src
/usr/local/bin/rsync -v -aNHAX --protect-args --fileflags --force-change --rsync-path=/usr/local/bin/rsync  /Volumes/Src/ /Volumes/Dst
./bbouncer verify -d /Volumes/Src /Volumes/Dst

Let’s hope with that settled, we can continue doing ‘real work’ with ‘good backups’ again :-)

Cheers.

]]> By: JS http://www.n8gray.org/blog/2007/04/27/introducing-backup-bouncer/comment-page-2/#comment-35988 JS Wed, 08 Sep 2010 10:38:56 +0000 http://www.n8gray.org/blog/2007/04/27/introducing-backup-bouncer/#comment-35988 Thanks for the tip-off Blue - my Mike was quick, as even late (my time) yesterday he hadn't made that update - cool! Oh, and yes, I have tested the new recipe, here are all the gory details: <pre> cd util && make make[1]: Nothing to be done for `all'. created: /Users/test/100908/backup-bouncer-0.2.0/Src.sparseimage /dev/disk3 GUID_partition_scheme /dev/disk3s1 Apple_HFS /Volumes/Src created: /Users/test/100908/backup-bouncer-0.2.0/Dst.sparseimage /dev/disk4 GUID_partition_scheme /dev/disk4s1 Apple_HFS /Volumes/Dst Cleaning: 00-basic-permissions Cleaning: 05-timestamps Cleaning: 10-symlinks Cleaning: 15-symlink-ownership Cleaning: 20-hardlinks Cleaning: 30-resource-forks Cleaning: 40-finder-flags Cleaning: 45-finder-locks Cleaning: 50-creation-date Cleaning: 60-bsd-flags Cleaning: 70-extended-attrs Cleaning: 80-access-control-lists Cleaning: 95-devices Cleaning: 99-combo-tests Creating: 00-basic-permissions ... ok Creating: 05-timestamps ... ok Creating: 10-symlinks ... ok Creating: 15-symlink-ownership ... ok Creating: 20-hardlinks ... ok Creating: 30-resource-forks ... ok Creating: 40-finder-flags ... ok Creating: 45-finder-locks ... ok Creating: 50-creation-date ... ok Creating: 60-bsd-flags ... ok Creating: 70-extended-attrs ... ok Creating: 80-access-control-lists ... ok Creating: 95-devices ... ok Creating: 99-combo-tests ... ok sending incremental file list ./ bbouncer-vol .Trashes/ .Trashes/507/ .fseventsd/ .fseventsd/fseventsd-uuid 00-basic-permissions/ 00-basic-permissions/owned-by-me 00-basic-permissions/owned-by-root 00-basic-permissions/owned-by-www 00-basic-permissions/some-dir/ 05-timestamps/ 05-timestamps/some-hardlink 05-timestamps/some-dir/ 10-symlinks/ 10-symlinks/broken_symlink -> ./bogus_file 10-symlinks/link2broken_symlink -> ./broken_symlink 10-symlinks/some-file 10-symlinks/symlink1 -> ./some-file 10-symlinks/symlink2 -> ./some-file 10-symlinks/symlink3 -> ./symlink1 15-symlink-ownership/ 15-symlink-ownership/some-file 15-symlink-ownership/symlink1 -> ./some-file 15-symlink-ownership/symlink2 -> ./some-file 15-symlink-ownership/symlink3 -> ./symlink1 20-hardlinks/ 20-hardlinks/some-file 30-resource-forks/ 30-resource-forks/hl-rfork2 30-resource-forks/some-file 40-finder-flags/ 40-finder-flags/hidden-extension.txt 40-finder-flags/mucho-flags-dir 40-finder-flags/mucho-flags-file 40-finder-flags/system-file 40-finder-flags/type-and-creator 40-finder-flags/bundle-dir/ 40-finder-flags/bundle-dir/stuff 40-finder-flags/invisible-dir/ 45-finder-locks/ 45-finder-locks/locked-file 50-creation-date/ 50-creation-date/creation-date-test 60-bsd-flags/ 60-bsd-flags/file-with-flags 60-bsd-flags/dir-with-flags/ 70-extended-attrs/ 70-extended-attrs/symlink-with-xattrs -> ./xattr-test 70-extended-attrs/xattr-test 70-extended-attrs/dir-with-xattrs/ 80-access-control-lists/ 80-access-control-lists/acl-test 80-access-control-lists/acl-test-dir/ 95-devices/ 95-devices/devvn0 95-devices/devzero 99-combo-tests/ 99-combo-tests/many-metadata 99-combo-tests/xattr-with-rfork 05-timestamps/some-file => 05-timestamps/some-hardlink 20-hardlinks/link3 => 20-hardlinks/some-file 20-hardlinks/link2 => 20-hardlinks/some-file 20-hardlinks/link1 => 20-hardlinks/some-file 30-resource-forks/hl-rfork1 => 30-resource-forks/hl-rfork2 sent 4595 bytes received 769 bytes 10728.00 bytes/sec total size is 365 speedup is 0.07 Verifying: basic-permissions ... ok (Critical) Verifying: timestamps ... ok (Critical) Verifying: symlinks ... ok (Critical) Verifying: symlink-ownership ... ok Verifying: hardlinks ... ok (Important) Verifying: resource-forks ... Sub-test: on files ... ok (Critical) Sub-test: on hardlinked files ... ok (Important) Verifying: finder-flags ... ok (Critical) Verifying: finder-locks ... ok Verifying: creation-date ... ok Verifying: bsd-flags ... ok Verifying: extended-attrs ... Sub-test: on files ... ok (Important) Sub-test: on directories ... ok (Important) Sub-test: on symlinks ... ok Verifying: access-control-lists ... Sub-test: on files ... ok (Important) Sub-test: on dirs ... ok (Important) Verifying: devices ... ok Verifying: combo-tests ... Sub-test: xattrs + rsrc forks ... ok Sub-test: lots of metadata ... ok </pre> Success! With grateful thanks to all involved, here and Mike Bombich, appreciated. Thanks for the tip-off Blue – my Mike was quick, as even late (my time) yesterday he hadn’t made that update – cool!

Oh, and yes, I have tested the new recipe, here are all the gory details:

cd util && make
make[1]: Nothing to be done for `all'.
created: /Users/test/100908/backup-bouncer-0.2.0/Src.sparseimage
/dev/disk3          	GUID_partition_scheme
/dev/disk3s1        	Apple_HFS                      	/Volumes/Src
created: /Users/test/100908/backup-bouncer-0.2.0/Dst.sparseimage
/dev/disk4          	GUID_partition_scheme
/dev/disk4s1        	Apple_HFS                      	/Volumes/Dst
Cleaning: 00-basic-permissions
Cleaning:        05-timestamps
Cleaning:          10-symlinks
Cleaning: 15-symlink-ownership
Cleaning:         20-hardlinks
Cleaning:    30-resource-forks
Cleaning:      40-finder-flags
Cleaning:      45-finder-locks
Cleaning:     50-creation-date
Cleaning:         60-bsd-flags
Cleaning:    70-extended-attrs
Cleaning: 80-access-control-lists
Cleaning:           95-devices
Cleaning:       99-combo-tests
Creating: 00-basic-permissions ... ok
Creating:        05-timestamps ... ok
Creating:          10-symlinks ... ok
Creating: 15-symlink-ownership ... ok
Creating:         20-hardlinks ... ok
Creating:    30-resource-forks ... ok
Creating:      40-finder-flags ... ok
Creating:      45-finder-locks ... ok
Creating:     50-creation-date ... ok
Creating:         60-bsd-flags ... ok
Creating:    70-extended-attrs ... ok
Creating: 80-access-control-lists ... ok
Creating:           95-devices ... ok
Creating:       99-combo-tests ... ok
sending incremental file list
./
bbouncer-vol
.Trashes/
.Trashes/507/
.fseventsd/
.fseventsd/fseventsd-uuid
00-basic-permissions/
00-basic-permissions/owned-by-me
00-basic-permissions/owned-by-root
00-basic-permissions/owned-by-www
00-basic-permissions/some-dir/
05-timestamps/
05-timestamps/some-hardlink
05-timestamps/some-dir/
10-symlinks/
10-symlinks/broken_symlink -> ./bogus_file
10-symlinks/link2broken_symlink -> ./broken_symlink
10-symlinks/some-file
10-symlinks/symlink1 -> ./some-file
10-symlinks/symlink2 -> ./some-file
10-symlinks/symlink3 -> ./symlink1
15-symlink-ownership/
15-symlink-ownership/some-file
15-symlink-ownership/symlink1 -> ./some-file
15-symlink-ownership/symlink2 -> ./some-file
15-symlink-ownership/symlink3 -> ./symlink1
20-hardlinks/
20-hardlinks/some-file
30-resource-forks/
30-resource-forks/hl-rfork2
30-resource-forks/some-file
40-finder-flags/
40-finder-flags/hidden-extension.txt
40-finder-flags/mucho-flags-dir
40-finder-flags/mucho-flags-file
40-finder-flags/system-file
40-finder-flags/type-and-creator
40-finder-flags/bundle-dir/
40-finder-flags/bundle-dir/stuff
40-finder-flags/invisible-dir/
45-finder-locks/
45-finder-locks/locked-file
50-creation-date/
50-creation-date/creation-date-test
60-bsd-flags/
60-bsd-flags/file-with-flags
60-bsd-flags/dir-with-flags/
70-extended-attrs/
70-extended-attrs/symlink-with-xattrs -> ./xattr-test
70-extended-attrs/xattr-test
70-extended-attrs/dir-with-xattrs/
80-access-control-lists/
80-access-control-lists/acl-test
80-access-control-lists/acl-test-dir/
95-devices/
95-devices/devvn0
95-devices/devzero
99-combo-tests/
99-combo-tests/many-metadata
99-combo-tests/xattr-with-rfork
05-timestamps/some-file => 05-timestamps/some-hardlink
20-hardlinks/link3 => 20-hardlinks/some-file
20-hardlinks/link2 => 20-hardlinks/some-file
20-hardlinks/link1 => 20-hardlinks/some-file
30-resource-forks/hl-rfork1 => 30-resource-forks/hl-rfork2

sent 4595 bytes  received 769 bytes  10728.00 bytes/sec
total size is 365  speedup is 0.07

Verifying:    basic-permissions ... ok (Critical)
Verifying:           timestamps ... ok (Critical)
Verifying:             symlinks ... ok (Critical)
Verifying:    symlink-ownership ... ok
Verifying:            hardlinks ... ok (Important)
Verifying:       resource-forks ...
   Sub-test:             on files ... ok (Critical)
   Sub-test:  on hardlinked files ... ok (Important)
Verifying:         finder-flags ... ok (Critical)
Verifying:         finder-locks ... ok
Verifying:        creation-date ... ok
Verifying:            bsd-flags ... ok
Verifying:       extended-attrs ...
   Sub-test:             on files ... ok (Important)
   Sub-test:       on directories ... ok (Important)
   Sub-test:          on symlinks ... ok
Verifying: access-control-lists ...
   Sub-test:             on files ... ok (Important)
   Sub-test:              on dirs ... ok (Important)
Verifying:              devices ... ok
Verifying:          combo-tests ...
   Sub-test:  xattrs + rsrc forks ... ok
   Sub-test:     lots of metadata ... ok

Success!

With grateful thanks to all involved, here and Mike Bombich, appreciated.

]]> By: blue http://www.n8gray.org/blog/2007/04/27/introducing-backup-bouncer/comment-page-2/#comment-35984 blue Wed, 08 Sep 2010 09:22:03 +0000 http://www.n8gray.org/blog/2007/04/27/introducing-backup-bouncer/#comment-35984 Mike Bombich has confirmed the 64-bit timestamp bug and and additional patch is available to fix it - see his page re: 64bit crtimes patch and bugzilla report: http://www.bombich.com/mactips/rsync.html Mike Bombich has confirmed the 64-bit timestamp bug and and additional patch is available to fix it – see his page re: 64bit crtimes patch and bugzilla report:

http://www.bombich.com/mactips/rsync.html

]]> By: blue http://www.n8gray.org/blog/2007/04/27/introducing-backup-bouncer/comment-page-2/#comment-35974 blue Tue, 07 Sep 2010 21:16:47 +0000 http://www.n8gray.org/blog/2007/04/27/introducing-backup-bouncer/#comment-35974 No JS hasn't done anything very, very silly. Logic honing helps narrow the field of possibilities. You may have found a bug in 64bit rsync machine builds on Snow Leopard. To date the Bombich recipe has been robust. Note Mike Bombich's latest 3.0.7 rsync as on his website reports 64bit timestamps, but not bbouncer reports.... No JS hasn’t done anything very, very silly. Logic honing helps narrow the field of possibilities. You may have found a bug in 64bit rsync machine builds on Snow Leopard.

To date the Bombich recipe has been robust. Note Mike Bombich’s latest 3.0.7 rsync as on his website reports 64bit timestamps, but not bbouncer reports….

]]> By: JS http://www.n8gray.org/blog/2007/04/27/introducing-backup-bouncer/comment-page-2/#comment-35972 JS Tue, 07 Sep 2010 20:56:54 +0000 http://www.n8gray.org/blog/2007/04/27/introducing-backup-bouncer/#comment-35972 Hi Blue, thanks for taking the time and trouble to follow-up on this. Note, I'm not ruling out that I've done something very, very silly here - it's just that I'll be the last to notice if so :-) 'my' patched rsync is built to Mike Bombich's recipe here http://www.bombich.com/mactips/rsync.html So, two additional patch files (patches/fileflags.diff and patches/crtimes.diff) are applied, and they seem to work - for Mike, and most others (which is why it may stll be a silly boo-boo on my part?) Yes, you can build for 32-bit times, with everything else as-is and in my break tomorrow, I'll try and do that - and report back the results :-) cheers! Hi Blue, thanks for taking the time and trouble to follow-up on this.
Note, I’m not ruling out that I’ve done something very, very silly here – it’s just that I’ll be the last to notice if so :-)

‘my’ patched rsync is built to Mike Bombich’s recipe here http://www.bombich.com/mactips/rsync.html

So, two additional patch files (patches/fileflags.diff and patches/crtimes.diff) are applied, and they seem to work – for Mike, and most others (which is why it may stll be a silly boo-boo on my part?)

Yes, you can build for 32-bit times, with everything else as-is and in my break tomorrow, I’ll try and do that – and report back the results :-)

cheers!

]]> By: blue http://www.n8gray.org/blog/2007/04/27/introducing-backup-bouncer/comment-page-2/#comment-35971 blue Tue, 07 Sep 2010 20:48:25 +0000 http://www.n8gray.org/blog/2007/04/27/introducing-backup-bouncer/#comment-35971 Yep mine is 32-bit. The faults in the other copiers are a feature until apple fixes them or you find/write patched versions. Doing the manual tests requires running rsync-patched, since other copiers (cp, etc) don't copy creation times, perhaps for valid reasons. Yours is different is a few ways - 32vs64bit timestamps, iconv and symtimes. Presumably the timestamp is the problem. My Leopard 10.5.8 machine: <cite>rsync version 3.0.7 protocol version 30 Copyright (C) 1996-2009 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, symtimes, file-flags</cite> My Snow Leopard 10.6.4 machine: <cite>rsync version 3.0.7 protocol version 30 Copyright (C) 1996-2009 by Andrew Tridgell, Wayne Davison, and others. Web site: http://rsync.samba.org/ Capabilities: 64-bit files, 64-bit inums, 32-bit timestamps, 64-bit long ints, socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace, append, ACLs, xattrs, iconv, symtimes, file-flags</cite> Presumably one can compile for 32-bit timestamps... Yep mine is 32-bit. The faults in the other copiers are a feature until apple fixes them or you find/write patched versions. Doing the manual tests requires running rsync-patched, since other copiers (cp, etc) don’t copy creation times, perhaps for valid reasons.

Yours is different is a few ways – 32vs64bit timestamps, iconv and symtimes. Presumably the timestamp is the problem.

My Leopard 10.5.8 machine:
rsync version 3.0.7 protocol version 30
Copyright (C) 1996-2009 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, symtimes, file-flags

My Snow Leopard 10.6.4 machine:
rsync version 3.0.7 protocol version 30
Copyright (C) 1996-2009 by Andrew Tridgell, Wayne Davison, and others.
Web site: http://rsync.samba.org/
Capabilities:
64-bit files, 64-bit inums, 32-bit timestamps, 64-bit long ints,
socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace,
append, ACLs, xattrs, iconv, symtimes, file-flags

Presumably one can compile for 32-bit timestamps…

]]> By: JS http://www.n8gray.org/blog/2007/04/27/introducing-backup-bouncer/comment-page-2/#comment-35968 JS Tue, 07 Sep 2010 19:20:39 +0000 http://www.n8gray.org/blog/2007/04/27/introducing-backup-bouncer/#comment-35968 Re-post (a bit was swallowed during the ScreenSave copy-n-paste, extraneous bits snipped out):- <blockquote cite=""> $touch some-file $ SetFile -d 12/31/1999 some-file l$ cp some-file some-file2 $ x1="`GetFileInfo -d some-file`" $ x2="`GetFileInfo -d some-file2`" l$ echo "$x1" = "$x2" 12/31/1999 12:31:00 = 09/07/2010 20:12:23 </blockquote> Re-post (a bit was swallowed during the ScreenSave copy-n-paste, extraneous bits snipped out):-

$touch some-file
$ SetFile -d 12/31/1999 some-file
l$ cp some-file some-file2
$ x1=”`GetFileInfo -d some-file`”
$ x2=”`GetFileInfo -d some-file2`”
l$ echo “$x1″ = “$x2″
12/31/1999 12:31:00 = 09/07/2010 20:12:23

]]> By: JS http://www.n8gray.org/blog/2007/04/27/introducing-backup-bouncer/comment-page-2/#comment-35966 JS Tue, 07 Sep 2010 19:14:13 +0000 http://www.n8gray.org/blog/2007/04/27/introducing-backup-bouncer/#comment-35966 Yes, like this: <code> cp some-file some-file2 orac:100907 paul$ x1="`GetFileInfo -d some-file`" orac:100907 paul$ x2="`GetFileInfo -d some-file2`" orac:100907 paul$ echo "$x1" = "$x2" 12/31/1999 12:31:00 = 09/07/2010 20:12:23 </code> indeed it fails! Clear as daylight now? Yes, like this:

cp some-file some-file2
orac:100907 paul$ x1="`GetFileInfo -d some-file`"
orac:100907 paul$ x2="`GetFileInfo -d some-file2`"
orac:100907 paul$ echo "$x1" = "$x2"
12/31/1999 12:31:00 = 09/07/2010 20:12:23
 indeed it fails!

Clear as daylight now?

]]> By: n8 http://www.n8gray.org/blog/2007/04/27/introducing-backup-bouncer/comment-page-2/#comment-35964 n8 Tue, 07 Sep 2010 19:04:52 +0000 http://www.n8gray.org/blog/2007/04/27/introducing-backup-bouncer/#comment-35964 @JS: It's not a bad theory. I certainly haven't tested BB on a 64-bit OSX kernel so it's possible there are issues with that. But I still don't understand why 32/64-bit mismatch would matter while we're within the 32-bit unix epoch. We're talking about this sequence of events: <pre> touch some-file SetFile -d 12/31/1999 some-file # 32-bit operation copy some-file some-file2 # ??-bit operation x1="`GetFileInfo -d some-file`" # 32-bit x2="`GetFileInfo -d some-file2`" # 32-bit test "$x1" = "$x2" # fails </pre> Even if SetFile doesn't set the date correctly due to some 32/64-bit mismatch and GetFileInfo doesn't read it correctly, x1 should still be equal to x2 if the copier has worked properly. @JS: It’s not a bad theory. I certainly haven’t tested BB on a 64-bit OSX kernel so it’s possible there are issues with that. But I still don’t understand why 32/64-bit mismatch would matter while we’re within the 32-bit unix epoch. We’re talking about this sequence of events:

touch some-file
SetFile -d 12/31/1999 some-file  # 32-bit operation
copy some-file some-file2  # ??-bit operation
x1="`GetFileInfo -d some-file`"  # 32-bit
x2="`GetFileInfo -d some-file2`"  # 32-bit
test "$x1" = "$x2"   # fails

Even if SetFile doesn’t set the date correctly due to some 32/64-bit mismatch and GetFileInfo doesn’t read it correctly, x1 should still be equal to x2 if the copier has worked properly.

]]> By: JS http://www.n8gray.org/blog/2007/04/27/introducing-backup-bouncer/comment-page-2/#comment-35961 JS Tue, 07 Sep 2010 17:32:26 +0000 http://www.n8gray.org/blog/2007/04/27/introducing-backup-bouncer/#comment-35961 rsync - think the problem is 32-bit versus 64-bit and 'unclean 64-biit tools' on SnowLeopard. CCC's rsync: <code> rsync version 3.0.6 protocol version 30 Copyright (C) 1996-2009 by Andrew Tridgell, Wayne Davison, and others. Web site: http://rsync.samba.org/ Capabilities: 64-bit files, <strong>32-bit inums, 32-bit timestamps,</strong> 64-bit long ints, socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace, append, ACLs, xattrs, iconv, no symtimes, file-flags </code> (Note the 32-bit inums, 32-bit timestamps) my patched rsync: <code> rsync version 3.0.7 protocol version 30 Copyright (C) 1996-2009 by Andrew Tridgell, Wayne Davison, and others. Web site: http://rsync.samba.org/ Capabilities: 64-bit files, <strong>64-bit inums, 64-bit timestamps,</strong> 64-bit long ints, socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace, append, ACLs, xattrs, no iconv, symtimes, file-flags </code>(Note the 64-bit inums, 64-bit timestamps) Note these are running on a 64-bit Mac (Snow Leopard) and here is the kicker: I *think* the Apple Developer tools are 32-bit (not 64-bit) hence why my tests fail, but CCC 'works' (for the wrong reason?) Some evidence to support that assertion: <code> file /usr/bin/SetFile /usr/bin/SetFile: Mach-O universal binary with 2 architectures /usr/bin/SetFile (for architecture i386): Mach-O executable i386 /usr/bin/SetFile (for architecture ppc7400): Mach-O executable ppc file /usr/bin/GetFileInfo /usr/bin/GetFileInfo: Mach-O universal binary with 2 architectures /usr/bin/GetFileInfo (for architecture i386): Mach-O executable i386 /usr/bin/GetFileInfo (for architecture ppc7400): Mach-O executable ppc </code> (is both are 32-bit/PPC bit neither are64-bit compatible) As all of BackupBouncers creation-date tests are predicated on the Developer tools SetFile, and GetFileInfo, if they aren't fully 64-bit compliant doesn't that mean that Backup Bouncer is (currently) only suitable for 32-bit environments? @N8: care to comment on this theory, please? rsync – think the problem is 32-bit versus 64-bit and ‘unclean 64-biit tools’ on SnowLeopard.

CCC’s rsync:

rsync version 3.0.6 protocol version 30
Copyright (C) 1996-2009 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, no symtimes, file-flags
 (Note the 32-bit inums, 32-bit timestamps)

my patched rsync:

rsync version 3.0.7 protocol version 30
Copyright (C) 1996-2009 by Andrew Tridgell, Wayne Davison, and others.
Web site: http://rsync.samba.org/
Capabilities:
64-bit files, 64-bit inums, 64-bit timestamps, 64-bit long ints,
socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace,
append, ACLs, xattrs, no iconv, symtimes, file-flags
(Note the 64-bit inums, 64-bit timestamps)

Note these are running on a 64-bit Mac (Snow Leopard) and here is the kicker: I *think* the Apple Developer tools are 32-bit (not 64-bit) hence why my tests fail, but CCC ‘works’ (for the wrong reason?)

Some evidence to support that assertion:

file /usr/bin/SetFile
/usr/bin/SetFile: Mach-O universal binary with 2 architectures
/usr/bin/SetFile (for architecture i386): Mach-O executable i386
/usr/bin/SetFile (for architecture ppc7400): Mach-O executable ppc

file /usr/bin/GetFileInfo
/usr/bin/GetFileInfo: Mach-O universal binary with 2 architectures
/usr/bin/GetFileInfo (for architecture i386): Mach-O executable i386
/usr/bin/GetFileInfo (for architecture ppc7400): Mach-O executable ppc
(is both are 32-bit/PPC bit neither are64-bit compatible)

As all of BackupBouncers creation-date tests are predicated on the Developer tools SetFile, and GetFileInfo, if they aren’t fully 64-bit compliant doesn’t that mean that Backup Bouncer is (currently) only suitable for 32-bit environments?

@N8: care to comment on this theory, please?

]]> By: JS http://www.n8gray.org/blog/2007/04/27/introducing-backup-bouncer/comment-page-2/#comment-35959 JS Tue, 07 Sep 2010 16:00:39 +0000 http://www.n8gray.org/blog/2007/04/27/introducing-backup-bouncer/#comment-35959 @Blue: <i>Good thinking (on running CCC) - that works - I'll try and manually go through what the differences are between CCC and the patched rsync, as the patched one is supposed to work.</i> Will cover this checking when I do as Nate suggested, and try some manual manipulations with touch, SetFile, and GetFileInfo - but, rysnc isn't my main concern! So knowing CCC works, <em>how do I now get cp, tar, xar, ditto, and (the other 'built-in' utilities to behave (ie pass the creation-date test)</em> - any ideas? @Blue: Good thinking (on running CCC) – that works – I’ll try and manually go through what the differences are between CCC and the patched rsync, as the patched one is supposed to work.
Will cover this checking when I do as Nate suggested, and try some manual manipulations with touch, SetFile, and GetFileInfo – but, rysnc isn’t my main concern!

So knowing CCC works, how do I now get cp, tar, xar, ditto, and (the other ‘built-in’ utilities to behave (ie pass the creation-date test) – any ideas?

]]> By: blue http://www.n8gray.org/blog/2007/04/27/introducing-backup-bouncer/comment-page-2/#comment-35954 blue Tue, 07 Sep 2010 12:06:17 +0000 http://www.n8gray.org/blog/2007/04/27/introducing-backup-bouncer/#comment-35954 See if you can copy with Carbon Copy Cloner (which uses its own rsync) and see what results it gets on a manual bbouncer test. See if you can copy with Carbon Copy Cloner (which uses its own rsync) and see what results it gets on a manual bbouncer test.

]]> By: blue http://www.n8gray.org/blog/2007/04/27/introducing-backup-bouncer/comment-page-2/#comment-35953 blue Tue, 07 Sep 2010 12:01:05 +0000 http://www.n8gray.org/blog/2007/04/27/introducing-backup-bouncer/#comment-35953 It's definitely nothing to do with the date format, as my machine is in Australia with Australian localisation of date. It’s definitely nothing to do with the date format, as my machine is in Australia with Australian localisation of date.

]]> By: JS http://www.n8gray.org/blog/2007/04/27/introducing-backup-bouncer/comment-page-2/#comment-35950 JS Tue, 07 Sep 2010 10:05:25 +0000 http://www.n8gray.org/blog/2007/04/27/introducing-backup-bouncer/#comment-35950 @N8: had a quick look - but will now do so 'properly', thanks for commenting. @Blue: Well, I don't believe the wrong rsync is being used, because the invocation is via this: <code> rsync=/usr/local/bin/rsync flags="-v -aNHAX --protect-args --fileflags --force-change --rsync-path=$rsync" …8< SNIP sudo $rsync $flags $1/ $2 </code> Which should pick up the patched rsync, as that is where it lives. In any case, why would ALL the tests fail the creation-date check, note ditto, cp, tar, xar, etc. all fail due to this creation-date test failing (that was why I included the entire run results :-) Tanks for the comments - will do so checking - but if anyone has a bright idea in the meantime, I' all ears (as this has me concerned). cheers. @N8: had a quick look – but will now do so ‘properly’, thanks for commenting.

@Blue: Well, I don’t believe the wrong rsync is being used, because the invocation is via this:

rsync=/usr/local/bin/rsync
flags="-v -aNHAX --protect-args --fileflags --force-change --rsync-path=$rsync"
…8< SNIP
sudo $rsync $flags $1/ $2

Which should pick up the patched rsync, as that is where it lives.

In any case, why would ALL the tests fail the creation-date check, note ditto, cp, tar, xar, etc. all fail due to this creation-date test failing (that was why I included the entire run results :-)

Tanks for the comments – will do so checking – but if anyone has a bright idea in the meantime, I’ all ears (as this has me concerned).
cheers.

]]> By: blue http://www.n8gray.org/blog/2007/04/27/introducing-backup-bouncer/comment-page-2/#comment-35949 blue Tue, 07 Sep 2010 08:42:09 +0000 http://www.n8gray.org/blog/2007/04/27/introducing-backup-bouncer/#comment-35949 [Sorry the dashes got munched in formatting, forgot to use tags] <code>flags="-aNHAX --fileflags --force-change --rsync-path=$rsync"</code> [Sorry the dashes got munched in formatting, forgot to use tags]
flags="-aNHAX --fileflags --force-change --rsync-path=$rsync"

]]> By: blue http://www.n8gray.org/blog/2007/04/27/introducing-backup-bouncer/comment-page-2/#comment-35947 blue Tue, 07 Sep 2010 08:29:23 +0000 http://www.n8gray.org/blog/2007/04/27/introducing-backup-bouncer/#comment-35947 Most likely, the copier from JS is not using the right rsync. OS 10.6.4 and patched rsync 3.0.7 as per Bombich. Works fine - edited output of ./autopilot: ------------------ rsync-3-patch ------------------ Verifying: basic-permissions ... ok (Critical) Verifying: timestamps ... ok (Critical) Verifying: symlinks ... ok (Critical) Verifying: symlink-ownership ... ok Verifying: hardlinks ... ok (Important) Verifying: resource-forks ... Sub-test: on files ... ok (Critical) Sub-test: on hardlinked files ... ok (Important) Verifying: finder-flags ... ok (Critical) Verifying: finder-locks ... ok Verifying: creation-date ... ok Verifying: bsd-flags ... ok Verifying: extended-attrs ... Sub-test: on files ... ok (Important) Sub-test: on directories ... ok (Important) Sub-test: on symlinks ... ok Verifying: access-control-lists ... Sub-test: on files ... ok (Important) Sub-test: on dirs ... ok (Important) Verifying: fifo ... ok Verifying: devices ... ok Verifying: combo-tests ... Sub-test: xattrs + rsrc forks ... ok Sub-test: lots of metadata ... ok The following lines are needed to run the patched version of rsync and the right flags. See the program file residing in .../.copiers.d (I used an edited version of 10-rsync-apple and called it 11-rsync-3-patch: rsync=/usr/local/bin/rsync flags="-aNHAX --fileflags --force-change --rsync-path=$rsync" Most likely, the copier from JS is not using the right rsync.

OS 10.6.4 and patched rsync 3.0.7 as per Bombich. Works fine – edited output of ./autopilot:

—————— rsync-3-patch ——————
Verifying: basic-permissions … ok (Critical)
Verifying: timestamps … ok (Critical)
Verifying: symlinks … ok (Critical)
Verifying: symlink-ownership … ok
Verifying: hardlinks … ok (Important)
Verifying: resource-forks …
Sub-test: on files … ok (Critical)
Sub-test: on hardlinked files … ok (Important)
Verifying: finder-flags … ok (Critical)
Verifying: finder-locks … ok
Verifying: creation-date … ok
Verifying: bsd-flags … ok
Verifying: extended-attrs …
Sub-test: on files … ok (Important)
Sub-test: on directories … ok (Important)
Sub-test: on symlinks … ok
Verifying: access-control-lists …
Sub-test: on files … ok (Important)
Sub-test: on dirs … ok (Important)
Verifying: fifo … ok
Verifying: devices … ok
Verifying: combo-tests …
Sub-test: xattrs + rsrc forks … ok
Sub-test: lots of metadata … ok

The following lines are needed to run the patched version of rsync and the right flags. See the program file residing in …/.copiers.d (I used an edited version of 10-rsync-apple and called it 11-rsync-3-patch:

rsync=/usr/local/bin/rsync

flags=”-aNHAX –fileflags –force-change –rsync-path=$rsync”

]]> By: n8 http://www.n8gray.org/blog/2007/04/27/introducing-backup-bouncer/comment-page-2/#comment-35943 n8 Tue, 07 Sep 2010 06:28:55 +0000 http://www.n8gray.org/blog/2007/04/27/introducing-backup-bouncer/#comment-35943 Hmm, I don't know what could be causing that. You can look at tests.d/50-creation-date.test and see what it does. None of it should depend on your locale. I would recommend playing around with touch, SetFile, and GetFileInfo to see if you can isolate the problem. Hmm, I don’t know what could be causing that. You can look at tests.d/50-creation-date.test and see what it does. None of it should depend on your locale. I would recommend playing around with touch, SetFile, and GetFileInfo to see if you can isolate the problem.

]]> By: JS http://www.n8gray.org/blog/2007/04/27/introducing-backup-bouncer/comment-page-2/#comment-35846 JS Wed, 01 Sep 2010 09:45:40 +0000 http://www.n8gray.org/blog/2007/04/27/introducing-backup-bouncer/#comment-35846 Running OS X v10.6.4, all up-to-date updates etc., I find *nothing* (no utility) manages to pass the 'creation-date' test, including stalwarts like cp, tar, rsync (v3.0.7 Apple or patched al. la. Bombich), ditto etc. FWIW, here is an ./autopilot run result: <code> We're now going to create two disk images, create some files on one, copy them to the other, and find out what metadata was preserved. cd util && make make[1]: Nothing to be done for `all'. created: /Users/Shared/backup-bouncer-0.2.0/Src.sparseimage /dev/disk2 GUID_partition_scheme /dev/disk2s1 Apple_HFS /Volumes/Src created: /Users/Shared/backup-bouncer-0.2.0/Dst.sparseimage /dev/disk3 GUID_partition_scheme /dev/disk3s1 Apple_HFS /Volumes/Dst Cleaning: 00-basic-permissions Cleaning: 05-timestamps Cleaning: 10-symlinks Cleaning: 15-symlink-ownership Cleaning: 20-hardlinks Cleaning: 30-resource-forks Cleaning: 40-finder-flags Cleaning: 45-finder-locks Cleaning: 50-creation-date Cleaning: 60-bsd-flags Cleaning: 70-extended-attrs Cleaning: 80-access-control-lists Cleaning: 95-devices Cleaning: 99-combo-tests Creating: 00-basic-permissions ... ok Creating: 05-timestamps ... ok Creating: 10-symlinks ... ok Creating: 15-symlink-ownership ... ok Creating: 20-hardlinks ... ok Creating: 30-resource-forks ... ok Creating: 40-finder-flags ... ok Creating: 45-finder-locks ... ok Creating: 50-creation-date ... ok Creating: 60-bsd-flags ... ok Creating: 70-extended-attrs ... ok Creating: 80-access-control-lists ... ok Creating: 95-devices ... ok Creating: 99-combo-tests ... ok src = /Volumes/Src dst = /Volumes/Dst Enabling owners on src/dst disks /dev/disk2s1 on /Volumes/Src (hfs, local, journaled) /dev/disk3s1 on /Volumes/Dst (hfs, local, journaled) Cleaning......... Copying with: rsync-apple ... ok Copying with: rsync-qdolan ... Skipping: can't find needed files ok Copying with: rsync-local ... ok Copying with: cp-apple ... ok Copying with: ditto ... ok Copying with: tar ... ok Copying with: pax ... ok Copying with: xar-apple ... ok Copying with: xar-svn ... Skipping: can't find needed files ok ------------------ rsync-apple ------------------ Verifying: basic-permissions ... ok (Critical) Verifying: timestamps ... ok (Critical) Verifying: symlinks ... ok (Critical) Verifying: symlink-ownership ... ok Verifying: hardlinks ... ok (Important) Verifying: resource-forks ... Sub-test: on files ... ok (Critical) Sub-test: on hardlinked files ... FAIL (Important) Verifying: finder-flags ... ok (Critical) Verifying: finder-locks ... FAIL Verifying: creation-date ... FAIL Verifying: bsd-flags ... FAIL Verifying: extended-attrs ... Sub-test: on files ... ok (Important) Sub-test: on directories ... ok (Important) Sub-test: on symlinks ... ok Verifying: access-control-lists ... Sub-test: on files ... ok (Important) Sub-test: on dirs ... ok (Important) Verifying: devices ... ok Verifying: combo-tests ... Sub-test: xattrs + rsrc forks ... ok Sub-test: lots of metadata ... ok ------------------ rsync-qdolan ------------------ This copier was skipped ------------------ rsync-local ------------------ This copier produced log output in: /Volumes/Dst/25-rsync-local/log Verifying: basic-permissions ... ok (Critical) Verifying: timestamps ... ok (Critical) Verifying: symlinks ... ok (Critical) Verifying: symlink-ownership ... ok Verifying: hardlinks ... ok (Important) Verifying: resource-forks ... Sub-test: on files ... ok (Critical) Sub-test: on hardlinked files ... ok (Important) Verifying: finder-flags ... ok (Critical) Verifying: finder-locks ... ok Verifying: creation-date ... FAIL Verifying: bsd-flags ... ok Verifying: extended-attrs ... Sub-test: on files ... ok (Important) Sub-test: on directories ... ok (Important) Sub-test: on symlinks ... ok Verifying: access-control-lists ... Sub-test: on files ... ok (Important) Sub-test: on dirs ... ok (Important) Verifying: devices ... ok Verifying: combo-tests ... Sub-test: xattrs + rsrc forks ... ok Sub-test: lots of metadata ... ok ------------------ cp-apple ------------------ Verifying: basic-permissions ... ok (Critical) Verifying: timestamps ... ok (Critical) Verifying: symlinks ... ok (Critical) Verifying: symlink-ownership ... ok Verifying: hardlinks ... FAIL (Important) Verifying: resource-forks ... Sub-test: on files ... ok (Critical) Sub-test: on hardlinked files ... FAIL (Important) Verifying: finder-flags ... ok (Critical) Verifying: finder-locks ... ok Verifying: creation-date ... FAIL Verifying: bsd-flags ... ok Verifying: extended-attrs ... Sub-test: on files ... ok (Important) Sub-test: on directories ... ok (Important) Sub-test: on symlinks ... ok Verifying: access-control-lists ... Sub-test: on files ... ok (Important) Sub-test: on dirs ... ok (Important) Verifying: devices ... ok Verifying: combo-tests ... Sub-test: xattrs + rsrc forks ... ok Sub-test: lots of metadata ... FAIL ------------------ ditto ------------------ Verifying: basic-permissions ... ok (Critical) Verifying: timestamps ... ok (Critical) Verifying: symlinks ... ok (Critical) Verifying: symlink-ownership ... ok Verifying: hardlinks ... ok (Important) Verifying: resource-forks ... Sub-test: on files ... ok (Critical) Sub-test: on hardlinked files ... ok (Important) Verifying: finder-flags ... ok (Critical) Verifying: finder-locks ... ok Verifying: creation-date ... FAIL Verifying: bsd-flags ... ok Verifying: extended-attrs ... Sub-test: on files ... ok (Important) Sub-test: on directories ... ok (Important) Sub-test: on symlinks ... ok Verifying: access-control-lists ... Sub-test: on files ... ok (Important) Sub-test: on dirs ... ok (Important) Verifying: devices ... ok Verifying: combo-tests ... Sub-test: xattrs + rsrc forks ... ok Sub-test: lots of metadata ... ok ------------------ tar ------------------ Verifying: basic-permissions ... ok (Critical) Verifying: timestamps ... ok (Critical) Verifying: symlinks ... ok (Critical) Verifying: symlink-ownership ... ok Verifying: hardlinks ... ok (Important) Verifying: resource-forks ... Sub-test: on files ... ok (Critical) Sub-test: on hardlinked files ... ok (Important) Verifying: finder-flags ... ok (Critical) Verifying: finder-locks ... ok Verifying: creation-date ... FAIL Verifying: bsd-flags ... ok Verifying: extended-attrs ... Sub-test: on files ... ok (Important) Sub-test: on directories ... ok (Important) Sub-test: on symlinks ... ok Verifying: access-control-lists ... Sub-test: on files ... ok (Important) Sub-test: on dirs ... ok (Important) Verifying: devices ... ok Verifying: combo-tests ... Sub-test: xattrs + rsrc forks ... ok Sub-test: lots of metadata ... FAIL ------------------ pax ------------------ Verifying: basic-permissions ... ok (Critical) Verifying: timestamps ... ok (Critical) Verifying: symlinks ... ok (Critical) Verifying: symlink-ownership ... FAIL Verifying: hardlinks ... ok (Important) Verifying: resource-forks ... Sub-test: on files ... ok (Critical) Sub-test: on hardlinked files ... ok (Important) Verifying: finder-flags ... ok (Critical) Verifying: finder-locks ... FAIL Verifying: creation-date ... FAIL Verifying: bsd-flags ... FAIL Verifying: extended-attrs ... Sub-test: on files ... ok (Important) Sub-test: on directories ... ok (Important) Sub-test: on symlinks ... FAIL Verifying: access-control-lists ... Sub-test: on files ... ok (Important) Sub-test: on dirs ... ok (Important) Verifying: devices ... ok Verifying: combo-tests ... Sub-test: xattrs + rsrc forks ... ok Sub-test: lots of metadata ... ok ------------------ xar-apple ------------------ Verifying: basic-permissions ... ok (Critical) Verifying: timestamps ... ok (Critical) Verifying: symlinks ... ok (Critical) Verifying: symlink-ownership ... ok Verifying: hardlinks ... ok (Important) Verifying: resource-forks ... Sub-test: on files ... ok (Critical) Sub-test: on hardlinked files ... ok (Important) Verifying: finder-flags ... ok (Critical) Verifying: finder-locks ... ok Verifying: creation-date ... FAIL Verifying: bsd-flags ... ok Verifying: extended-attrs ... Sub-test: on files ... ok (Important) Sub-test: on directories ... ok (Important) Sub-test: on symlinks ... ok Verifying: access-control-lists ... Sub-test: on files ... ok (Important) Sub-test: on dirs ... ok (Important) Verifying: devices ... ok Verifying: combo-tests ... Sub-test: xattrs + rsrc forks ... ok Sub-test: lots of metadata ... FAIL ------------------ xar-svn ------------------ This copier was skipped </code> Running BB v0.2.0 with a test added for rsync built to Mike Bombich's instructions (al. la. http://www.bombich.com/mactips/rsync.html ) My only guess is - I'm in the UK, so times are conventionally written dd/mm/yy rather than the US-style mm/dd/yy as used by the SetFile and GetFileInfo developer tools - surely I'm not the only EC person to have noticed this problem? So I assume it's something I've done to cause it - but what? Any ideas/solutions gratefully accepted, as long as it doesn't materially affect my real data :-) Running OS X v10.6.4, all up-to-date updates etc., I find *nothing* (no utility) manages to pass the ‘creation-date’ test, including stalwarts like cp, tar, rsync (v3.0.7 Apple or patched al. la. Bombich), ditto etc.
FWIW, here is an ./autopilot run result:

We're now going to create two disk images, create some files on one,
copy them to the other, and find out what metadata was preserved.

cd util && make
make[1]: Nothing to be done for `all'.
created: /Users/Shared/backup-bouncer-0.2.0/Src.sparseimage
/dev/disk2 GUID_partition_scheme
/dev/disk2s1 Apple_HFS /Volumes/Src
created: /Users/Shared/backup-bouncer-0.2.0/Dst.sparseimage
/dev/disk3 GUID_partition_scheme
/dev/disk3s1 Apple_HFS /Volumes/Dst
Cleaning: 00-basic-permissions
Cleaning: 05-timestamps
Cleaning: 10-symlinks
Cleaning: 15-symlink-ownership
Cleaning: 20-hardlinks
Cleaning: 30-resource-forks
Cleaning: 40-finder-flags
Cleaning: 45-finder-locks
Cleaning: 50-creation-date
Cleaning: 60-bsd-flags
Cleaning: 70-extended-attrs
Cleaning: 80-access-control-lists
Cleaning: 95-devices
Cleaning: 99-combo-tests
Creating: 00-basic-permissions ... ok
Creating: 05-timestamps ... ok
Creating: 10-symlinks ... ok
Creating: 15-symlink-ownership ... ok
Creating: 20-hardlinks ... ok
Creating: 30-resource-forks ... ok
Creating: 40-finder-flags ... ok
Creating: 45-finder-locks ... ok
Creating: 50-creation-date ... ok
Creating: 60-bsd-flags ... ok
Creating: 70-extended-attrs ... ok
Creating: 80-access-control-lists ... ok
Creating: 95-devices ... ok
Creating: 99-combo-tests ... ok
src = /Volumes/Src
dst = /Volumes/Dst
Enabling owners on src/dst disks
/dev/disk2s1 on /Volumes/Src (hfs, local, journaled)
/dev/disk3s1 on /Volumes/Dst (hfs, local, journaled)
Cleaning.........
Copying with: rsync-apple ... ok
Copying with: rsync-qdolan ... Skipping: can't find needed files
ok
Copying with: rsync-local ... ok
Copying with: cp-apple ... ok
Copying with: ditto ... ok
Copying with: tar ... ok
Copying with: pax ... ok
Copying with: xar-apple ... ok
Copying with: xar-svn ... Skipping: can't find needed files
ok

------------------ rsync-apple ------------------
Verifying: basic-permissions ... ok (Critical)
Verifying: timestamps ... ok (Critical)
Verifying: symlinks ... ok (Critical)
Verifying: symlink-ownership ... ok
Verifying: hardlinks ... ok (Important)
Verifying: resource-forks ...
Sub-test: on files ... ok (Critical)
Sub-test: on hardlinked files ... FAIL (Important)
Verifying: finder-flags ... ok (Critical)
Verifying: finder-locks ... FAIL
Verifying: creation-date ... FAIL
Verifying: bsd-flags ... FAIL
Verifying: extended-attrs ...
Sub-test: on files ... ok (Important)
Sub-test: on directories ... ok (Important)
Sub-test: on symlinks ... ok
Verifying: access-control-lists ...
Sub-test: on files ... ok (Important)
Sub-test: on dirs ... ok (Important)
Verifying: devices ... ok
Verifying: combo-tests ...
Sub-test: xattrs + rsrc forks ... ok
Sub-test: lots of metadata ... ok

------------------ rsync-qdolan ------------------
This copier was skipped

------------------ rsync-local ------------------
This copier produced log output in:
/Volumes/Dst/25-rsync-local/log
Verifying: basic-permissions ... ok (Critical)
Verifying: timestamps ... ok (Critical)
Verifying: symlinks ... ok (Critical)
Verifying: symlink-ownership ... ok
Verifying: hardlinks ... ok (Important)
Verifying: resource-forks ...
Sub-test: on files ... ok (Critical)
Sub-test: on hardlinked files ... ok (Important)
Verifying: finder-flags ... ok (Critical)
Verifying: finder-locks ... ok
Verifying: creation-date ... FAIL
Verifying: bsd-flags ... ok
Verifying: extended-attrs ...
Sub-test: on files ... ok (Important)
Sub-test: on directories ... ok (Important)
Sub-test: on symlinks ... ok
Verifying: access-control-lists ...
Sub-test: on files ... ok (Important)
Sub-test: on dirs ... ok (Important)
Verifying: devices ... ok
Verifying: combo-tests ...
Sub-test: xattrs + rsrc forks ... ok
Sub-test: lots of metadata ... ok

------------------ cp-apple ------------------
Verifying: basic-permissions ... ok (Critical)
Verifying: timestamps ... ok (Critical)
Verifying: symlinks ... ok (Critical)
Verifying: symlink-ownership ... ok
Verifying: hardlinks ... FAIL (Important)
Verifying: resource-forks ...
Sub-test: on files ... ok (Critical)
Sub-test: on hardlinked files ... FAIL (Important)
Verifying: finder-flags ... ok (Critical)
Verifying: finder-locks ... ok
Verifying: creation-date ... FAIL
Verifying: bsd-flags ... ok
Verifying: extended-attrs ...
Sub-test: on files ... ok (Important)
Sub-test: on directories ... ok (Important)
Sub-test: on symlinks ... ok
Verifying: access-control-lists ...
Sub-test: on files ... ok (Important)
Sub-test: on dirs ... ok (Important)
Verifying: devices ... ok
Verifying: combo-tests ...
Sub-test: xattrs + rsrc forks ... ok
Sub-test: lots of metadata ... FAIL

------------------ ditto ------------------
Verifying: basic-permissions ... ok (Critical)
Verifying: timestamps ... ok (Critical)
Verifying: symlinks ... ok (Critical)
Verifying: symlink-ownership ... ok
Verifying: hardlinks ... ok (Important)
Verifying: resource-forks ...
Sub-test: on files ... ok (Critical)
Sub-test: on hardlinked files ... ok (Important)
Verifying: finder-flags ... ok (Critical)
Verifying: finder-locks ... ok
Verifying: creation-date ... FAIL
Verifying: bsd-flags ... ok
Verifying: extended-attrs ...
Sub-test: on files ... ok (Important)
Sub-test: on directories ... ok (Important)
Sub-test: on symlinks ... ok
Verifying: access-control-lists ...
Sub-test: on files ... ok (Important)
Sub-test: on dirs ... ok (Important)
Verifying: devices ... ok
Verifying: combo-tests ...
Sub-test: xattrs + rsrc forks ... ok
Sub-test: lots of metadata ... ok

------------------ tar ------------------
Verifying: basic-permissions ... ok (Critical)
Verifying: timestamps ... ok (Critical)
Verifying: symlinks ... ok (Critical)
Verifying: symlink-ownership ... ok
Verifying: hardlinks ... ok (Important)
Verifying: resource-forks ...
Sub-test: on files ... ok (Critical)
Sub-test: on hardlinked files ... ok (Important)
Verifying: finder-flags ... ok (Critical)
Verifying: finder-locks ... ok
Verifying: creation-date ... FAIL
Verifying: bsd-flags ... ok
Verifying: extended-attrs ...
Sub-test: on files ... ok (Important)
Sub-test: on directories ... ok (Important)
Sub-test: on symlinks ... ok
Verifying: access-control-lists ...
Sub-test: on files ... ok (Important)
Sub-test: on dirs ... ok (Important)
Verifying: devices ... ok
Verifying: combo-tests ...
Sub-test: xattrs + rsrc forks ... ok
Sub-test: lots of metadata ... FAIL

------------------ pax ------------------
Verifying: basic-permissions ... ok (Critical)
Verifying: timestamps ... ok (Critical)
Verifying: symlinks ... ok (Critical)
Verifying: symlink-ownership ... FAIL
Verifying: hardlinks ... ok (Important)
Verifying: resource-forks ...
Sub-test: on files ... ok (Critical)
Sub-test: on hardlinked files ... ok (Important)
Verifying: finder-flags ... ok (Critical)
Verifying: finder-locks ... FAIL
Verifying: creation-date ... FAIL
Verifying: bsd-flags ... FAIL
Verifying: extended-attrs ...
Sub-test: on files ... ok (Important)
Sub-test: on directories ... ok (Important)
Sub-test: on symlinks ... FAIL
Verifying: access-control-lists ...
Sub-test: on files ... ok (Important)
Sub-test: on dirs ... ok (Important)
Verifying: devices ... ok
Verifying: combo-tests ...
Sub-test: xattrs + rsrc forks ... ok
Sub-test: lots of metadata ... ok

------------------ xar-apple ------------------
Verifying: basic-permissions ... ok (Critical)
Verifying: timestamps ... ok (Critical)
Verifying: symlinks ... ok (Critical)
Verifying: symlink-ownership ... ok
Verifying: hardlinks ... ok (Important)
Verifying: resource-forks ...
Sub-test: on files ... ok (Critical)
Sub-test: on hardlinked files ... ok (Important)
Verifying: finder-flags ... ok (Critical)
Verifying: finder-locks ... ok
Verifying: creation-date ... FAIL
Verifying: bsd-flags ... ok
Verifying: extended-attrs ...
Sub-test: on files ... ok (Important)
Sub-test: on directories ... ok (Important)
Sub-test: on symlinks ... ok
Verifying: access-control-lists ...
Sub-test: on files ... ok (Important)
Sub-test: on dirs ... ok (Important)
Verifying: devices ... ok
Verifying: combo-tests ...
Sub-test: xattrs + rsrc forks ... ok
Sub-test: lots of metadata ... FAIL

------------------ xar-svn ------------------
This copier was skipped
Running BB v0.2.0 with a test added for rsync built to Mike Bombich’s instructions (al. la. http://www.bombich.com/mactips/rsync.html )

My only guess is – I’m in the UK, so times are conventionally written dd/mm/yy rather than the US-style mm/dd/yy as used by the SetFile and GetFileInfo developer tools – surely I’m not the only EC person to have noticed this problem? So I assume it’s something I’ve done to cause it – but what?

Any ideas/solutions gratefully accepted, as long as it doesn’t materially affect my real data :-)

]]> By: Empfehlenswerte Mac-Datensicherung bei Amazon S3 mit «Arq» | MacMacken http://www.n8gray.org/blog/2007/04/27/introducing-backup-bouncer/comment-page-2/#comment-35321 Empfehlenswerte Mac-Datensicherung bei Amazon S3 mit «Arq» | MacMacken Sat, 24 Jul 2010 23:04:04 +0000 http://www.n8gray.org/blog/2007/04/27/introducing-backup-bouncer/#comment-35321 [...] die Bedeutung dieser Metadaten und zeigt auf, wie «Arq»-Alternativen beim Vergleichen mittels Backup-Bouncer in dieser Hinsicht [...] [...] die Bedeutung dieser Metadaten und zeigt auf, wie «Arq»-Alternativen beim Vergleichen mittels Backup-Bouncer in dieser Hinsicht [...]

]]>