"unknown mac error"

[davidduff]

i've noticed that my retrospect 9 engine is spitting out a lot of console messages of the following form:

 

7/14/12 19:02:41  com.retrospect.retroengine[118] #2> MapError: unknown Mac error 22
7/14/12 19:02:41  com.retrospect.retroengine[118] #2> TVol::GetInfo: UGetVolumeInformation failed, /private/var/folders/zz/zzzivhrRnAmviuee+++++++++++/-Tmp-/FPInstallMountPoint/, oserr 22, error -1002

 

i rarely seem to see them isolation. instead, once they start they keep repeating every two seconds or so. it appears as though retrospect is continuing to make progress (it's not completely frozen and the remaning/completed fields get updated), however it also appears that once these messages start appearing, retrospect slows down considerably.

 

i have tried restarting the server, the messages seem to stop for a while, then eventually i notice that they start up again. i haven't yet been able to determine the a pattern or sequence of events that cause them start. odd that there is no mention in the error itself of what the "cause" is or of what retrospect is trying to do that causes the error. rather, it has the feel of an internal error or debug statement or something. i can't tell for sure what "#2>" part might mean but it smacks to me of something left in by a programmer that really isn't intended to be seen by a user.

 

my intuition is that stuff that retrospect writes to /private/var/folders/* should be mainly ephemeral stuff and that if i were to simply delete that entire folder, that it shouldn't hurt anything. i haven't tried that yet. thought i'd float this issue out to the forum before doing so.

 

any ideas of what causes this? how to fix? is it "safe" to just blow away the entire containing folder?

[davidduff]

i looked and the referenced path does exist. it is an empty dir owned by root, owner-writable and world readable if i'm not mistaken.

bash-3.2# pwd ; ls -l
/private/var/folders/zz/zzzivhrRnAmviuee+++++++++++/-Tmp-
total 22624
drwxr-xr-x  2 root  wheel	    68 Jul 11 18:41 FPInstallMountPoint
drwxr-xr-x  3 root  wheel	   102 Jul 11 18:41 FPUnpackPath
-rw-r--r--@ 1 root  wheel  11579718 Jul 11 18:41 decryptedFile.dmg
drwxr-xr-x  2 root  wheel	    68 Jul 10 03:35 hsperfdata_root

[Lennart_T]

What do you mean by "restarting the server"? Did you restart the server computer or just the Retrospect engine?

 

I would try repairing the hard drive and also repair permissions.

[Daniels]

The unknown mac error was left over debugging code that should have been removed. As long as the backups complete succesfully you can ignore this message. See tech note 9730 for more information.

[davidduff]

thanks for this info - can you tell me how i can find tech note 9730? searching for "tech note 9730" on the retrospect support site does not get me there. searching for "unknown mac error" seemingly yields a short summary but with no link.

 

or else perhaps it is the case that the entirety of the tech note consists of "

This is debug logging displayed by Retrospect and is not an actual error to be worried about. As long as the backup reports 'completed successfully' or has no errors displayed with a Red Arrow in the left margin, your backup is secure."

[Lennart_T]

thanks for this info - can you tell me how i can find tech note 9730? searching for "tech note 9730" on the retrospect support site does not get me there.

Searching for just 9730 in the knowledge base gives you the article:

http://kb.retrospect.com/articles/en_US/Retrospect_Article/Unknown-Mac-Error-20/?q=9730&l=en_US&fs=Search&pn=1

 

Yes, very short indeed, but still the article.

[padorange]

Searching for just 9730 in the knowledge base gives you the article:

http://kb.retrospect...&fs=Search&pn=1

 

Yes, very short indeed, but still the article.

 

Very short indeed.

So we do not have to worry... OK.

But why Retrospect report this as an error and why does it display a warning icon beside the script summary.

Other save has a green icon, except one for me tha has always a warning icon (because of unknown error 20).

 

I can understand that the OS could return an error that's is not a real one (strange but OK) but why registered this as a warning.

The day we have a real warning, the problem will be hidden but the warning icon that appears every day...