#4
|
||||
|
||||
Mat,
You didn't give me much information here -- but I never said this was a "hardware" problem. I said you should repair the source drive. (And I know what a malloc error is, really.) What's going on is that a structure in the file system has a bad/damaged size or invalid structure, typically in its extended attributes (which includes ACLs), and the OS X calls we're using to copy the data are getting confused by that and doing something wrong. The actual failure is pretty deep in the file system copy calls. Are you running with 10.4.11 server? If so, there are a number of bugs in ACL handling in 10.4.11 that can cause this problem (Apple fixed these issues in Leopard, although in some situations they can still happen, hence the repair request). But, try turning off the ACL copying checkbox in the Advanced tab of Options.
__________________
--Dave Nanian |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Time Machine stopped working - SuperDuper involved? | adriansmith | General | 18 | 02-20-2008 03:48 PM |
Errors when attempting to clone drive | russb | General | 2 | 09-01-2007 07:46 AM |
error code=3 ACL issue | vudutu | General | 9 | 12-13-2006 02:32 PM |
SuperDuper Error | nvlagry | General | 3 | 10-09-2006 07:22 PM |
Panther to Tiger with a bootable Lacie external | dombort | General | 20 | 07-25-2005 02:06 PM |