Let's see...that's about 16 Exabytes more than what a normal Hard Drive can hold. Have you been fooling around with ResEdit? Have you tried running Norton SystemWorks to fix this? If this is a big deal, I recommend you run Norton.
Since 16,777,216 is 2^24, and a terabyte is 2^40 (at least as programmers count, by 1024s instead of by 1000s), you must have 2^64 bytes in use! It can also be referred to as 16 exabytes (from the sequence mega, giga, tera, peta, exa).
That's 16 quintillion bytes in the continental system used in the U.S., France, and other countries or 16 trillion in the English system used in the U.K.
Since one published estimate put the sum of mankind's knowledge at 12 exabytes, and you have more than that, I conclude that some of your data must be redundant!
Of course, since 2^64 is also the same bit pattern as flat 0 in 64-bit binary arithmetic, there is a teeny tiny chance that a bug in Mac OS X is causing you to get the wrong display. Nawwwww!
if it was bits, then it would say Tb, not TB. B= Bytes b=bits
bits are off to the left of it anyway
still trying to fix my hard drive with Drive 10.
it's gotten better, before it wouldn't even mount, then error -60. Now disk utility shows no errors and i can use the partition. But it still get error -90 on drive 10. When i try to boot on that partition it just starts up on another one. Evem if i hold down the option key and select the one I want.
And yes, I will never use norton again after one incident other than for viruses, which i never get.
Once on the Cnet bandwidth meter i got a bandwidth of 23543 Gb/s. hehe
I also installed 6F19 on the partition, yay, i found a 6F9 downgrader. 6F9 was wacked.
i saw this once before on an imac running 9.2...it was an image file that was some huge terabyte number in size...couldn't delete it either...it messed up the entire computer and the whole thing had to be reformatted
the easiest way to run fsck (the mac os x file system check) is to boot from the mac os install cd and run disk utility to verify/repair the disk. the system automatically runs fsck on the startup disk at boot time, but if you want to be extra sure, you can restart your computer while holding down command-s and it will boot into single user (command line) mode. then you just type in "fsck -y" (the -y just tells it to say yes to any options) and it will check and repair your boot disk. when you're done, type in "reboot" (or restart, or something) and you should be good to go.