Time machine error - linking files?

Completely new to me... what does the console say (under system messages)?

Yeah. I think that TM is too far ahead of its time. It reminds me of Charles Babbage's attempt to build a mechanical calculator. He designed it to work, however it was far too complex and could not be built. TM, automatic backup system, backing up all files and new files, it needs to be redesigned. Or Apple just didn't take enough time to work out all of the bugs.

I am seeing the same error.

Here is what the log is showing.... (repeated every hour):

2008-01-16 21:02:13.785 Backup[2834:7203] * -[NSConditionLock dealloc]: lock (<NSConditionLock: 0xda3540> '(null)') deallocated while still in use
2008-01-16 21:02:13.799 Backup[2834:7203] * Break on _NSLockError() to debug.
2008-01-16 21:02:41.542 Backup[2834:9203] backup reference was nil for (0x1b38e020) /Users/bsb/Library/Preferences/com.apple.iCal.AlarmScheduler.plist
2008-01-16 21:02:41.783 Backup[2834:9203] backup reference was nil for (0x1b3904a0) /Users/bsb/Library/Preferences/com.apple.iCal.AlarmScheduler.plist
2008-01-16 21:02:42.470 Backup[2834:9203] backup reference was nil for (0x1b392020) /Users/bsb/Library/Preferences/com.apple.iCal.AlarmScheduler.plist
2008-01-16 21:02:42.685 Backup[2834:9203] backup reference was nil for (0x1b3ac9f0) /Users/bsb/Library/Preferences/com.apple.iCal.AlarmScheduler.plist
2008-01-16 21:02:42.904 Backup[2834:9203] backup reference was nil for (0x1b376090) /Users/bsb/Library/Preferences/com.apple.iCal.AlarmScheduler.plist
2008-01-16 21:02:43.135 Backup[2834:9203] backup reference was nil for (0x1b3ad640) /Users/bsb/Library/Preferences/com.apple.iCal.AlarmScheduler.plist
2008-01-16 21:02:43.353 Backup[2834:9203] backup reference was nil for (0x1b3a1e60) /Users/bsb/Library/Preferences/com.apple.iCal.AlarmScheduler.plist
2008-01-16 21:02:45.019 Backup[2834:9203] backup reference was nil for (0x1b3dce30) /Users/bsb/Library/Preferences/com.apple.iCal.AlarmScheduler.plist
2008-01-16 21:02:46.973 Backup[2834:9203] backup reference was nil for (0x1b3cd350) /Users/bsb/Library/Preferences/com.apple.iCal.AlarmScheduler.plist
2008-01-16 21:02:47.774 Backup[2834:9203] backup reference was nil for (0x1b3ee770) /Users/bsb/Library/Preferences/com.apple.iCal.AlarmScheduler.plist
2008-01-16 21:02:48.005 Backup[2834:9203] backup reference was nil for (0x1b3f14f0) /Users/bsb/Library/Preferences/com.apple.iCal.AlarmScheduler.plist
2008-01-17 21:02:05.480 Backup[5986:7203] * -[NSConditionLock dealloc]: lock (<NSConditionLock: 0xdc89b0> '(null)') deallocated while still in use
2008-01-17 21:02:05.493 Backup[5986:7203] * Break on _NSLockError() to debug.
2008-01-17 21:02:27.206 Backup[5986:9103] backup reference was nil for (0x1b3c7400) /Users/bsb/Library/Preferences/com.apple.iCal.AlarmScheduler.plist
2008-01-17 21:02:27.337 Backup[5986:9103] backup reference was nil for (0x1b3c85e0) /Users/bsb/Library/Preferences/com.apple.iCal.AlarmScheduler.plist
2008-01-17 21:02:27.677 Backup[5986:9103] backup reference was nil for (0x1b3c8990) /Users/bsb/Library/Preferences/com.apple.iCal.AlarmScheduler.plist
2008-01-17 21:02:27.853 Backup[5986:9103] backup reference was nil for (0x1b3d7ca0) /Users/bsb/Library/Preferences/com.apple.iCal.AlarmScheduler.plist
2008-01-17 21:02:28.388 Backup[5986:9103] backup reference was nil for (0x1b3e3870) /Users/bsb/Library/Preferences/com.apple.iCal.AlarmScheduler.plist
2008-01-17 21:02:28.552 Backup[5986:9103] backup reference was nil for (0x1b3df1c0) /Users/bsb/Library/Preferences/com.apple.iCal.AlarmScheduler.plist
2008-01-17 21:02:28.641 Backup[5986:9103] backup reference was nil for (0x1b3f0a80) /Users/bsb/Library/Preferences/com.apple.iCal.AlarmScheduler.plist
2008-01-17 21:02:29.504 Backup[5986:9103] backup reference was nil for (0x1c110aa0) /Users/bsb/Library/Preferences/com.apple.iCal.AlarmScheduler.plist
2008-01-17 21:02:30.661 Backup[5986:9103] backup reference was nil for (0x1c134db0) /Users/bsb/Library/Preferences/com.apple.iCal.AlarmScheduler.plist
2008-01-17 21:02:31.273 Backup[5986:9103] backup reference was nil for (0x1c12f3b0) /Users/bsb/Library/Preferences/com.apple.iCal.AlarmScheduler.plist
2008-01-17 21:02:31.426 Backup[5986:9103] backup reference was nil for (0x1c13e7d0) /Users/bsb/Library/Preferences/com.apple.iCal.AlarmScheduler.plist
2008-01-18 21:02:04.923 Backup[9184:7203] * -[NSConditionLock dealloc]: lock (<NSConditionLock: 0xddf290> '(null)') deallocated while still in use
2008-01-18 21:02:04.928 Backup[9184:7203] * Break on _NSLockError() to debug.
2008-01-18 21:02:22.304 Backup[9184:9103] backup reference was nil for (0x1b3f78d0) /Users/bsb/Library/Preferences/com.apple.iCal.AlarmScheduler.plist
2008-01-18 21:02:22.432 Backup[9184:9103] backup reference was nil for (0x1b407b10) /Users/bsb/Library/Preferences/com.apple.iCal.AlarmScheduler.plist
2008-01-18 21:02:22.788 Backup[9184:9103] backup reference was nil for (0x1b40a0f0) /Users/bsb/Library/Preferences/com.apple.iCal.AlarmScheduler.plist
2008-01-18 21:02:22.956 Backup[9184:9103] backup reference was nil for (0x1b41d810) /Users/bsb/Library/Preferences/com.apple.iCal.AlarmScheduler.plist
2008-01-18 21:02:23.132 Backup[9184:9103] backup reference was nil for (0x1b422b70) /Users/bsb/Library/Preferences/com.apple.iCal.AlarmScheduler.plist
2008-01-18 21:02:23.296 Backup[9184:9103] backup reference was nil for (0x1b428ee0) /Users/bsb/Library/Preferences/com.apple.iCal.AlarmScheduler.plist
2008-01-18 21:02:23.364 Backup[9184:9103] backup reference was nil for (0x1b42d8e0) /Users/bsb/Library/Preferences/com.apple.iCal.AlarmScheduler.plist
2008-01-18 21:02:24.626 Backup[9184:9103] backup reference was nil for (0x1b43a500) /Users/bsb/Library/Preferences/com.apple.iCal.AlarmScheduler.plist
2008-01-18 21:02:25.427 Backup[9184:9103] backup reference was nil for (0x1b473430) /Users/bsb/Library/Preferences/com.apple.iCal.AlarmScheduler.plist
2008-01-18 21:02:26.062 Backup[9184:9103] backup reference was nil for (0x1b439840) /Users/bsb/Library/Preferences/com.apple.iCal.AlarmScheduler.plist
2008-01-18 21:02:26.215 Backup[9184:9103] backup reference was nil for (0x1b474ed0) /Users/bsb/Library/Preferences/com.apple.iCal.AlarmScheduler.plist
2008-01-19 07:02:23.485 Backup[9809:7603] * -[NSConditionLock dealloc]: lock (<NSConditionLock: 0xd13540> '(null)') deallocated while still in use
2008-01-19 07:02:23.486 Backup[9809:7603] * Break on _NSLockError() to debug.
2008-01-19 07:02:23.502 Backup[9809:7203] * -[NSConditionLock dealloc]: lock (<NSConditionLock: 0xd37730> '(null)') deallocated while still in use
2008-01-19 07:02:23.503 Backup[9809:7203] * Break on _NSLockError() to debug.
2008-01-20 07:02:23.574 Backup[11022:7203] * -[NSConditionLock dealloc]: lock (<NSConditionLock: 0x1525b940> '(null)') deallocated while still in use
2008-01-20 07:02:23.585 Backup[11022:7203] * Break on _NSLockError() to debug.
2008-01-20 07:02:39.314 Backup[11022:8e03] backup reference was nil for (0x1b427f30) /Users/bsb/Library/Preferences/com.apple.iCal.AlarmScheduler.plist
2008-01-20 07:02:39.874 Backup[11022:8e03] backup reference was nil for (0x1b4237b0) /Users/bsb/Library/Preferences/com.apple.iCal.AlarmScheduler.plist
2008-01-20 07:02:40.190 Backup[11022:8e03] backup reference was nil for (0x1b429910) /Users/bsb/Library/Preferences/com.apple.iCal.AlarmScheduler.plist
2008-01-20 07:02:40.345 Backup[11022:8e03] backup reference was nil for (0x1b442960) /Users/bsb/Library/Preferences/com.apple.iCal.AlarmScheduler.plist
2008-01-20 07:02:40.480 Backup[11022:8e03] backup reference was nil for (0x1b440e80) /Users/bsb/Library/Preferences/com.apple.iCal.AlarmScheduler.plist
2008-01-20 07:02:40.634 Backup[11022:8e03] backup reference was nil for (0x1b45c310) /Users/bsb/Library/Preferences/com.apple.iCal.AlarmScheduler.plist
2008-01-20 07:02:40.735 Backup[11022:8e03] backup reference was nil for (0x1b4368d0) /Users/bsb/Library/Preferences/com.apple.iCal.AlarmScheduler.plist
2008-01-20 07:02:42.063 Backup[11022:8e03] backup reference was nil for (0x1b4792b0) /Users/bsb/Library/Preferences/com.apple.iCal.AlarmScheduler.plist
2008-01-20 07:02:42.853 Backup[11022:8e03] backup reference was nil for (0x1b498780) /Users/bsb/Library/Preferences/com.apple.iCal.AlarmScheduler.plist
2008-01-20 07:02:43.477 Backup[11022:8e03] backup reference was nil for (0x1b4532c0) /Users/bsb/Library/Preferences/com.apple.iCal.AlarmScheduler.plist
2008-01-20 07:02:43.630 Backup[11022:8e03] backup reference was nil for (0x1b4a7370) /Users/bsb/Library/Preferences/com.apple.iCal.AlarmScheduler.plist

