View Single Post
  #1  
Old 05-18-2005, 10:18 AM
camner camner is offline
Registered User
 
Join Date: Apr 2004
Posts: 152
error with SC aborting

Here's the final few entries of the console log after SD! aborted during a safety clone operation:

Code:
|11:06:35 PM|Info|       Ignoring /private/var/vm
|11:23:22 PM|Error| SVUclone: Error: Couldn't create
|11:23:22 PM|Error| : Result too large
|11:23:22 PM|Error| SVUclone: Error copying /.hotfiles.btree to /Volumes/G4 SC/.hotfiles.btree of type 8
|11:23:22 PM|Error| : Result too large
|11:23:22 PM|Error| ****FAILED****: result=256 errno=1 (Operation not permitted)
|11:23:22 PM|Info|       Ignoring /Volumes/G4 old
|11:23:22 PM|Info|       Ignoring /Volumes/G4 SC
|11:23:22 PM|Info|       Ignoring /Volumes/G4
|11:23:22 PM|Info|       Ignoring /mach
|11:23:22 PM|Info|       Ignoring /mach.sym
|11:23:22 PM|Info|       Ignoring /Desktop DF
|11:23:22 PM|Info|       Ignoring /Desktop DB
|11:23:22 PM|Info|       WARNING:  Caught I/O exception(16): Resource busy
|11:23:22 PM|Info|       WARNING:  Source: /.hotfiles.btree, lstat(): 0
|11:23:22 PM|Info|       WARNING:  Target: /Volumes/G4 SC/.hotfiles.btree, lstat(): 0
|11:23:22 PM|Info|       Logging attributes for item: /.hotfiles.btree of type: 8
|11:23:22 PM|Info|       Error copying /.hotfiles.btree to /Volumes/G4 SC/.hotfiles.btree of type 8
Right after the abort, the target disk had over 6GB space left (of 15 GB allocated), and I had started with a "safe boot".

Is this a space problem, or something else?

Thank you.
Reply With Quote