Slashdot Mirror


Terabyte Hard Drive Put To the Test

EconolineCrush writes "As a technical milestone, Hitachi's Deskstar 7K1000 hard drive is undeniably impressive. The drive is the first to pack a trillion bytes into a standard 3.5" form factor, and while some may argue the merits of tebi versus tera, that's still an astounding accomplishment. Hitachi also outfitted the drive with 32MB of cache—double what you get with standard desktop drives—making this latest Deskstar a leader in both cache size and total capacity. That looks like a great formula for success on paper, but how does it pan out in the real world? The Tech Report has tested the 7K1000's performance, noise levels, and power consumption against 18 other drives to find out, with surprising results."

90 of 376 comments (clear)

  1. Test? by Anonymous Coward · · Score: 5, Funny

    Now, my porn collection, THAT is what would put this drive to the test.

    1. Re:Test? by Hydryad · · Score: 5, Funny

      Why am I not surprised at all that porn is the third word in the comments about a terabyte hard drive. Pushing forward innovation since the dawn of time, hot steamy sex.

      --
      No sig for you, two weeks!
    2. Re:Test? by Anonymous Coward · · Score: 5, Funny

      Pushing forward.... and back... and forward.... and back....

  2. kanashhk shhk shhk by BadAnalogyGuy · · Score: 5, Funny

    ge ge ge kanashhk shhk shhk fzzke kek shhk shhk

    I love the sound of head crashes in the morning. Smells like... a coffee break.

    1. Re:kanashhk shhk shhk by Sensible+Clod · · Score: 4, Funny

      That's no moon, it's a hard drive!

      --

      The difference between spam and poop is that you don't have to dig through septic tanks looking for real food. -- Me
    2. Re:kanashhk shhk shhk by Anonymous Coward · · Score: 2, Funny

      Thats no moon - thats yo mama

    3. Re:kanashhk shhk shhk by david.given · · Score: 2, Interesting

      Hitachi_Hard-Drive_Project_-_Noriko_Version.mp3

      Written by James Postlethwaite, whose home page I can't find, and made entirely out of hard drive failure noises (Hitachi provide a nice set of wavs).

  3. RAID 5 Please by FF8Jake · · Score: 5, Funny

    I'm not losing my 1.5TB of porn to a single Hitachi Deathstar.

    1. Re:RAID 5 Please by tibike77 · · Score: 4, Funny

      Only 1.5 TB of porn ? That's like what, 350 DVDs worth ?

      That's 85-125 USD for your entire collection in one single copy.
      Or make that a nice round 200$ for two sets of copies.
      So, where can I get two 1.5 TB HDDs for 100$ each ?

      Sure, the "seek time" would suck, but then again who cares, it's porn, not like you'll die if you wait 15 more seconds before you start looking at it... or are you ?

      --
      By reading this signature you agree to not disagree with the post you just read.
    2. Re:RAID 5 Please by Applekid · · Score: 5, Funny

      Only 1.5 TB of porn ? That's like what, 350 DVDs worth ? But how would we hide 350 DVDs from our parents?
      --
      More Twoson than Cupertino
    3. Re:RAID 5 Please by TurboStar · · Score: 4, Funny

      But how would we hide 350 DVDs from our parents?

      You have an entire basement. Look around, I'm sure you'll find somewhere.
  4. Data loss by B5_geek · · Score: 2, Interesting

    I feel bad enough when one of my 500GB drives goes tits up, I would hate to loose that much data on one drive.

    But on the other hand, a full-tower case loaded with those in a raid5 is enough to make me drool.

    --
    "The price good men pay for indifference to public affairs is to be ruled by evil men." ~Plato (427-347 BC)
    1. Re:Data loss by ipooptoomuch · · Score: 5, Funny

      500GB of data loss?!? I CRIED for a half hour over a filled 160GB drive after it got killed by an electrical storm. Even though it wasn't technically covered under warranty, the fine folks at best buy still took it back after I said a defective flux capacitor on the drive started it on fire.

    2. Re:Data loss by jimicus · · Score: 5, Insightful

      RAID 1+0 is the way to go for redundancy. Unless you're unlucky enough to lose both drives in one of the pairs making up the array, you can survive more than one drive failing.

      It's also the way to go for speed - your controller doesn't have to calculate the parity bits for every write operation (yes I know the parity sum is simple - that doesn't stop it from adding a bottleneck).

      RAID5 is most useful where:

      1. You desperately need the space.
      AND
      2. You can't afford the drives (or, for that matter, power/larger RAID controller) required to acheive the same space in RAID 1+0.

    3. Re:Data loss by blackicye · · Score: 4, Informative

      BTW: Turn off S.M.A.R.T. This is like the indication of an ink cartridge: When the maker thinks you need a new
      drive.


      In my experience, when S.M.A.R.T. tells you a drive is dead or dying, its not kidding.
    4. Re:Data loss by Jafafa+Hots · · Score: 2, Interesting
      I hear all of these stories of people having drives go bad, I don't understand it. I've owned hard drives since about 1981, I've gone through dozens, replacing them as they become obsolete and too small, and I have yet to have one fail on me - except the one I accidentally launched across a room. And even that one I managed to get most of the data off of.

      What are people doing with drives to make them fail?

      --
      This space available.
    5. Re:Data loss by Ex-MislTech · · Score: 3, Informative

      Some problems with RAID 1+0:

      Not all hardware controllers will allow you to do a reconstruct to add more
      space and extend the partitions later on RAID 10 or 1+0.

      Recovering from a failed 1+0 is ok if it is a "simple" failure.

      I have had better luck recovering RAID5's than 10's or 1+0's.

      --
      google "32 trillion offshore needs IRS attention"
    6. Re:Data loss by xtracto · · Score: 3, Insightful

      Yeah, I've got to agree with you. I think that is one of the worst advices I have read on slashdot... A hard disk died on me a month after the S.M.A.R.T. thing started to annoy... it was on a laptop. Fortunately, I bought a bigger driver and passed all the information before the defective drive went dead.

      While I agree that the S.M.A.R.T. heuristics might be a bit sensitive but if you consider what is at stake (yeah... your valuable pr0n collection), then I guess its better safe than sorry.

      And, comparing it to the ink cartdriges? I am sure *your life* (or work...) does not depend on printing or not that pr0n picture...

      --
      Ubuntu is an African word meaning 'I can't configure Debian'
    7. Re:Data loss by Eivind · · Score: 5, Informative

      That's nonsense. It isn't even true in theory. (at some point the remaining charge is below the noise-floor) If it wasn't you could store an infinite amount of data on a drive by simply filling it once with dataset1, overwrite by dataset2, overwrite by dataset3 and so on. You claim dataset1 will always be recoverable, so in this method, you could recover each of the sets and have stored triple amounts of data on the drive. You claim *any* amount of overwriting will be insufficient, so I guess I can store 1000 datasets on the drive then. Cool. Hint: The real world doesn't work like that

      Secondly, even if in theory you where rigth (which you aren't), in *practice* most data is not valuable enough that theres much real risk that anyone will recover it, even after something as simple as a one-time-all-nulls overwrite. (which is just about the suckiest overwrite you can do) Yes, in that case an expert lab *can* recover it, but odds are it won't happen.

      In practice, if you do the standard wipe, which is usually some variant of all-nulls, all ones, 3 times random, there is -zip- chance that anyone will be able to get at the data that was once on the platter.

      Now, what many (clueless people) do are "format" the drive or "delete" the files. These functions don't overwrite even once 99% of the platter, so files removed in this manner are certainly recoverable -- they're there in plaintext, just not referenced from the filesystem anymore. Something as simple as "cat /dev/hda | strings" will recover huge amounts of text from a hard-drive which has been erased in this manner.

    8. Re:Data loss by MrNaz · · Score: 5, Funny

      You really, really need to buy a lottery ticket.

      --
      I hate printers.
    9. Re:Data loss by sumdumass · · Score: 2, Interesting

      It's best buy, He could have started talking about temporal distortions in the space time continuum in the same process and they would have looked at him like he was a god.

      I go into bestbuy every once in a while just to screw with the geek-squad. One of my favorite things to do it read the specs of a system sitting on the shelf and ask someone if it would run that good with linux. Some would say anything if they thought you were going to buy it, some ask for the geek squad people to come over and field the question. And those boys tell you anything for any reason it seems. I have often thought about writing their answers down and publishing them somewhere. This reminds me of a time when a neighbor's cdrom quit working and he was told he needed a plug and play card (whatever that is) and it would cost $80 on top of the cdrom.

    10. Re:Data loss by zeromemory · · Score: 3, Informative

      Not all hardware controllers will allow you to do a reconstruct to add more
      space and extend the partitions later on RAID 10 or 1+0. Likewise, many hardware controllers won't let you extend a RAID-5 array, (unless they implement some dynamic stripe size hack, a la ZFS's RAID-Z).

      Recovering from a failed 1+0 is ok if it is a "simple" failure. Please explain what a !simple failure would be. Here, let me give you a 'simple' failure case where RAID-5 would be pretty difficult to recover from: a drive fails in your RAID-5 array, and you lose power or experience another hardware failure shortly afterwards, before you can replace the drive. Whoops, you just became another victim of the RAID-5 write-hole (see the section under RAID-5 performance).

      OK, here's why we use RAID-10 at my installation: it provides great performance and can survive multiple drive failures without the overhead of something like RAID-6. RAID-10 also has no 'write-hole'. Don't just take my word for it, though, check out this article from Adaptec comparing the merits of all the basic RAID levels and their nested brethren.
    11. Re:Data loss by Eivind · · Score: 4, Insightful

      No. I don't think you are. Or you are, but for a different reason.

      Even the NSA very very probably can not recover any useful information from a disk overwritten the way I wrote. They have lots of money and expertise, but the laws of physics apply to them too.

      But they could get at the information on your computer by other means that you'd be unlikely to detect, if they really wanted to. For example, if the information is from the net and you don't encrypt everything, they could easily wiretap your broadband. Getting a hardware-keylogger into your keyboard would be possible too, aswell as dozens of other tricks.

    12. Re:Data loss by proxima · · Score: 3, Insightful

      I have my desktop set up to mail me a warning and shut down on any SMART error. That should give me enough time to buy a new disk and salvage my data.

      I've always thought you have a slightly better chance of getting valid data off of a drive if you never actually power it down when it's failing. This is anecdotal from a power outage causing many old hard drives in a building to give up, with their computers normally having uptime measured in months or even years.

      Of course, to recover data like this you would need another computer accessible via the network, rather than installing a replacement in the desktop itself. Read any possible data off it while you still can, without putting it through the stress of powerdown/powerup.
      --
      "The universe seems neither benign nor hostile, merely indifferent." --Carl Sagan
    13. Re:Data loss by drsmithy · · Score: 2, Interesting

      It's also the way to go for speed - your controller doesn't have to calculate the parity bits for every write operation (yes I know the parity sum is simple - that doesn't stop it from adding a bottleneck).

      The "bottleneck" of parity calculations is so small as to be irrelevant. Parity-based RAID levels are bottlenecked by the much higher number of physical disk operations, not the parity calculations.

    14. Re:Data loss by Gr8Apes · · Score: 3, Informative

      I think you've missed the point - RAID 1+0 allows you to fail up to n drives (with 2 n needed to build the array).

      Additionally, should a drive fail, rebuilding will only marginally affect your performance, degrading it by a fraction compared to a RAID 5/6 rebuild. (Only 1 drive is affected out of your stripe set, the rest perform at peak operational speed)

      --
      The cesspool just got a check and balance.
    15. Re:Data loss by encoderer · · Score: 5, Informative

      Yesterday at a Best Buy in Ohio a guy and his wife were looking at 42" Sony LCDs. There was a 1080P for $1899 and a 1080i for $1599. Guy asked the sales associate what the difference was.

      Sales associate, I shit you not, said "The "P" is actually a newer product. It is 7 minor revisions later. We still carry the "i" because it's still very popular. The same thing happens with our wireless equipment, too. the "N" version is out, but most users are still buying the "G" Version"

      I approached the guy after the sales associate left and said "listen, that guy has no clue what he's talking about. I is interlaced, P is progressive. On an "i" it's drawing 540 lines every frame, on a "p" it's drawing all 1080. Go with the "P" if you can afford the difference. It's worth it"

    16. Re:Data loss by walt-sjc · · Score: 5, Informative

      I lost 3 drives out of 6 within a few hours of each other. Raid 1+0 saved my bacon. Zero down time. Got the email alert about the first drive, and scheduled a trip to the datacenter. Then I got the other two back to back a couple hours later. These were all 15K rpm SCSI drives which had survived a 2 week stress test burn-in, and had been in production for about a year, so it was totally unexpected. In another case, I lost 2 drives in a Raid 5 and had to resort to restoring the machine from backups - a day lost. Raid 6 performance is even worse than Raid 5, so I personally see no point - YMMV. Raid 5 and 6 rebuild time is also VERY slow compared to 1+0, taking 3 times longer in my testing.

      Anyway, what's that old saying? Expect the unexpected? When you buy a pile of drives, you are likely to get the batch from the same manufacturing line, day, etc. This probably also increases the chances of simultaneous failures if there is a physical quality problem. If you have two fail, expect a third. I generally don't mix up batches because I want to know where all the drives from a particular batch are, but maybe I should.

    17. Re:Data loss by MBGMorden · · Score: 2, Interesting

      Must just have good luck. I've bee using hard drives since 1991 or so (until then I was on Commodores with floppy only :)). I've been through dozens as well, and MOST of help up just fine. Exceptions are: 1gb Western Digital. This was the first drive to fail on me, but it was 1 week after I had gotten into a car accident (rear ended) with the computer sitting in my back seat of the car. I'm thinking that jolt may have had something to do with the failure. The replace for that drive was a 5gb Micropolis. It had "clicky" (read head tapping the platter) problems out of the box, but after RMA'ing that drive the replacement worked fine (and still works fine in an old computer I keep in my shed).

      And then I met the beast known as the IBM Desktar 75GXP 40gb. I went through 5 of those, all the same drive (or rather, the same warranty) having to RMA it over and over. It was eventually replaced with a 60gb 60GXP. That one failed too. It's replacement is still working, but it makes a clicking noise every now and then that isn't the "normal" read noise - I don't put any data on the drive. Just apps that I have backup install media for. There was eventually a class action suit brought against IBM for these drives. They were just terrible.

      I'll still never buy anything that says Desktar again, and despite the possiblity of the crash effecting it, my time spent as a computer tech while in college has prompted me to never buy Western Digital again either. Though I'm sure there are other reliable brands, I've developed a very, very good respect for Seagate drives. They never tend to be the fastest, but they've never given me any trouble.

      --
      "People who think they know everything are very annoying to those of us who do."-Mark Twain
    18. Re:Data loss by operagost · · Score: 2, Informative

      RAID-6 may seem inefficient, but it's superior to RAID 10 because it is capable of recovering from two drive failures, whereas RAID 10 may recover from two drive failures. It is possible to lose a second member of one of the mirrors before the first is rebuilt. In RAID 6, you already have enough parity data online to recover immediately from two simultaneous failures.

      --

      Gamingmuseum.com: Give your 3D accelerator a rest.
    19. Re:Data loss by Feanturi · · Score: 3, Informative

      What are people doing with drives to make them fail?

      I've got the same question, as I've gone through a lot of hard drives over the years but only due to upgrading, not failure. The only exception was the IBM Deskstar GXP75 that had the whole click of death thing going on. I don't count that one since it was a known issue that resulted in a class action suit, which I didn't bother to take part in. The first one failed within a month, so I replaced it at the store, and the replacement failed after a day. Replaced again. The third one failed after a week but I was tired of going back to the store by then so tried an experiment - the click of death was kicking in somewhere near 500MB after the beginning of the drive so I repartitioned it to leave the first 500MB unpartitioned. My experience with the drive up to that point told me that wherever the click of death manifested, it would consistantly happen in whatever part of the drive it first happened at. That drive has been in constant use ever since then (it's been like 5 years or so by now hasn't it?) and still works great, since it never accesses the 'bad part' anymore.

    20. Re:Data loss by Mr+Z · · Score: 2, Informative

      Right, but if the wrong 2 drives fail, you're hosed. You can lose up to N drives (out of a 2*N array) only if you lose 1 drive from each mirror pair. It's possible to hose a RAID 10 array of any size by losing just two drives if they're the two drives that mirror each other.

    21. Re:Data loss by afidel · · Score: 2, Informative

      The best is something like what Xiotech implements, we do virtual RAID10 across all our spindles and it makes sure that no data and redundancy block are in the same drive bay. That way you can lose both power supplies or fibre controllers in a disk cabinet and not lose any data. It can do the same with RAID5 but performance is limited by the speed that the controllers can do the parity calculations whereas with RAID10 we are limited only by FC bandwidth or the number of concurrent I/O's we are trying to push (we've tested to 18,000).

      --
      There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
    22. Re:Data loss by aztracker1 · · Score: 2, Interesting

      I like to use Raid1 myself.. usually not an issue, but I did have two drives fail at once in a system, which royally sucked.. one wouldn't do anything.. fortunately the other was able to run long enough to rebuild the mirror (after a 15 minute stay in the freezer). Most disk access, for most typical use is read.. so slower writes aren't a huge deal.

      --
      Michael J. Ryan - tracker1.info
    23. Re:Data loss by pakar · · Score: 2, Insightful

      Hmm... lets see... The IDE interface has been around since around 1984 so that's around 24 years.. Quite impressive... SCSI came at 1981 so that's around 26 years... Depending on the adapter you might even be able to access one of those old SASI disks that came around 1979, so now we are up to about 28-29 years of old hardware that you can access with currently available controllers... And you could even read punchcards with current hardware.. Just get a scanner :)

      The issue is always if you have some possibility to read the media in the future, and it's always a hard thing if you have something that requires some extra reader with moving parts that can fail even if it's not being used due to corrosion and such... And i do think that a plain controller-card without any moving parts can be a bit easier to store, and if just using lots and lots of disk you can just migrate the data as time go by and the disks becomes cheaper.. Alot more fuss if you would want to migrate any of those LTO tapes to some new tape since that would require someone to fetch the tape, put it into a reader, read the data back, verify the data and then continue on with the next tape.. Just look at the past.. The amount of storage the disks have has exploded.. I remember when i got my first 'big' drive of a whole whopping 20MB and now around 20 years later i could fit 250 copies of that in my RAM..
      So the problem is not really 'how do we store all the data' but more 'How do we migrate the data to new storage in the future?'

      1. Man paints on cavewalls - still visible ~30000 years
      2. Man carves on stone-platters - still visible after ~20000 years
      3. Man writes on paper/papyrus etc - still readable after ~7500 years
      4. Man invents computers - All unmaintained data older than 40 years is lost :)

      And yes, it's fun to mess with people at this hour :)

  5. Comment removed by account_deleted · · Score: 3, Funny

    Comment removed based on user account deletion

  6. Re:Perpendicular by sykopomp · · Score: 4, Interesting

    best hardware ad ever http://www.youtube.com/watch?v=-xPvD0Z9kz8 Get perpendicular!

  7. whoops by scapermoya · · Score: 3, Insightful

    FTFA: "Gigabyte drives were only "missing" 24 bytes, and that was easy to swallow."

    i think they meant 24 megabytes, which is easy to scoff at now, but wasn't when the first gigabyte drives dropped.

    --
    Beware the Jubjub bird, and shun the frumious Bandersnatch.
  8. it's been here for a while by _Shorty-dammit · · Score: 3, Interesting

    There have already been several drive models using this technology. Seagate's 7200.10 line comes to mind. Toshiba released one in 2005, for that matter. And Fujitsu's got some, too.

  9. The author has some problems with his arithmetic by Don+Sample · · Score: 5, Informative
    He spends a lot of time talking about the difference between binary and SI terabytes and gigabytes, and then comes out with:

    Back in the day, the gap between decimal and binary capacity wasn't big enough to ruffle feathers. Gigabyte drives were only "missing" 24 bytes, and that was easy to swallow.
    Um, 24 bytes is the difference between kilo meaning 1000 and kilo meaning 1024. A binary gigabyte is 1,073,741,824, or 73 megabytes bigger than an SI gigabyte.
  10. tebi? shut up. 1 terabyte drive still NOT here by _Shorty-dammit · · Score: 5, Insightful

    This marketing BS always pisses me off. For years and years and years we've used 1024 in the computer world, since it's a power of 2, and computers deal with powers of 2. A 931GB drive is NOT a 1TB drive. And we don't need new stupid labels like tebi, we just need storage manufacturers to stop being retards.

    1. Re:tebi? shut up. 1 terabyte drive still NOT here by ipooptoomuch · · Score: 2, Insightful

      When the marketing department figured out they could make their drives look 5-10% bigger than what they actually were to all non-techies they took advantage of it.

    2. Re:tebi? shut up. 1 terabyte drive still NOT here by Jugalator · · Score: 4, Insightful

      Tera is the SI unit for 10^12 so unless you want to introduce special cases for the computer industry alone, we need a new prefix.

      --
      Beware: In C++, your friends can see your privates!
    3. Re:tebi? shut up. 1 terabyte drive still NOT here by _Shorty-dammit · · Score: 5, Insightful

      Way to pay attention. Nobody gives a rat's ass about "the SI unit." These are computers. And we've always used kilobyte/megabyte/etc as they applied to computers. You think you're right, but you're not. A kilobyte will always be 1024 bytes. A megabyte will always be 1024 kilobytes. A gigabyte will always be 1024 megabytes. And a terabyte will always be 1024 gigabytes...

    4. Re:tebi? shut up. 1 terabyte drive still NOT here by Moridineas · · Score: 4, Insightful

      The revisionists are everywhere unfortunately..

      Every time I see a wikipedia page with MiB or mebibyte or whatever the heck, I want to change--fix--it!

      e.g..

      http://en.wikipedia.org/wiki/Voodoo2

    5. Re:tebi? shut up. 1 terabyte drive still NOT here by Anonymous Coward · · Score: 5, Interesting

      The definition of Tera of anything is 10^12 of that object.

      Let us take your absolutism to its logical conclusion.

      Prima: I've got a huge car!

      Secunda: Dude, I've got a huge cat!

      * SUV-sized cat walks in.

      Prima: Dude!

      Secunda: (looking to camera) No, you see, "big" is an adjective, and must be read in the context of the noun it describes. A big cat is not the same size as a big car, or a big house, or a big boat. Prima: I see what you're saying. Similarly, a "kilo-gram" is prefixing the gram, a base-10 system, thus 10^3 grams; while a "kilo-byte", prefixing the byte, part of a base-2 system, refers to 2^10 bytes?

      Secunda: Exactly! Humans, complex machines that they are, make use of context to bring out meaning.

      Prima: But on Wikipedia it says this use is incorrect?

      Secunda: Well, Wikipedia has the quality of a scientific journal... assuming submissions to scientific journals were all accepted for publication, and could be edited by anyone at any time.
      Prima: So, the individual or group with the most amount of time ends up producing the predominant content?

      Secunda: Exactly! The best way to confirm whether an article is likely to be useless is to read its talk page; in fact, you are more likely to learn from this page, as it illustrates the points of contention that one side or the other has tried to suppress.

      Prima: So for the past two decades we have called 1024 bytes a "kilobyte", until one standards body associated with manufacturers of hard drives decided to redefine it...?

      Secunda: Precisely. Worse, the previously unambiguous (outside of hard drive manufacturing) "kilobyte" is now defined as "1000 bytes". It'd be like renaming the mile to the "iMile", then stipulating that all future uses of "mile" should be based on the origin of the word - i.e. one thousand double paces.

      Prima: But paces vary from person to person - it's like you're making an arbitrary change based in a tenuous argument that goes against the principle that language evolves other than by edict!
      Secunda: Now you're getting the hang of it. Have you considered becoming a Wikipedia editor?

      Tercera: Listen you two, either shut up or get a room.

      Prima: Let's get some beer.

      Secunda: Word.

      * SUV-sized cat disappears in a puff of semantics, replaced with a slightly overweight puddytat.

    6. Re:tebi? shut up. 1 terabyte drive still NOT here by Eivind · · Score: 5, Insightful
      It's worse than that actually, because as the sizes grow, the disparity grows too.
      • When you say 1KB, the difference is 2.4% or 24 bytes.
      • When you say 1MB, the difference is 4.8% or 48KB.
      • When you say 1GB, the difference is 7.4% or 74MB.
      • When you say 1TB, the difference is 10% or 100GB.
      So, the higher the capacity, the more difference is there between binary and decimal units. 2.4% difference is significant enough, but it's not as bad as 10%. Lacking 100GB, or a full tenth of the capacity is however quite noticeable.
    7. Re:tebi? shut up. 1 terabyte drive still NOT here by Anonymous Coward · · Score: 2, Interesting

      Lol, you're so obviously clueless. The SI prefixes have been EXPLICITLY defined as base-10 since the 1890's. Long before the comp.sci people ARBITRARILY defined the prefixes to be base-2 in their field.

      The "mile" had been defined as 1000 double-paces since before the supposed birth of Christ. But then its meaning evolved in various contexts - the statute mile, the nautical mile, etc. Or, to use your language, "people ARBITRARILY redefined the mile". I hope that you maintain consistency with the original Roman definition when observing speed limits.

      The "kilo", as you say, was defined according to the SI system in C18 to mean "1000 of". But then, as you barely well describe, its meaning evolved in a particular field. In fact, even better, it evolved within a specific context, so all its previous uses stand; and the redefintion was far from ARBITRARY, since powers of 2 make sense to use in binary, and powers of 10 usually don't.

      Please try to get to grips with context in understanding language. It's a skill some engineers are very bad at; X in context A is not precisely X in context B. It never will be, because this sort of simplified reasoning abrogates the human brain's fantastic ability to recognise patterns without the need for identity.
    8. Re:tebi? shut up. 1 terabyte drive still NOT here by maxume · · Score: 2, Insightful

      So for like two weeks back in 1992, they were really screwing people over? Because they have all used the same convention since basically forever.

      (I guess if somebody had a 10 gigabyte file to store and bought a 10 gigabyte disk to store it on they would be pissed, but I'm willing to assume that that one guy got over it...)

      --
      Nerd rage is the funniest rage.
    9. Re:tebi? shut up. 1 terabyte drive still NOT here by Firehed · · Score: 2, Insightful

      There's absolutely no need for the power-of-two notation anymore, at least not when you're viewing the drive properties to check free space. The "mega", "giga", "tera", et al prefixes are globally defined to be powers-of-ten - 10^6, 10^9, and 10^12 respectively. If you want to keep with the old-school notation of 2^20, 2^30, and 2^40 respectively, be my guest, but don't complain when your numbers come up short.

      It's the operating systems - Windows, Mac OS and the *nixes alike that are mis-reporting drive size (or, rather, the units). I don't care who changes at the end of the day so long as the two are in parity so a "1TB" drive (be it 1TB or 1TiB) shows up as 1TB for my drive size in the OS. Sure, I'd prefer having extra space on the hard drive, but it's the OS writers that are truly at fault.

      I agree - the notation of the SI and binary units is completely moronic. But until someone changes, be it the OSs or the HDD manufacturers, don't expect things to start matching up.

      --
      How are sites slashdotted when nobody reads TFAs?
    10. Re:tebi? shut up. 1 terabyte drive still NOT here by achbed · · Score: 2, Insightful

      Except that I know plenty of non-computer savvy people who walk into Staples, pick up a drive off the shelf, get it installed, and then ask "But why is the size different from what it says on the box?" I'm waiting for the 1TB (not TiB) drive to result in lawsuits over people not getting their promised 1TiB.

    11. Re:tebi? shut up. 1 terabyte drive still NOT here by Lord+Ender · · Score: 2, Interesting

      For years and years and years we've used 1024
      And we were wrong to do it. Metric prefixes meant base 10 for "years and years and years" before people started trying to use them for base 2. In every industry, and part of the computer industry, metric prefixes mean base 10.

      Why fight the rest of the world over this? Now that we have binary prefixes, let's use them! This idea that metric prefixes are base 10 in networking and base 2 in storage is embarrassingly inconsistent. Let binary prefixes mean binary, and let metric prefixes mean base 10! Just because we did it one way in the past doesn't mean it is the best way to do it now! This is engineering, not religion.
      --
      A slashdotter who didn't build his own computer is like a Jedi who didn't build his own lightsaber.
    12. Re:tebi? shut up. 1 terabyte drive still NOT here by clarkcox3 · · Score: 2, Informative

      So? "Byte" is not an SI unit.

      KB, MB, GB, TB, etc. have had a well-defined meaning for decades (probably over a half century by now). According to The Oxford Pocket Dictionary of Current English:

      n. Comput. a unit of memory or data equal to 1,024 (2^10) bytes.

      ... so get over it, a kilobyte is 1024 bytes.

      --
      There are no tiger attacks in my area and it's all because this rock I'm holding keeps the tigers away.
  11. Visit our site! by Zebedeu · · Score: 4, Funny

    The Tech Report has tested the 7K1000's performance, noise levels, and power consumption against 18other drives to find out, with surprising results. Suspense!

    Come on! Just tell us what the results were directly, don't make us have to break Slashdot law and RTFA!
    1. Re:Visit our site! by LarsG · · Score: 4, Informative

      I've RTFA, and still don't get what the 'surprising results' is supposed to be.

      It has huge capacity - check.
      It is noisy and sucks power - check.
      It is not a speed champion - check.

      Not exactly surprising for the first 1TB drive on the market.

      --
      If J.K.R wrote Windows: Puteulanus fenestra mortalis!
  12. Conclusion in the article: by Futurepower(R) · · Score: 4, Informative

    Conclusion in the article: Too expensive.

  13. RAID 6 Please by the_doctor_23 · · Score: 3, Interesting

    Make that RAID-6. With consumer grade drives I would not want to see a second drive die during a RAID-5 rebuild.
    For example a 3ware 9650SE-8LPML can be had for as little $520.

    --
    "Extraordinary claims require extraordinary evidence" - Carl Sagan
    1. Re:RAID 6 Please by Anonymous Coward · · Score: 4, Informative

      Because it isn't safer, at least not unless you have a battery-backed interface card *anyway*. And usually the only cards with battery-backing are... hardware raid cards. I have been known to use linux-md on an old hardware raid card, when the card had a very slow processor. But these days, raid cards have processors in the 300-600 MHz range, AND ASIC or FPGAs to do parity. They're more than adequate.

      Also, linux-md doesn't guarantee ordering, which hardware-raid cards, as they're intended for use with oracle and friends, do.

    2. Re:RAID 6 Please by Spazmania · · Score: 5, Interesting

      Depends on the raid card. I run about 80 servers with a mix of HP/Compaq SmartArray, Adaptec aacraid, LSI Megaraid and Linux MD raid systems.

      The Adaptec and LSI Megaraid cards are truly heinous. Just last week I had a system that wouldn't boot because the megaraid card decided that the NVRAM and on-disk settings didn't match... Even though the "force boot" option was set. Force-boot is supposed to write the on-disk config to nvram on a mismatch. As often as not, a machine with a megaraid card crashes on a single-disk failure instead of continuing to operate minus one disk. It'll reboot fine but not before you lose the unwritten data and deal with filesystem corruption. And God help you if a second disk develops a bad spot... It won't do the best it can to rebuild; it'll simply flunk leaving the good portions of the data unrecoverable.

      I'll match Linux MD against those cards for reliability purposes any day. I wish there was some hardware I could buy that enhanced it with a battery-backed cache and parity acceleration. Then I could throw away the megaraid and adaptec cards.

      The SmartArray cards are actually very good. Expensive as hell, but good. Sadly the primary configuration utility is on a CD instead of in the bios and some goober at HP decided to rig the disc so it won't boot on any hardware that's not HP/Compaq. Fortunately you can boot Knoppix, copy the linux config utilities and configure it that way.

      --
      Moderating "-1, Disagree" is simple censorship. Have the guts to post your opinion.
  14. 32 MB cache? by dabadab · · Score: 2, Insightful

    Is there any point to these "huge" caches? My Linux system uses a few hundred MB's as disk cache so I don't really expext another few MB's on the disk to make any noticable difference (and, if I recall it correctly, when disks with 8 MB caches were new they did not really gave any performance advantage compared to models with only 2 MB of cache).

    --
    Real life is overrated.
    1. Re:32 MB cache? by dargaud · · Score: 2, Interesting

      s there any point to these "huge" caches? Depends on your use... I work with a lot of images and my drive has a 16Mb cache. When I save an image that's <16Mb, it's almost instant and I can start work on the next one. If the image is >16Mb, it takes a good 5~15 seconds for the drive to thrash around until it's saved it. For me, yeas, a large cache makes a difference as most of my images are in the 10~50Mb range.
      --
      Non-Linux Penguins ?
  15. They may have meant 24 k by FoamingToad · · Score: 2, Informative

    But they'd have still been way off.

    For a decimal megabyte versus a binary one, there's 48 1/2 KB difference.

    For a gigabyte, there's about 70 megabytes difference.

    The only case where you'd only lose 24 bytes would be if you had a kilobyte drive.

    F_T

  16. Re:base 1024 by llirik · · Score: 3, Interesting

    You realize that all non-removable media can be a single drive letter on Windows right? It's trivial to configure on win2k-XP Yeah, except for a small caveat that even Microsoft installers can't deal with it. I had to go back to letters once Visual Studio 2005 refused to install claiming there is not enough space, while in fact there was plenty of space at the mount point where I wanted it to install, but it stubbornly insisted for checking space at the root.
  17. Fills up too fast anyways by emj · · Score: 3, Funny

    The problem is this will be full in 24h with a 100Mbps connection anyways, or ~6 hours if you live in sweden.

    1. Re:Fills up too fast anyways by joke_dst · · Score: 5, Funny

      No matter how big a hard drive gets it still only has two states: new and full.

  18. cat got my tongue by Anonymous Coward · · Score: 3, Funny

    Yes, but does it Destroy Planets ?

  19. Meaningful tests? by mrkh · · Score: 4, Insightful

    I'm not that convinced by the testing methods here. The boot and load times page shows 20 seconds difference between the slowest and fastest drives which they barely comment on, and yet the drive with the slowest boot time is among the quickest when loading Far Cry and Doom 3? Something is not right there.

    And if they're really timing level loads with a stopwatch, why on earth are they quoting 2 decimal places (and besides, the variability in reaction time is accounting for most of the supposed differences in any case). Half of their tests don't appear to tell anybody anything significant, and the most worthwhile page in there is the conclusion. Pretty graphics though.

  20. Nothing new, then by Moraelin · · Score: 2, Insightful

    Nothing new, then. At this point 1 TB may sound like "that much data", but then so did a 40 MB drive waaay back. Heck, at one point 1.4 MB meant a hard drive the size of a large washing machine. Nowadays that's called a floppy and already outdated.

    What I'm getting at is that it's sorta like "Moore's law" for hard drives. (And occasionally Murphy's law too;) What's "whoa, I'd hate to lose that much data" at one point, is just adequate in a couple of years, and not even enough for your system files and/or swap file in 20 years.

    --
    A polar bear is a cartesian bear after a coordinate transform.
  21. The value of consistent nomenclature by Valacosa · · Score: 5, Insightful

    Nobody gives a rat's ass about "the SI unit." These are computers.
    Yeah. Making nomenclature consistent across industries is damned inconvenient! Why bother?

    Look, I hate marketing dishonesty as much as the next guy, but borrowing the SI prefixes honestly does nothing but add confusion. Hard drives are easy, because one can safely assume that the marketing 'tards went with whatever number was bigger. But what about my phone's data plan? Aside from the whole kB vs kb thing, how do I know which definition of "kilo" my provider has gone with? Do they consider themselves with the "computer industry" or with the rest of the world? And (this is the best question), will the not-very-well-paid support grunt even know the difference?

    Would you like it if you agreed to sell a dozen POS systems to a bakery, only to be told after the contract, "Sorry sir. This is the baking industry. You agreed to give us thirteen systems." Or if you got a $30 bill from your ISP with the explanation, "This is the computer industry. Though our adverts say this plan is $30 a month, that's hex. In base-ten dollars, you owe us $48."

    You hate marketing people skewing reality. Good. It is only through fighting ambiguity that they can be stopped from getting away with this.

    Do you know the difference between a pipe and a tube? If you get into any business involving either, I hope you don't repurpose the words everyone else has settled upon.

    You think you're right, but you're not.
    It's that extra bit of humility that really makes your post shine.
    --
    "Live as if you'll die tomorrow." Ridiculous. You could die later today.
  22. O RLY? by _Shorty-dammit · · Score: 2, Informative

    http://stason.org/TULARC/pc/hard-drives-hdd/ibm/WD A-L42S-40MB-3-5-HH-IDE-AT.html Hard Drive: IBM: WDA-L42S 40MB 3.5"/HH IDE / AT Cylinders: 1067 Heads: 2 Sectors per track: 39 Bytes per sector: 512 1067 * 2 * 39 * 512 = 42,611,712 bytes 42,611,712 / 1024 = 41613 kilobytes 41613 kilobytes = just over 40.6 megabytes This was sold as a 40MB drive. Not a 41MB, 42MB, or 43MB drive. A 40MB drive. And that's just what it was, a 40MB drive. So, I'm sorry to tell you, but lying about the drive's size was *NOT* always the way it was. This is just one example. And, no, I don't care for finding out exactly when manufacturers started lying about capacity. They did, and that's enough for me.

    1. Re:O RLY? by Ed+Avis · · Score: 2, Interesting

      I think that the '40 megabyte' branding is just rounding to a multiple of ten... but anyway, the first commercial hard disk, the IBM 305, had a capacity of five megabytes - five million bytes, exactly - and was sold as such. Actually, it could have held more, but marketing thought that five megabytes was a nice round number. (Some of the space was taken for error correction, though.)

      (The long series of calculations you have to go through in your post are the best argument for ditching the 1024*1024*1024 nonsense and just using thousands, millions and billions like the rest of the world.)

      --
      -- Ed Avis ed@membled.com
  23. The history (as I remember it...) by DusterBar · · Score: 2, Informative

    The "clever" marketing company was Atari with the 520ST - they wanted to make it sound better than the Amiga with 520K of memory (it had 512K like anything else, but it was 520 in marketing terms). The same reason they has the 1040ST.

    Note that it was sometime after that point in time (don't have the exact year) that some hard drive manufacturers started to play the same games. (Only with megabytes). Back then it was common to look at a 30meg vs 32meg drive and pick the 32meg drive. So when a marketing person figured out that a "real" 40meg drive could be called 42meg "unformatted" and get away with it, well, they did. And the other manufacturers followed and, well, everything was different by the time 1990 happened... (or so, maybe 1991 for the last holdout)

    It really does not matter much now - but when different manufacturers followed different rules, it was a real problem.

    (ps - Jack was always pushing the marketing envelope - albeit I can not claim to know if he did come up with the 520-vs-512 idea himself, he did push it rather hard)

  24. Power-of-10 prefixes are the norm in IT by this+great+guy · · Score: 4, Informative
    Contrary to common belief, power-of-10 prefixes (as used by disk manufacturers) are much more commonly used than power-of-2 prefixes in the IT world. People claiming the contrary are wrong. Here are a few examples:
    • A 128 kbit/s audio stream is 128 * 10^3 bit/s (power of 10)
    • A 100 Mbit/s ethernet card is 100 * 10^6 bit/s (power of 10)
    • A 480 Mbit/s USB2 link is 480 * 10^6 bit/s (power of 10)
    • A 500 GByte disk is 500 * 10^9 bytes (power of 10)
    • A 56 kbaud modem is 56 * 10^3 baud/s (power of 10)
    • A 1.5 GHz processor is 1.5 * 10^9 Hz (power of 10)
    • A 6 Mbit/s DSL line is 6 * 10^6 bit/s (power of 10)
    • A 650 MByte CD is 650 * 10^6 bytes (power of 10)
    It is a total mystery to me why people think that power-of-2 prefixes should be the norm, when the only few places where they are used are to refer to the size of files and RAM sticks.

    Spread the truth. Mod me informative ;-)
    1. Re:Power-of-10 prefixes are the norm in IT by SoapBox17 · · Score: 3, Insightful

      If you notice, everything listed in the parent is in powers of 10 bits (or Hz) except for disc capacities. Like everyone else said, this is because disc manufacturers want to confuse you. When talking about m/g/k bits the convention is to use powers of 10, and when talking about bytes it is to use powers of 2. Hence, as the parent said, powers of 2 are used for file sizes and RAM sizes... because those are usually in bytes.

    2. Re:Power-of-10 prefixes are the norm in IT by this+great+guy · · Score: 2, Informative
      So you are still not convinced ? Here are some examples not based on bits or Hz:
      • A 1x 250MB/s PCI-e lane is 250 * 10^6 byte/s (power of 10)
      • A PC3200 DDR400 memory stick is 3200 * 10^6 byte/s (power of 10)
      • A 56 kbaud modem is 56 * 10^3 baud/s (power of 10)
      • A 650 MByte CD is 650 * 10^6 bytes (power of 10)
      • A 300 MB/s SATA link is 300 * 10^6 byte/s (power of 10)
      • A 4000 MB/s HT1 link is 4000 * 10^6 byte/s (power of 10)
      • And of course, a 500 GByte disk is 500 * 10^9 bytes (power of 10)
    3. Re:Power-of-10 prefixes are the norm in IT by MrHanky · · Score: 2, Insightful

      No, when talking about RAM, where a MB is 1024 KB where a KB is 1024 bytes, you're talking about stuff connected to a memory controller that addresses this in a certain number of two, so that a 32 bit controller can address 4,294,967,296 bytes or 4 GiB. A disk controller works in a different way, and a disk is addressed in a different way. The only reason for demanding the same kind of numbering from a disk is when you need to know how much RAM a file will consume when you load it. Which is why a file's size may be denoted in KiB.

      It really isn't confusing at all. I suspect the outrage at hard drive capacities is really caused by the high frequency of autism in the geek community.

    4. Re:Power-of-10 prefixes are the norm in IT by Fex303 · · Score: 2, Funny

      Here's hoping quantum computing doesn't make a sudden arrival - otherwise people may start using qbits and confusion would really reign! ;-)
      Schrödinger's hard drive - you don't know the capacity until you open the box.
  25. Real-world use by zuki · · Score: 4, Interesting

    Been using this drive as my primary music streaming audio drive while on the road, with rugged real-world everyday mission-critical use
    in front of thousands of people, where one mis-hap is already too much.

    So far things have been flawless, and it has made a huge difference for me due to portability compared to anything else of the same capacity.
    as previously this meant a two-drive combo with heftier power supply.

    The weight and size make it easier to have it as a carry-on item, rather than in my checked luggage!
    As far as performance, it has been able to handle 4 simultaneous 24-bit / 96 kHz audio tracks playing back with no hiccups whatsoever.
    The drive-to-drive copying in Firewire 800 or SATA has been quite speedy and error-proof.... (copying 900 gig at a time is always a good test)
    Dream come true if you ask me.... I still carry a backup anyway, LOL!
    (ymmv(TM), batteries not included, kids don't try this at home, etc....)

    Z.

  26. Ok... but 992, 977, 1023, 1011, 973 or 1005? by PMBjornerud · · Score: 4, Insightful

    Nobody gives a rat's ass about "the SI unit." These are computers. And we've always used kilobyte/megabyte/etc as they applied to computers. Well, maybe electrical engineers would prefer to have 992 watts on the kilowatt, grocers would like to define a kg as 977 grams. Maybe 1023 tons of TNT is what fits on a standard truck, so it would be handier than that stupid 1000 for a kiloton. And the food industry, maybe they would like to redefine kilocalories as 1005 to the kilo, just because of some weird internal workings of molecular workings?

    But instead of going with whatever number that fits their specific field, they all went with 1000. Really, that IT people refuse to do the same makes us look utterly retarded.

    Not that it matters anyway. With 8 bits on the byte, we're doomed before we even start. There is no hope in sight until we just ditch this shit, get a clue from the network people, and start counting bits in multiples of 1000.
    --
    I lost my sig.
    1. Re:Ok... but 992, 977, 1023, 1011, 973 or 1005? by poot_rootbeer · · Score: 4, Informative

      Maybe 1023 tons of TNT is what fits on a standard truck, so it would be handier than that stupid 1000 for a kiloton.

      Are those "long" tons (2240lb), "short" tons (2000lb), or "metric" tons (1000kg)?

      Ambiguous terms of measurement do exist outside of the computer industry, too -- which, I should point out, is actually "the software development industry" plus "the hardware manufacturing industry" plus "the IT service industry" and so forth.

      Drive manufacturers have always used base-10 prefixes to describe the capacity of winchester drives. It's not a marketing ploy, it's historic convention.

  27. Pretty small platters by AbRASiON · · Score: 4, Interesting

    So this baby has 200gb platters, it sounds all impressive and all, except we've had 188gb platters for ages now.
    Seagate has announced (and released, I think?) their 1TB HDD with only 4 platters (cooler, quieter, less power, less weight, less cost to manufacture) that's 250gb a platter

    Samsung have announced the F1 using 333GB per platter! 1.6TB if they copy Hitachi and slap 5 of them in a 3.5" unit - or rather 333gb single platter, light, cheap drives, be damned if anyone can find the F1 yet though :/

  28. Solid State? by SharpFang · · Score: 2, Interesting

    Interestingly, this form factor would neatly fit some 512 MicroSD cards leaving enough room for mechanics (slots, frame) and electronics. Take 512 2GB cards, you get 1 terabyte of solid state memory. Each of the cards can work independently from the others = easy RAID of 512 disks = quite insane speeds possible, and cheap replacement of failing parts (you replace a single failing card, not the whole device). Of course the price would be higher, but still the 1TB drive isn't cheap for sure, and without RAID.

    --
    45 5F E1 04 22 CA 29 C4 93 3F 95 05 2B 79 2A B2
  29. 5.25"? by Doc+Ruby · · Score: 2, Interesting

    The drive is the first to pack a trillion bytes into a standard 3.5" form factor

    Hard drives used to be physically much bigger, when the interface tech was "MFM: 5.25" diameter, and "Full Height" was about 3.5".

    Physically smaller discs have faster access times and lower power consumption. But why not use larger discs for their higher data capacity, without wrapping each smaller chunk in the same electronics overhead for rotation and data transfer? And get the faster data transfer at the outer cylinders from their faster angular velocity?

    At a guess, I'd say that a 5.25" full height HD could have 2.5x the 3.5" capacity per platter, and probably at least 5x the platters, for about 12x the capacity. The access times across the large areas would be larger, but for large files that wouldn't matter as much (as long as they're kept defragmented).

    These truly "large" drives could be the best for archiving, thrown back in place after an emergency and gradually replaced with 3.5" disks (if necessary) as they continue to run.

    We could have 12TB drives with the same encoding tech as these Hitachis. And they'd cost less per TB than the 3.5" ones, because they'd have more storage per overhead hardware. Where can I get one?
    --

    --
    make install -not war

    1. Re:5.25"? by Fweeky · · Score: 3, Insightful

      Except they'd have more parts, more complexity, and the larger components would need to be made to even finer tolerences since they need to remain well aligned over a much larger area (and they'd need to be stronger if you wanted to keep the same sort of RPM). They'd be much more expensive, and you'd probably still have to drop the density per platter a lot to keep it within the realm of sanity, not least because of things like thermal expansion having a much larger effect.

      File next to the disk with multiple drive head assemblies; possible, but just not worth it when you could just fit more, smaller, cheaper, independent disks in the same space.

  30. I'll never buy a Hitachi *cough* IBM Deskstar by Pigeon451 · · Score: 3, Insightful
    Several years ago when IBM released their much hyped Deskstar performance series hard drives, I bought one. It was more expensive than the others, but since I was doing some video work at the time, I figured I would splurge even though I was a student.

    It died a horrible death only three years later, just outside of warranty. Despite a class action lawsuit against IBM (in the US, not Canada) I couldn't get it replaced. There was apparently a fix for it, simply by downloading a program, but really, who looks for updates to their hard drives?

    IBM further went into my bad books, after it simply sold off the business to Hitachi instead of fixing their mess. It really left a sour taste in my mouth for IBM ...

  31. Why didn't they compare it against 1TB Samsung ? by Brane2 · · Score: 3, Interesting

    While Hitachi uses 5 platters for 1TB, Spinpoint F1 manages to pack that space on only 3 platters, so it should be faster, more quiet and lower power than Hitachi. Not to mention good deal cheaper.

  32. Re:Exactly! by LighterShadeOfBlack · · Score: 2, Insightful

    So, what, you'd rather have had zero indications of hard disk failure then only one?

    I've had four drives fail on me before (all of them Maxtor), SMART predicted one of them a month in advance by which time I'd backed up the whole thing. Maybe it missed the other three but even if it only catches a few errors, that's still a hell of a lot better than none isn't it?

    --
    Spelling mistakes, grammatical errors, and stupid comments are intentional.
  33. On another note... by gerardrj · · Score: 3, Insightful

    TOO states " As the first hard drive to reach the terabyte mark, Hitachi's Deskstar 7K1000 will be remembered, too. Squeezing a trillion bytes into a 3.5" hard drive form factor is a monumental engineering achievement"

    I doubt that anyone will remember this in a year. Quick; what was the model and manufacturer of the first drive to pass 500GB, or 1GB. Both were monumental engineering achievements in their time. These milestones will not be remembered because they are all evolutionary; a 10-30% jump in capacity. When we see 10x capacity increases in one generation, THAT name might be remembered.

    That said.. good job Hitachi, but we all know that WD and Seagate will be out with their versions in a month or so.

    --
    Article X: The powers not delegated... by the Constitution...are reserved...to the people
  34. Haven't you seen "Avenue Q"? by wsanders · · Score: 3, Funny

    http://www.stlyrics.com/lyrics/avenueq/theinternet isforporn.htm ...

    TREKKIE AND GUYS
    Porn, porn, porn, porn
    porn, porn, porn, porn
    KATE
    I hate the internet!
    TREKKIE AND GUYS
    Porn, porn, porn, porn

    TREKKIE
    The internet is for

    TREKKIE AND SOME
    The internet is for

    TREKKIE AND ALL
    The internet is for PORN!

    TREKKIE
    YEAH!

    --
    Give a man a fish and you have fed him for today. Teach a man to fish, and he'll say "WHERE'S MY FISH, YOU IDIOT?"
    1. Re:Haven't you seen "Avenue Q"? by HobophobE · · Score: 2, Funny

      The video is on YouTube...

      http://www.youtube.com/watch?v=QtiGd58J0bY

      --

      -HobophobE
      Nothing laughs forever.