Message was edited by: Brian Brumfield

I have been running Time Machine since early November, backing up to a G-Drive FireWire external, with no problems whatsoever.

By any chance are you using a USB drive as your TM backup?

As preventative maintenance, I verify the TM destination drive weekly with Disk Utility.

Could the com.apple.iCal.AlarmScheduler.plist file be corrupt?

You could try deleting that file.

FIXED (for me)!!

Okay, that plist file issue was just a weird symptom. The file was not even there. I sync this mini with my MBP, so I copied those files from the MBP, but it did not resolve the TimeMachine issue.

After much thread diving around the various forums that are discussing TimeMachine frustrations, I saw a recommendation to remove the in-process file. (It was late last night -- I'm looking for the URL)

So I removed it and TimeMachine started working again.

This was, however, after:
1. using disk utility to scan the backup disk (and it did report an invalid sibling link error, and repair to the catalog) -- didn't stop the failure directly
2. Stopping spotlight indexing on that disk -- didn't stop the failure directly
3. Removing the /Volumes/[mount-point]/.Spotlight-V100 folder (a suggestion on another thread) -- didn't stop the failure directly

Good luck.

Message was edited by: Brian Brumfield

For Rotlex,

Remember that TM uses hard links to save space so although a previously backed up file in today's backup, if you "Get Info" on it, will indicate the full file size, it is still only a link to the previously-backed-up data.

So if your TM destination drive fails and you recover its data to maintain the TM history, you need to recover all of the TM folders.

Also, here is some background on the appearance of this issue for me.

1. It followed a string of brown-outs and failure of my UPS.
2. A timemachine backed-up disk corrupted in the process, reporting unrecoverable sibling link errors (tried single-user mode, fsck_hfs -b/-f/etc). NOTE: I think that the backup volume also became corrupted at this time. Not from backing up the corrupted drive, but from the repeated (about 10 over 3 days) crashes of the machine.
3. I reformatted that drive, and then restored the whole disk with timemachine
4. The next backup attempt failed with that 'failed while linking files' error.

Thinking maybe that I mistakenly reformatted with the wrong partition type (extended, journaled, case-sensitive -- instead of just extended and journaled), so I again, reformatted the disk with the alternative format, and restored again.

No dice.

Then I went through the rest of the gyrations mentioned above, and came to the "in process" file removal, which was the last step I took before it started working again.

I will say this -- the restore process that I went through -- after that initial drive corruption, was the most amazing data reclamation process that I have ever experienced. With 22 years in high-tech, I've seen and tried virtually every back-up solution that there has been (back to 9-track 200MB tapes, DAT, DLT, zip disks, STK Silos, NAS, everything), and this one blew me away. I had a smile on my face during the restore, and when it was done I had to pick my jaw up off the desk.

That experience was then tainted by this rotten, vague, and maddening error. Ugh. But man, when TimeMachine works, it really works.

The key to TimeMachine's success is the blending of the hardware/software and GUI solution. *When it is working* -- you don't have to guess about the backup medium. Which tape/disk has the stores with your missing data? What timeframe? Which files are missing? You can just pop back through time in whichever folder you need, choose any view you want of the files, even preview them if you want, and select whatever is appropriate for restore. I cannot understate the absolute magnitude of this solution. It is simply the most amazing process I ever went through to restore lost files, and IT WORKED FLAWLESSLY! (note: I am talking about the restore) Obviously there are a lot of components to TImeMachine that have to be working in harmony for Apple to pull this off. That is the chink in the armor of this marvelous tool.

Are you synchronizing with dot Mac? There have been some glitches there, which might contribute to a problem.

Did you manually copy the .plist file? That may have been confusing to TM, especially if there was an earlier file linked to the same application on the Mini.

Thanks, Brian. That's illuminating.

Yes, Time Machine is a sophisticated implementation of multiple components, which is why I think it's important to verify drives weekly, have a good UPS, and use Apple standard protocols.

You had a "perfect storm" with brown-outs and UPS failure.

I've read other posts about problems with formatting a drive using case-sensitive extended journaled rather than simply Extended Journaled. Good observation!

I've made it a point to allow Spotlight to finish indexing.

Enjoy!

dr'

Syncing with dotMat, yes.

I copied the plist files after I saw that 'nill' error in the logs. Not coincidentally, that particular string of errors went away once the files existed. I've been having a sync issue around iCal and alarms, but that is a whole other thread, not related to TimeMachine.

Apart from the perfect storm of power related issues (my new UPS is working and functioning perfectly via apcupsd -- yet another thread :)), I believe that the crashes were the root trigger of this TimeMachine issue.

