Posts Tagged ‘time machine’

Time Machine making mount_hfs & syslogd use CPU resources

Time Machine decided to misbehave. I’m still running OS X 10.7.5. 

mount_hfs & syslogd were consuming close to 100% CPU time (on this machine with 2 cores), so it was clearly grinding the system to a halt. I couldn’t kill the mount_hfs process (kill -9), but I could kill syslogd though it would repeatedly restart.

Problem was only solved via power cycling. There was advice from Macworld titled: One fix for a runaway syslogd process, but nothing from that was useful.

Root cause seems to be another external disk going wonky. Yes, I’ve seen 2 disks die being Time Machine backups in a span of what, 3.5 years? Worrying trend. 

root 30064 88.0 0.0 2434804 776 ?? R 10:40am 2:45.62 /sbin/mount_hfs -u 99 -g 99 -m 755 -o nodev -o noowners -o nosuid -o owners /dev/disk1s2 /Volumes/Expansion Drive

Incremental backup that uses MySQL

A while back, Ted Ts’o asked for a incremental backup solution that used a database. It reminded me of the talk at the 2009 MySQL Conference & Expo, titled Build your own MySQL time machine.

Chuck and Mats will talk about the backup and replication code, and will show off a web interface, that allows you to go back in time, similar to Apple’s Time Machine in Mac OS X. Its a talk that I most certainly want to attend, as an avid Time Machine user.

Register for the MySQL Conference & Expo 2009 before February 16, and you’ll get an early bird discount (saving $200). April 20-23 2009 will be a rocking few days, see you there.

Fixing Time Machine: Backup failed with error: 11

Got the dreaded “Backup failed with error: 11” with Time Machine. Actually, I only got the dreaded message from the Console – the application itself, just kept failing silently with no suggestions (Apple, this is your cue to make Time Machine a little more useful). Nothing in Apple’s knowledgebase. Nothing seemingly useful come up in a Google search (i.e. something conclusive)

Solution? Delete:

/Time Machine Backups/Backups.backupdb/nameOfComputer/date.inProgress

It’ll ask for your password, and be gone with the file. Now the backups should start working again.

An example of what the Console showed:

13/08/2008 12:51:57 /System/Library/CoreServices/backupd[4946] Error: (-43) copying /Users/byte/Library/Application Support/Adium 2.0/Users/Default/Logs/AIM.bytebotdotnet to /Volumes/Time Machine Backups/Backups.backupdb/lovegood/2008-08-13-125154.inProgress/424A6617-37A5-4C20-8845-764D9167E317/Macintosh HD/Users/byte/Library/Application Support/Adium 2.0/Users/Default/Logs
13/08/2008 12:51:57 /System/Library/CoreServices/backupd[4946] Copied 702 files (169 KB) from volume Macintosh HD.
13/08/2008 12:51:57 /System/Library/CoreServices/backupd[4946] Copy stage failed with error:11
13/08/2008 12:52:03 /System/Library/CoreServices/backupd[4946] Backup failed with error: 11
13/08/2008 12:55:31[73] (0x10dbd0.Locum[4961]) Exited: Terminated