|
|
Thread Tools | Rate Thread | Display Modes |
|
#1
|
|||
|
|||
SD 2.1: error processing extended attributes: Cannot allocate memory
Just upgraded to 2.1. When it ran, I recieved 5,000 syslog lines of....
" /Applications/SuperDuper!.app/Contents/MacOS/SDCopy: error processing extended attributes: Cannot allocate memory" Nothing has changed in my configuration, except the upgrade to 2.1. Ideas? |
#2
|
||||
|
||||
This is a (pointless) diagnostic printed by an OSX call we're making; it's quite annoying, but we need to make the call to properly copy certain types of metadata...
__________________
--Dave Nanian |
#3
|
|||
|
|||
Thanks for the response. However, today this generated 56,000 lines in my syslog. Would it be possible to provide a link to download the previous 2.0.1 version, that did not induce these messages? Thanks.
EDIT: Found 2.0.1 at download.com Last edited by priller; 03-12-2006 at 10:21 PM. Reason: Additional Info |
#4
|
||||
|
||||
While you might have had a lot of logging during an erase-then-copy, subsequent Smart Updates will log far, far less... I'd really suggest sticking with 2.1...
__________________
--Dave Nanian |
#5
|
|||
|
|||
I also found thousands of similar messages in the system log asl.log the first time running version 2.1 -- this was a smart update. The messages are like this:
[Sender /Applications/SuperDuper Folder/SuperDuper!.app/Contents/MacOS/SDCopy] [PID -1] [Message error processing extended attributes: Invalid argument] [Level 4] [UID -2] [GID -2] [Host xxxxxxxx] xxxxxxx is the name of the host computer This asl.log file is 18 Megabytes and it's mostly SD messages like this! Is there something wrong or is this expected? The size of the file worries me. I haven't tried to boot yet from this clone but does this look normal? |
#6
|
||||
|
||||
At present, there's nothing we can do right now, unfortunately, but we're looking again. The call that does the EA copying are logging in a weird way when they find unusual structures on the drive.
It might help to repair the startup volume -- not permissions, but the drive itself. You'll usually want to boot from your Tiger install DVD and run Disk Utility from the Installer or Utilities menu to do that. (For the curious, those who have permission from Apple can look at where the logging is coming from by navigating to this page -- the errors are coming from copyfile_xattr, which is called from SD under Tiger, via copyfile, to copy the EAs.)
__________________
--Dave Nanian |
#7
|
|||
|
|||
Quote:
|
#8
|
||||
|
||||
OK. Try what I suggested above and repair the drive. Make sure to only use Tiger-qualified tools: repairing with old versions of DW (etc) might be corrupting the EA part of the directory structure.
__________________
--Dave Nanian |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|