Corrupted disk, but computer runs fine?

[YodaOfDarkness]

So I decided to run a disk verification on Macintosh HD using Disk Utility after formatting some external hard drives, and two minutes into the verification process it stopped and said

Disk Utility stopped verifying "Macintosh HD"

This disk needs to be repaired. Start up your computer with another disk (such as your Mac OS X installation disc), and then use Disk Utility to repair this disk.

Log:

2010-02-14 21:23:35 -0800: Disk Utility started.

2010-02-14 21:23:51 -0800: Verifying volume “Macintosh HD”
2010-02-14 21:23:51 -0800: Starting verification tool:
2010-02-14 21:23:52 -0800: Performing live verification.
2010-02-14 21:23:52 -0800: Checking Journaled HFS Plus volume.
2010-02-14 21:23:53 -0800: Checking extents overflow file.
2010-02-14 21:23:53 -0800: Checking catalog file.
2010-02-14 21:25:20 -0800: Missing thread record (id = 33880151)
2010-02-14 21:25:20 -0800: Incorrect number of thread records
2010-02-14 21:25:20 -0800: Checking multi-linked files.
2010-02-14 21:25:21 -0800: Checking catalog hierarchy.
2010-02-14 21:25:21 -0800: Invalid volume file count
2010-02-14 21:25:21 -0800: (It should be 733788 instead of 733789)
2010-02-14 21:25:21 -0800: Checking extended attributes file.
2010-02-14 21:25:21 -0800: Checking volume bitmap.
2010-02-14 21:25:21 -0800: Checking volume information.
2010-02-14 21:25:21 -0800: The volume Macintosh HD was found corrupt and needs to be repaired.
2010-02-14 21:25:21 -0800: Error: This disk needs to be repaired. Start up your computer with another disk (such as your Mac OS X installation disc), and then use Disk Utility to repair this disk.2010-02-14 21:25:21 -0800:

Do I need to do a disk repair, or is OSX just being fussy about nothing (as it still works perfectly fine, never would've thought there was a problem). Oh, if it matters, I'm on an early 2008 Macbook Pro running 10.6.2.

 

[silencer88]

If disk utility is complaining, then it found a problem. I wouldn't risk data loss or a crash by not fixing it, especially since it's so easy. Boot from your installation DVD and run a repair.

 

[Denarius]

Judging by the file count, I'd say it's just one dodgy file somewhere that doesn't have to be a system file so won't necessarily cause any failures. You'll probably only know exactly which one if you stumble across it by accident.

I agree with the other chap, just do what it says and forget about it and you can't go wrong.

 

[t0mat0]

Worth running the disk utility as it'll likely fix the issue and you don't have to worry about it then.