Recent adventures
Nov. 7th, 2009 12:08 pmOur small band of adventurers (me, two terriers) was strolling through a normal-appearing suburban landscape on our way to an afternoon of writing when we were ambushed by a gnarly computer error ("Backup Error send_files failed to open "//mds-crash-state": Permission denied rsync(21973) malloc: ***error for object 0x300920: double free rsync(21973) malloc: *** set a breakpoint in szone_error to debug rsync error: some files could not be transferred (code 23)at main.c(639)").
Caught totally unawares we responded the best we could (roll Computer Knowledge, Roll Intimidation, computer wins).
After suffering stress and intimidation, we tried magic (roll Drive Genius tm, roll Diskwarrior tm, roll Drive Genius tm again, computer wins).
Staggering back after suffering moderate damage, we called for reinforcements (roll Email Xavid, roll Try Ideas, computer wins).
With our final breath, we made an appointment with Apple's Genius Bar, and emailed Xavid one last time. He figured out that the error message meant that there was a problem with permissions on a file named mds-crash-state (it seems obvious now that he pointed it out), I found the file, determined that it was damaged beyond repair, and deleted it.
So far the backup is still running in the background but I think it is past the point where it stopped before and the computer seems completely recovered. Yay! (Thanks Xavid) Now it's time to roll Rake Leaves and Put Stuff Away.
Caught totally unawares we responded the best we could (roll Computer Knowledge, Roll Intimidation, computer wins).
After suffering stress and intimidation, we tried magic (roll Drive Genius tm, roll Diskwarrior tm, roll Drive Genius tm again, computer wins).
Staggering back after suffering moderate damage, we called for reinforcements (roll Email Xavid, roll Try Ideas, computer wins).
With our final breath, we made an appointment with Apple's Genius Bar, and emailed Xavid one last time. He figured out that the error message meant that there was a problem with permissions on a file named mds-crash-state (it seems obvious now that he pointed it out), I found the file, determined that it was damaged beyond repair, and deleted it.
So far the backup is still running in the background but I think it is past the point where it stopped before and the computer seems completely recovered. Yay! (Thanks Xavid) Now it's time to roll Rake Leaves and Put Stuff Away.