Very interesting, but way over my head. This reply seems to reinforce what both of you said:

"I have never had either of these problems despite all my crashes (lots)
and kernel panics (two). It should also be impossible for LimeWire to
cause these errors - either way, it's a bug in the file system drivers.

OSX has other oddities, like writing to the console taking up space even
though console.log is taking up none ('echo > /var/tmp/console.log'
usually doesn't keep it at zero size). There was also the 10.1 thing where
swapfiles took up no space (as reported by df).

Most of the time, though, all fsck reports is 'orphaned extent allocations'
or something (allocated space on disk that doesn't belong to any files). "


Anyway, the thread is viewable at macfixit.com. In case you want to reply and/or defend directly so that macfixit does not post incorrect information.