How's this for disk usage?

[ColonelPanic]

Not sure how I can keep having technology that defies the laws of, um, everything but here we go again. First, my GPS tells me I'm going 130-something and then 300+ MPH... Now, however I accomplished cramming 38 TB onto a 64 GB partition, I'll never know. This is the second time this has happened.... There are probably a few really whacked out files around somewhere like last time when I had "14 TB" in a handful of jpeg's. I'm guessing I have some file system issues on that drive (formatted in ReiserFS.) lol

Attached files

[ColonelPanic]

Wow... Not sure if any of you guys remember mod music files from waaaaay back in the day... We're talking old stuff - some was probably made on a Commodore/Amiga/something like that, the newer stuff was at least a decade old.. Yeah, what should have been no more than a couple hundred kb each, the OS was seeing some as large as 5000 GB. That's funny. Deleted the offending files and it's looking much more normal now. I've seen file system corruption skew things like free space, but this was beyond nuts!

Attached files

[robodoc]

Wow, sounds to me like a hole or flaw that I am sure someone can turn into a virus. Better keep that one to yourself.

[joatmon]

your Linux advocacy just lost a few credibility points

[ColonelPanic]

No way! See, um, this just goes to show how superior Linux is with the fact that it can handle huge drives right now, not just in the future.... or something.

[robodoc]

Ah, don't fret Colonel, Linux, your Vibe.....you can't win them all!! LOL

[millster]

Quote, originally posted by joatmon »your Linux advocacy just lost a few credibility points No sir. Not a single point. I've seen Windows pull this trick too. I had a friend with a laptop with a strangely full hard disk. Having located the offending folder (the properties showed it to be 30GB) we opened it and ordered the view by file size. It quickly became apparent that there was no way the files added up to 30GB. To make a long story short, we ended up using a program called BartPE which boots the machine into a shrunken version of XP with a killer file management utility that was actually able to view the corruption as files. Somehow, the machine had written a number of .TMP files between 1GB and 4GB to the disk that were not visible to Windows and yet somehow were visible to BartPE.

[Mr. Poopypants]

Quote, originally posted by joatmon »your Linux advocacy just lost a few credibility points Yep, your little penguin is BUSTED, CP.

[Kari]

Not if anything that can calculate disk usage off a corrupt file can do it too... *pets Tux* It's okay, we still love you...

[Mr. Poopypants]

Quote, originally posted by Kari »Not if anything that can calculate disk usage off a corrupt file can do it too... *pets Tux* It's okay, we still love you... Trying to make excuses???

[Kari]

Nope, millster said Windows is equally guilty.

[Mr. Poopypants]

Damn. OK, fine.

[Kari]

LOL...See...it's not just little Tux that gets confused every now and then... Though multiple terabytes makes for a pretty cool screen shot since such a drive does not exist and probably won't for at least 10 or 15 years...heh.

[Mr. Poopypants]

I was watching tech tv, yes I know, I'm a nerd. They had a computer on RAID with 2 terabytes of storage.

[Kari]

It's okay, I like TechTV too...at least I used to, before it became video game TV. *weeps for the original Screen Savers*Wonder how far away we really are from having at least a 1 TB hard drive in a PC...

[Mr. Poopypants]

In one hard drive.....not too far. I would give it 9 months to a year.