Re: ANN: Backup Bouncer -- a metadata test suite
Re: ANN: Backup Bouncer -- a metadata test suite
- Subject: Re: ANN: Backup Bouncer -- a metadata test suite
- From: email@hidden
- Date: Thu, 3 May 2007 18:43:15 +0200
I like your BB and used it to verify the esbdump/esbrestore commands
included in ES-Backup...
Some notes, IMHO:
- I doubt it is sensefull testing the "busy" Finder flag on
directories to be backed up and failing this test if not. Even if a
directory is busy on the source, this flag should not be copied over
to the destination, since this is something the Finder should
set/unset.
- Another issue is the Finder "lock" flag and the "uchg" BSD flag on
files and directories: Setting them in the destination might result
in not being able to modify this file/directory during the next
(incremental) restore, rsync, copy, etc. When carrying out a UNIX cp
this seems to be an expected behaviour, but e.g. when doing
synchronizations or incremental restores, it depends on what the user
expects as the result on the destination, e.g.:
A source directory was locked and synced to the destination. Before
the next sync takes place I unlock the source directory and copy
files to it and afterwards lock it again. Should I expect to have the
new files in the locked destination directory after the next sync was
carried out? So not copying the "lock" flag might or might not be a
reason to fail this test.
Uwe
At 18:30 Uhr -0700 01.05.2007, Nathaniel Gray wrote:
Hi folks,
I'm pleased to announce the first release of Backup Bouncer, a tool
to keep the ugly backup tools out of the club. To be more precise,
BB is a tool for systematically testing backup tools in OS X, with a
focus on ensuring proper preservation of file-related metadata. It
contains a suite of tests to verify that metadata has survived a
copy operation, along with a suite of copiers. It will even
automatically prepare disk images as source/destination targets for
you.
How is this relevant to darwin-dev? Well, the results of the
various copy/archival tools in Tiger leave much to be desired. Here
are the results from rsync:
------------------ rsync-apple ------------------
This copier exited with error code 24
This copier produced log output in:
/Volumes/Dst/10-rsync-apple/log
Verifying: basic-permissions ... ok
Verifying: timestamps ...
Sub-test: modification time ... ok
ok
Verifying: symlinks ... ok
Verifying: symlink-ownership ... ok
Verifying: hardlinks ... ok
Verifying: resource-forks ... FAIL
Verifying: finder-flags ... FAIL
Verifying: finder-locks ... FAIL
Verifying: creation-date ... FAIL
Verifying: bsd-flags ... FAIL
Verifying: extended-attrs ...
Sub-test: on files ... FAIL
Sub-test: on directories ... FAIL
Sub-test: on symlinks ... FAIL
FAIL
Verifying: access-control-lists ...
Sub-test: on files ... FAIL
Sub-test: on dirs ... FAIL
FAIL
Verifying: fifo ... ok
Verifying: devices ... ok
Verifying: combo-tests ...
Sub-test: xattrs + rsrc forks ... FAIL
Sub-test: lots of metadata ... FAIL
FAIL
And here are the results from tar:
------------------ tar ------------------
This copier produced log output in:
/Volumes/Dst/50-tar/log
Verifying: basic-permissions ... ok
Verifying: timestamps ...
Sub-test: modification time ... ok
ok
Verifying: symlinks ... ok
Verifying: symlink-ownership ... ok
Verifying: hardlinks ... ok
Verifying: resource-forks ... FAIL
Verifying: finder-flags ... FAIL
Verifying: finder-locks ... FAIL
Verifying: creation-date ... FAIL
Verifying: bsd-flags ... FAIL
Verifying: extended-attrs ...
Sub-test: on files ... FAIL
Sub-test: on directories ... FAIL
Sub-test: on symlinks ... FAIL
FAIL
Verifying: access-control-lists ...
Sub-test: on files ... FAIL
Sub-test: on dirs ... FAIL
FAIL
Verifying: fifo ... ok
Verifying: devices ... ok
Verifying: combo-tests ...
Sub-test: xattrs + rsrc forks ... FAIL
Sub-test: lots of metadata ... FAIL
FAIL
On a happier note, here are the results from cp -Rp:
------------------ cp-apple ------------------
Verifying: basic-permissions ... ok
Verifying: timestamps ...
Sub-test: modification time ... ok
ok
Verifying: symlinks ... ok
Verifying: symlink-ownership ... FAIL
Verifying: hardlinks ... FAIL
Verifying: resource-forks ... ok
Verifying: finder-flags ... ok
Verifying: finder-locks ... ok
Verifying: creation-date ... FAIL
Verifying: bsd-flags ... ok
Verifying: extended-attrs ...
Sub-test: on files ... ok
Sub-test: on directories ... ok
Sub-test: on symlinks ... FAIL
FAIL
Verifying: access-control-lists ...
Sub-test: on files ... ok
Sub-test: on dirs ... ok
ok
Verifying: fifo ... ok
Verifying: devices ... ok
Verifying: combo-tests ...
Sub-test: xattrs + rsrc forks ... ok
Sub-test: lots of metadata ... ok
ok
Anyhow, I know you're aware of many of these problems. I hope that
having an automated test suite can help you to find and solve them.
Find out more here:
http://www.n8gray.org/blog/2007/04/27/introducing-backup-bouncer/
Cheers,
-n8
--
-- Nathaniel Gray -- Caltech Computer Science ------>
-- Mojave Project -- http://mojave.cs.caltech.edu -->
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden