System Crash on Time Machine Backup

Question

I have been running timemachine without issue for several months now. A few weeks back I started to get a back up error but then things seemed to work out. Now.....everytime timemachine runs, it crashes my system. It seems to start up ok, then a curtain comes down and says I must shut down my mac. I restart and get the following error message:
Sun Jun 1 10:59:30 2008
panic(cpu 0 caller 0x0031678A): "btreeswapnode: about to write corrupt node!\n"@/SourceCache/xnu/xnu-1228.4.31/bsd/hfs/hfs_btreeio.c:197
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x34b0f918 : 0x12b0f7 (0x4581f4 0x34b0f94c 0x133230 0x0)
0x34b0f968 : 0x31678a (0x484588 0x92d6000 0x1 0x34b0fa40)
0x34b0f9a8 : 0x1fa244 (0x3054aa60 0x5c85004 0x0 0x0)
0x34b0fa68 : 0x1fb543 (0x0 0x0 0x200 0x0)
0x34b0fab8 : 0x3388b1 (0x4396e08 0x5c853b4 0x484261fc 0x2597b)
0x34b0fae8 : 0x325fa5 (0x5c85004 0x2 0x0 0x1)
0x34b0fc58 : 0x1f3097 (0x34b0fc78 0x5e26660 0x4 0xb52b9a4)
0x34b0fca8 : 0x1e2b5d (0x6354630 0x9361490 0x34b0fe2c 0xb52b9a4)
0x34b0ff78 : 0x3dcf13 (0xa8bec50 0xb52b8a0 0xb52b8e4 0x1)
0x34b0ffc8 : 0x19f1c3 (0x766b0e0 0x0 0x1a20b5 0x4b71480)
No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xb0102578
BSD process name corresponding to current thread: backupd
Mac OS version:
9C7010
Kernel version:
Darwin Kernel Version 9.2.2: Tue Mar 4 21:17:34 PST 2008; root:xnu-1228.4.31~1/RELEASE_I386
System model name: MacBookPro4,1 (Mac-F42C89C8)
I am using a Macbookpro with OSX version 10.5.2. My time machine is an apple integrated airport/harddrive. (It is working fine as an airport). If it helps, I also seem to be having the same problem when I try to connect to another apple computer via bluetooth. If anyone can help, I would be eternally grateful!!!!!!

Answer 1

Yes, you do have to do a full backup from scratch.
No you don't have to erase the drive or lose all your backups. But I'm not sure how useful they are because they are corrupt.
I started to have this problem before I upgraded to 10.5.3; upgraded to 10.5.3 in hopes of fixing the problem; no dice.
When the OS is restarted, it offers to send the crash info to Apple. I let it do that a few times. You guys should, too. I don't know how else to bring this to Apple's attention. Call technical support? My life is too short.
I'm pretty sure this is some sort of a bug: the backup data is corrupted and the OS can't recover from it. I don't know if this has anything to do with the "sparse bundle" remote mounted format but I suppose that is likely. But the data shouldn't get corrupted and the OS should tolerate it better.
In the mean time:
1. Stop TM
2. Open the backup disk itself with the finder (you may need to use
Go->Connect to server to do this.)
3. Create a new folder, say "BadBackupData".
4. Select the backup data (it will have a name ending with ".sparsebundle")
5. Drag into the new folder created in 3.
6. Turn TM back on
This will cause a new complete backup. It won't lose your old data. It doesn't require a disk erase.
Someone really should make sure this is reported to Apple.