On Mar 9, 2011, at 10:38 PM, Chris Murphy wrote:

> We'd have serious problems if that were not the case.

We do. As I've pointed out Finder can't even see whole sets of files. 

>>> And an even larger sample size exists if filesystems other than jhfs+ are 
>>> considered. RAID 5/6 are common with ext3, ext4, XFS and other file systems 
>>> without anyone suggesting RAID 5 in particular is known for itself 
>>> increasing the incidence of silent data corruption.
>> 
>> Sorry to be blunt: What rock have you been under?
> 
> You are conflating a higher incidence of silent data corruption with a known 
> deficiency with RAID 5/6. They are not the same thing. Feel free to repeat 
> yourself, though.

No let me repeat: silent data corruption only occurs under raid5

>>> CCC is not rocket science. I have a new version, it does not produce 
>>> identical copies of all files in all cases. 
>> 
>> Since Backup Bouncer demonstrates it does, to what are you referring?
> 
> hfsdebug indicates the original and cloned/copied files are not the same. 
> With Time Machine restores, they are.
>> 

Since I must not be following you since I don't see this empirically please 
provide and example. 


>>> While the cloned system was perfectly functional, at a file system level 
>>> they were not *identical* to the original, which is a very specific meaning.
>> 
>> Again, in what way?
> 
> Data stored in attributes was restored into the data fork. Storage 
> requirement for files doubled to quadrupled. That is not identical to the 
> original.

Then you used the tool differently. 

>>> Disk Utility is using asr. It does *not* restore or copy files identically 
>>> to the original.
>> 
>> No, disk utility and asr are quite different but perform a similar operation 
>> using different code and operations. Watch a sc_usage or dtrace of each and 
>> you'll see they're operating quite differently. 
> 
> I have watched Disk Utility while doing disk to disk copies and the only 
> process it spawned was asr. Only asr was producing file system usage to the 
> target drive.

This is not accurate across all OS X versions of the tool. 

-d

------------------------------------------------------------------------
Dan Shoop
[email protected]
GoogleVoice: 1-646-402-5293
aim: iWiring
twitter: @colonelmode



_______________________________________________
MacOSX-admin mailing list
[email protected]
http://www.omnigroup.com/mailman/listinfo/macosx-admin

Reply via email to