Crash -> corrupted disks -> invalid/corrupted "in process" file -> TimeMachine wig-out.

In retrospect it's hard to say what one thing or combination of things worked to resolve this, but I suspect it's a combination of two key actions on my part:
1. Disk Utility repair of the volume, and
2: Removal of the corrupt "in process" file.

Y'all will have to forgive me for not wanting to recreate this problem in order to isolate the cure. :-/

Message was edited by: Brian Brumfield

Y'all will have to forgive me for not wanting to recreate this problem in order to isolate the cure. :-/

Absolutely.

Yep, I'm amazed by how well Time Machine works -- a very user-friendly solution to an important user need. Still important, though, to do preventative disk maintenance. I'm going to update to Leopard-compatible version of Disk Warrior, but in the meantime weekly verify of all drives with Disk Utility.

Enjoy!

Just recieved the same error message, and now have fixed the problem.

The problem was caused because I repartitioned one of my disks to combine a couple of volumes. So that made the two remaining partitions have their original names. I was only backing up one of the partitions with TM. I then restored that partition from TM. Worked great. Then I made a some changes in that partition and, tried to back it up with TM. Thats when I found the error message.

I read the discussions. Repaired my disk with disk utility and it had link errors. Read the console messages and could see which volume was giving the problem. The one that was repartitioned but with the same name. It was still trying to copy the entire partition to the backup, but could not link to the previous backup, probably because it was reformatted.

Solution: so I changed the name of the partition slightly and now TM is happy again.

Renaming partition just worked for me as well.